>> > > If you have HTTP-over-SSL service on 80 port, users connect to it with > "https://hostname:80". If you use proper HTTP-over-SSL port, they connect > to "https://hostname". No port numbers visible and URL is nicer. > >> the correct install works with https://hostname > > My tests show that APC reduces SquirrelMail memory usage. Not sure, if > memcache helps. Problems with memory usage might cause issues in compose, > if folder listing uses memory to the point where you start hitting > memory_limit in compose. the memcache was recommended for install with APC for FreeBSD >> >> no oy os false although SOrty and THread are availabel onf dovecot > > Please turn on server side sorting in SquirrelMail configuration. It is > written in SquirrelMail optimization guidelines. If you don't do that, you > will run into trouble on larger sorted mail folders. Okay i was going with the installation instructions I saw which seemed luke warm on that > >> have not tried that yet >> >>> A02 namespace >>> ... show this response >> >> * NAMESPACE (("" "/")) NIL (("Public/" "/")) > > Your Dovecot namespace configuration is similar to the one which was used > when dovecot preset was implemented. > I am 99% certain that my IPAM settings are the default that SM found when I ran setu > Backup your SquirrelMail configuration (config/config.php). Start conf.pl > and select D command. Select dovecot preset. Save configuration. > > Remove all individual sent, draft and trash folder preferences from .pref > files. Remember that preferences are cached in PHP session and you should > restart browser or delete SquirrelMail cookies, if you want to clear > cache. > I am uncertain as to what .pref u are referring the only thing I can easily find close is a default_pref in /data > Check if it starts working after applying preset and cleaning user > preferences from folder customizations. > > Test things in alternative non-user facing SquirrelMail setup, if you want > to be sure that your configuration changes work. Always apply proper IMAP > preset first when you create initial SquirrelMail configuration. > > -- > Tomas > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > ----- > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users