search for: kmcgrail

Greetings, I have several users who have inboxes that are over 20 GB. Lately I have noticed Dovecot logs say it's taking over 30 seconds to sync their mailboxes. As email admins,? how do you handle inboxes that are so large? Do you use mailbox types that have better performance like dbox? We're using maildir. What's a reasonable inbox size?? Is 20+ GB reasonable and nothing to

On 3/28/2019 7:42 AM, Aki Tuomi via dovecot wrote: > olution: > Operators should update to the latest Patch Release. The only workaround > is to disable FTS and pop3-uidl plugin. Hi Aki, thanks for the CVE.? For quick mitigation, can you confirm how to disable these plugins and what they provide?? We'd like to assess if we are using them while we rollout the fix. Regards, KAM

On 3/28/2019 10:40 AM, Aki Tuomi wrote: > > check for fts in mail_plugins. pop3-uidl is used by pop3_migration > plugin. Sorry if I'm dense but can you be more specific?? Are you talking about checking conf files or binary files?? For example, does the existence of /usr/local/lib/dovecot/lib20_fts_plugin.so imply an exploitable situation?? Are their settings in a conf file that

On 5/7/2020 11:39 AM, Asai wrote: > What's a reasonable inbox size?? Is 20+ GB reasonable and nothing to > worry about? > Great question. At my firm, we wrote rotation tools that work for mbox format to rotate inboxes monthly if they are over a certain size.? We also do the sent items folders. We find that large inboxes are bad for the server and bad for the client because the MUAs

On 5/7/2020 12:43 PM, Asai wrote: > Thanks for your response, > > So, how do those rotation scripts work in concept? > > People are still able to access their old inboxes, but it just moves > them to an archived state? We rotate the folder to another name with the date like INBOX-2020-05-07 with instructions how to refresh their folder list (or even modify the .subscription file

I'm throwing an error compiling with a custom-compiled gcc 3.2.3 on one box. The configuration string is CC=/usr/local/gcc3.2.3/bin/gcc CPPFLAGS=-I/usr/local/ssl/include LDFLAGS=-L/usr/local/ssl/lib ./configure --with-ssl=openssl --with-ssldir=/usr/local/ssl/certs --with-pam --with-pop3d --sysconfdir=/etc --localstatedir=/var I've used this to compile on other older boxes with success.

Possible Caching Bug showing up as a MIME Boundary Issue I'm using Dovecot version 1.0.0. I was using Dovecot version 1.0.0 beta3 or alpha4. I upgraded to Dovecot 1.0.0 to make sure that was not the issue. Over the past few weeks on a server running a stable dovecot, I have seem a few emails arriving where the MIME document structure dividers are visible. I've included a