- dovecot - dovecot.org

Re: [Dovecot] SSL errors
by Bill Boebel 08 Oct '06

08 Oct '06

On Fri, September 29, 2006 11:46 am, Dominic Marks <dom(a)helenmarks.co.uk> said: >> Actually, I found in the archives that I should increase login_process_size if >> I'm not running with login_process_per_connection. I have done this and that >> seems to have taken care of the malloc failure. However I am still getting a ton >> of these every few seconds: >> >> Sep 29 11:30:06 director4 dovecot: imap-login: SSL_read() syscall failed: EOF >> [70.171.61.190] >> Sep 29 11:30:06 director4 dovecot: imap-login: SSL_read() syscall failed: EOF >> [24.236.204.154] >> Sep 29 11:30:06 director4 dovecot: imap-login: SSL_read() syscall failed: EOF >> [70.171.61.190] >> Sep 29 11:30:08 director4 dovecot: imap-login: SSL_read() syscall failed: EOF >> [65.242.19.3] >> > > These are client disconnects, I believe. > Yep, all of my customers who had IMAP SSL problems are reporting that the problem is fixed now that I have increased login_process_size to 64 MB. In just two hours though the imap-login process is up to 33 MB, and continuing to grow. Is that normal? This particular server handles 1200 IMAP connections and 800 IMAPS connections concurrently on average. Bill

2 1

[Dovecot] Outlook "IMAP server closed connection"
by Mark Adams 08 Oct '06

08 Oct '06

Hi All, Dovecot 1.0rc2. Currently having a problem with Outlook clients popping up with the error; "Your IMAP server has closed the connection. This may occur if you have left the connection idle for to long" I initially though this would be the imap_client_workarounds = outlook-idle option, but this is currently set and always has been. I dont think this is a known issue that has been fixed with newer releases, as we have rc2 on another server that does not have this problem. Any help thankfully recieved. Regards, Mark

2 1

Re: [Dovecot] dovecot-1.0.rc7 install probs
by Timo Sirainen 08 Oct '06

08 Oct '06

On Fri, 2006-10-06 at 19:55 -0400, Steve Maring wrote: > and the make and make install appear to go smoothly. However I am > struck by the lack on an include directory in the install location. > I'm not sure if that means anything. Doesn't mean anything. No header files are installed. > AUXLIBS=" \ > -L/usr/local/dovecot-1.0.rc7/lib/dovecot \ Postfix doesn't need any Dovecot libraries or anything to build Dovecot SASL support. > but the postfix make always dies with: > > smtpd.c:4534: error: âdovecotâ undeclared (first use in this function) Well, don't know about that. I'd ask from Postfix list.

1 0

[Dovecot] Add virtual users to the Dovecot configuration
by Jens E. Madsen Jr. 08 Oct '06

08 Oct '06

Dear Dovecot Mail List, I have used Dovecot for quite a while to service remote users on my SOHO network. A local not-for-profit asked about getting their own dedicated domain name for mail. I followed: http://www.howtoforge.com/linux_postfix_virtual_hosting to set up a virtual, but the article leaves out system accounts and I have not been able to access both system and virtual users at the same time. I have the following lines: default_mail_env = maildir:/var/spool/vmail/%d/%n/ which, when commented out, works for system users default_mail_env = mbox:~/mail/:INBOX=/var/spool/mail/%u which, when commented out, which works for virtual users If both are uncommented, only system users work. Wiki-ing and Googling, I learned that namespace could be applied to the problem. Here is the namespace from the configuration file. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. # The default however depends on the underlying mail storage format. #separator = # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to deprecate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} How do I specify which users use which namespace. Is there a good description of namespaces and how to use them? Thanks Jens

2 2

Re: [Dovecot] Automatically deleting Trash a la Courier
by Jeff Kowalczyk 08 Oct '06

08 Oct '06

Timo Sirainen wrote: > # Expire plugin. Mails are expunged from mailboxes after being there the > # configurable time. The first expiration date for each mailbox is stored in > # a dictionary so it can be quickly determined which mailboxes contain > # expired mails. The actual expunging is done in a nightly cronjob, which > # you must set up: > # dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool > #expire = Trash 7 Spam 30 > #expire_dict = db:/var/lib/dovecot/expire.db For users implementing the expire-tool as an email retention policy, it may be helpful to add path wildcarding and exclusion to handle users with folder heirarchies. e.g., To implement a 1-year retention policy on messages in all folders, excluding all messages in and in subfolders of 'Archived Email': expire = Trash 7 Spam 30 * 365 expire_exclude = Archived\ Email\\*

2 1

Re: [Dovecot] Dovecot vs Ports
by Jos Chrispijn 08 Oct '06

08 Oct '06

Odhiambo WASHINGTON schreef (08-10-06 9:16): > You could have as well explained the problem, if it was that serious. > After the latest portupgrade I rebooted my system and for some reason it stopped booting after loadin acpi.ko Investigated the OS with Fixit (from the first install disc booting and choosing this option from the sysinstall menu). After fsck we could mount the HD and investigate the problem. Main problem was an error in the /etc/rc.conf.. The dovecot_enable was missing the quotes... I think this is due to the portmanager (the person that has made the port for BSD) instead of Dovecot itself... > I am running this version on 30+ FreeBSD 5.5-STABLE boxes and they all > seem fine though. Perhaps I should thank God I still don't run 6.2-PRE? > I think it is a combination of OS version and the person that makes the (accurate) port for that version. Anyway we're all humans after all, so this is allways possible. Just a little bit stressing on a normal Saturdaynight :-) regards, Jos Chrispijn

4 4

[Dovecot] Searchable archives?
by Francisco Reyes 08 Oct '06

08 Oct '06

Is there a searchable archive of the lists somewhere?

3 2

[Dovecot] bug: ssl fails when using certificates with "trust" setting
by Freddy Knolderpoort 08 Oct '06

08 Oct '06

Hi, just a minor bug... I filled in the fedora tracker: **https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208746 It concerns (fedora-)version "1.0-0.beta2.7". Regards,

3 2

[Dovecot] Dovecot vs Ports
by Jos Chrispijn 08 Oct '06

08 Oct '06

Just discovered that there might be a problem with the latest Dovecot update thru portupgrade. If I reboot my BSD (6.2-PRERELEASE), it stopped/hanged during boot-sequence. Thanks to Jack Raats problem is solved now; he will explain _exactly_ what went wrong... regards, Jos

1 0

[Dovecot] test
by Timo Sirainen 07 Oct '06

07 Oct '06

?

3 2