- dovecot - dovecot.org

[Dovecot] mysql index control allow nets
by Evaggelos Balaskas 17 May '08

17 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, I am using dovecot 1.0.13 with sieve plugin, index, control and allow nets in my userdb per user. I am trying to have the same configuration with dovecot 1.1 and MySQL. According to log files when a virtual user is connecting to dovecot, the dovecot reads from MySQL the correct values but dovecot doesnt create the dirs for INDEX, CONTROL and the allow_nets is bypasses. - From my logs : dovecot: May 14 20:56:23 Info: auth(default): master out: USER 12 ebalaskas(a)ebalaskas.gr uid=1002 gid=8 mail=maildir:/var/mail/ebalaskas.gr/ebalaskas INDEX=/var/mail/.index/ebalaskas.gr/ebalaskas CONTROL=/var/mail/.control/ebalaskas.gr/ebalaskas allow_nets=10.10.10.192 The connection is ok (i tested via telnet and webmail) but my IP is : 10.10.10.102 and there isnt any /var/mail/.index/ebalaskas.gr/ebalaskas or /var/mail/.control/ebalaskas.gr/ebalaskas folders The only thing is the folder : var/mail/ebalaskas.gr/ebalaskas the dovecot-sql.conf is correct (you can see this from my logs) so what is wrong ??? Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIKykUWIK+Pe9twhoRAhemAJ0ff793TAsqhDhrAZ7pbATLmDrJggCfXjDZ Cfiojr0LoJc0Vtif6XjfoTs= =Jeph -----END PGP SIGNATURE-----

2 5

[Dovecot] Panic: IMAP(...): Trying to close mailbox INBOX with open transactions
by Mike Abbott 16 May '08

16 May '08

I have been seeing this crash, which has been reported before but apparently not yet resolved. As with the previous reporters, I do not know how to reproduce it reliably. Dovecot version: 1.1.rc5 Operating system: Mac OS X 10.5.2 CPU architecture: x86 File system: HFS+ Activity: From the backtrace it appears the client logged out while in the middle of some operation. Backtrace: 0 libSystem.B.dylib 0x946210ea __kill + 10 1 libSystem.B.dylib 0x946983f2 raise + 26 2 libSystem.B.dylib 0x946a79af abort + 73 3 imap 0x000743e2 i_internal_fatal_handler + 102 4 imap 0x00073e03 i_fatal + 0 5 imap 0x0004614c mailbox_close + 48 6 imap 0x000053c4 cmd_logout + 74 7 imap 0x00007f14 client_command_input + 41 8 imap 0x000080d9 client_command_input + 494 9 imap 0x000081c5 client_handle_input + 218 10 imap 0x0000835d client_input + 176 11 imap 0x0007c001 io_loop_handler_run + 350 12 imap 0x0007af06 io_loop_run + 44 13 imap 0x00010732 main + 1972 14 imap 0x00001e76 start + 54

2 2

[Dovecot] Sieve plugins 1.0.3 and 1.1.5 released
by Timo Sirainen 16 May '08

16 May '08

http://dovecot.org/releases/sieve/dovecot-sieve-1.0.3.tar.gz http://dovecot.org/releases/sieve/dovecot-sieve-1.0.3.tar.gz.sig http://dovecot.org/releases/sieve/dovecot-sieve-1.1.5.tar.gz http://dovecot.org/releases/sieve/dovecot-sieve-1.1.5.tar.gz.sig I've usually released new Sieve plugins at the same time as new Dovecot versions, but since I wasn't planning on releasing v1.0.14 anytime soon and it looks like v1.0.2 release was quite a while ago, I decided to release these today. Changes: - Improved vacation reply checks, log discarded vacation replies (in v1.0.3, these were already in v1.1.0) - Expand ~ to home directory in sieve path - If compiled script has the exact same mtime as the source script, assume the script hasn't changed (changed "<" check to "<="). - Unfold multiline headers before comparing them. - Improved error logging.

1 0

[Dovecot] deliver exits with status 89 on some but not all mails of a batch
by Patrick Nagel 16 May '08

16 May '08

Hi, I'm trying to get dovecot's LDA 'deliver' to deliver mails that come in through a postfix daemon on the same box. I'm talking about dovecot version 1.0.rc15 (on CentOS 5 as Linux-VServer guest on a CentOS 5 host). Configuration ------------- # /etc/dovecot.conf ssl_cert_file: /etc/pki/selfmade/server.crt ssl_key_file: /etc/pki/selfmade/server.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login verbose_proctitle: yes mail_extra_groups: mail mail_location: maildir:~/Maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: verbose: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: dovecot group: dovecot dovecot-ldap.conf looks like this: uris = ldap://dbserver dn = cn=dovecot,ou=services,dc=company,dc=net dnpass = secret ldap_version = 3 base = ou=people,dc=company,dc=net scope = onelevel user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%n)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = LDAP-MD5 postfix has mailbox_transport set to dovecot, and master.cf contains the following: dovecot unix - n n - - pipe flags=DRhu user=fry:fry argv=/usr/libexec/dovecot/lda/deliver -d ${recipient} Problem ------- When a lot of mails come in 'at the same time', for example because an employee mailed all other (local) employees, the following happens: Some mails are being delivered as advertised, but on some mails, deliver exits with status 89 and the message bounces. Here is a (postfix) log that illustrates the problem. I replaced all receivers with 'xy', but they are in fact all different. May 13 17:58:32 mail1 postfix/smtpd[28164]: connect from unknown[192.168.0.103] May 13 17:58:32 mail1 postfix/smtpd[28164]: 1D6508FD93FF: client=unknown[192.168.0.103] May 13 17:58:33 mail1 postfix/cleanup[28165]: 1D6508FD93FF: message-id=<200805131758288906193(a)company.net> May 13 17:58:33 mail1 postfix/qmgr[27255]: 1D6508FD93FF: from=<zz(a)company.net>, size=1613090, nrcpt=31 (queue active) May 13 17:58:33 mail1 postfix/smtpd[28164]: disconnect from unknown[192.168.0.103] May 13 17:58:33 mail1 postfix/pipe[28169]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=1.9, delays=1.5/0/0/0.35, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:33 mail1 postfix/pipe[28299]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=1.9, delays=1.5/0.02/0/0.34, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:33 mail1 postfix/pipe[28168]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=1.9, delays=1.5/0/0/0.35, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:33 mail1 postfix/pipe[28298]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=1.9, delays=1.5/0.01/0/0.34, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28362]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.21/0/0.95, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:34 mail1 postfix/pipe[28304]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.1/0/1.1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28320]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.13/0/1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28311]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.12/0/1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28313]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.12/0/1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28306]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.11/0/1.1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28333]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.14/0/1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28317]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.12/0/1.1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28337]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.7, delays=1.5/0.16/0/1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28342]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.8, delays=1.5/0.17/0/1.1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:34 mail1 postfix/pipe[28368]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=2.9, delays=1.5/0.23/0/1.1, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:35 mail1 postfix/pipe[28364]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.1, delays=1.5/0.22/0/1.4, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:35 mail1 postfix/pipe[28350]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.2, delays=1.5/0.19/0/1.5, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:35 mail1 postfix/pipe[28376]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.3, delays=1.5/0.26/0/1.6, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:35 mail1 postfix/pipe[28375]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.3, delays=1.5/0.25/0/1.6, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:35 mail1 postfix/pipe[28334]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.3, delays=1.5/0.15/0/1.7, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:35 mail1 postfix/pipe[28347]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.3, delays=1.5/0.18/0/1.6, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:35 mail1 postfix/pipe[28372]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.3, delays=1.5/0.24/0/1.6, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:35 mail1 postfix/pipe[28355]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.5, delays=1.5/0.2/0/1.7, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:35 mail1 postfix/pipe[28340]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=3.5, delays=1.5/0.17/0/1.8, dsn=2.0.0, status=sent (delivered via dovecot service) May 13 17:58:36 mail1 postfix/pipe[28366]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4, delays=1.5/0.23/0/2.2, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:36 mail1 postfix/pipe[28325]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4.2, delays=1.5/0.13/0/2.5, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:36 mail1 postfix/pipe[28323]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4.2, delays=1.5/0.13/0/2.5, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:36 mail1 postfix/pipe[28330]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4.2, delays=1.5/0.14/0/2.5, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:36 mail1 postfix/pipe[28359]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4.3, delays=1.5/0.2/0/2.5, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:36 mail1 postfix/pipe[28354]: 1D6508FD93FF: to=<xy(a)city.company.net>, orig_to=<xy(a)company.net>, relay=dovecot, delay=4.4, delays=1.5/0.19/0/2.6, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/lda/deliver") May 13 17:58:51 mail1 postfix/smtp[28292]: 1D6508FD93FF: to=<xy(a)company.net>, relay=10.10.0.1[10.10.0.1]:25, delay=20, delays=1.5/0.09/1.3/17, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 3E8611881EB) May 13 17:58:52 mail1 postfix/cleanup[28160]: F0CE98FD9453: message-id=<20080513095851.F0CE98FD9453(a)mail1.city.company.net> May 13 17:58:52 mail1 postfix/qmgr[27255]: F0CE98FD9453: from=<>, size=7408, nrcpt=1 (queue active) May 13 17:58:52 mail1 postfix/bounce[28379]: 1D6508FD93FF: sender non-delivery notification: F0CE98FD9453 May 13 17:58:52 mail1 postfix/qmgr[27255]: 1D6508FD93FF: removed Does anybody have an idea what could cause this behaviour? How to debug? Patrick. -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 5427 7799 x 826 Fax: +86 (21) 6485 0071 PGP key: https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005

2 7

[Dovecot] Dovecot dying when deliver is called
by MyGoddess 15 May '08

15 May '08

Hello, I run a debian etch server with the mail services configured like their: http://workaround.org/articles/ispmail-etch/ It worked during month but of the last upgrade it doesn't work anymore when postfix calls deliver. dovecot version is 1.0.rc15. I don't remember which was the previous version. There is no error accessing dovecot in any other way. Here my configuration: # /etc/dovecot/dovecot.conf log_path: /var/log/dovecot_err.log info_log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 pop3s imap imaps login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n mail_debug: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap):You can find a copy of the pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=1004 gid=1005 home=/home/vmail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail I am not able to get a coredump. You can find a copy of the error mail attached. I didn't get any message from log files. If someone have any clue, I will helping. Regards, Pierrick Caillon

3 5

[Dovecot] moving folders bug - rc4
by Anil 15 May '08

15 May '08

I am fairly new to dovecot... I had a user who in outlook tried to move one of the folders into another folder but it crapped out. User tried to move "Djans*" folders into Koi folder. The subscription seems to show the folder move but the actual data is still under ".ClickEats.Clients.Djans" instead of ".ClickEats.Clients.Koi.Djans*. How do I fix this? Thanks. root@the:/apps/mail/clickeats.com/juliam/Maildir# grep -i djan subscriptions ClickEats.Restaurants.Djan's ClickEats.Clients.Koi.Djans.Online Orders ClickEats.Clients.Koi.Djans root@the:/apps/mail/clickeats.com/juliam/Maildir# ls -a |grep -i djan .ClickEats.Clients.Djans .ClickEats.Clients.Djans.Online Orders .ClickEats.Restaurants.Djan's root@the:/apps/mail/clickeats.com/juliam/Maildir#

2 1

[Dovecot] Automounted home dirs not working
by Roy McMorran 15 May '08

15 May '08

I'm testing Dovecot as a possible replacement for UW. In my environment the home directories are automounted via NFS from a NetApp. In general this works fine, but Dovecot isn't picking up the automounted directories. Consider the case of Arthur Dent, test user: May 12 10:30:24 testbed dovecot: [ID 107833 mail.info] imap-login: Login: user=<adent>, method=PLAIN, rip=xxx.xxx.xxx.242, lip=xxx.xxx.xxx.242, secured May 12 10:30:24 testbed dovecot: [ID 107833 mail.error] IMAP(adent): mkdir_parents(/home/adent/Mail) failed: No such file or directory May 12 10:30:24 testbed dovecot: [ID 107833 mail.error] IMAP(adent): Mail storage creation failed with mail_location: mbox:/home/adent/Mail:INBOX=/var/mail/adent May 12 10:30:24 testbed dovecot: [ID 961074 mail.error] child 21816 (imap) returned error 89 (if however I make sure that /home/adent is mounted at the server (eg. cd /home/adent) prior to starting the mail client this error does not occur) Why isn't the automount succeeding? This is Dovecot Version 1.0.13. I'm running under Solaris 10. Thanks! Roy PS: [root@testbed][ /var/log ]# dovecot -n # 1.0.13: /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/imapd.pem ssl_key_file: /etc/ssl/private/imapd.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login verbose_proctitle: yes mail_privileged_group: mail mail_location: mbox:~/Mail:INBOX=/var/mail/%u mmap_disable: yes dotlock_use_excl: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu auth default: mechanisms: plain login passdb: driver: pam passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /etc/dovecot-ldap.conf -- Roy McMorran Systems Administrator MDI Biological Laboratory mcmorran(a)mdibl.org

3 7

Re: [Dovecot] Time moved backwards
by Eugene 15 May '08

15 May '08

Hi people, > From: Adam McDougall <mcdouga9(a)egr.msu.edu> > I would just like to mention a circumstance that happened to me this > Sunday. We had a total power outage in our building, longer than our > UPS's could last and we don't have a generator for servers (nor is it > economical or needed). When the power came back on, my local NTP server > came on at the same time as my mail servers, as well a majority of my > other servers. My servers tried to step their time to be in sync with > my local NTP server, which was still busy trying to sync itself with > outside sources, which takes a while, so my mail servers did not get an > answer. Later, dovecot died because the time finally synced, and I > found out why pretty quick (have seen this before) but this was an > unusual situation. > > My point is, we had an unusual circumstance, and even though I've taken > steps to have my mail servers sync their time at boot and run ntpd > afterwards, there are some circumstances in which this is not enough, > and dovecot still died. Its not always because someone was lazy about > their time setup. My point exactly. It's amazing how some people are quick to ramble about someone else's administrative incompetence without taking time to read the situation. (One person even suggested hacking the dovecot startup script to run ntpdate -- useless as ntpd already occupies the ports). Fact is, ntpd can take unpredictable delay before the initial time-step. Delay that can't be controlled, and it would be unreasonable to delay starting mail services until it is guaranteed to complete. Then, dovecot dies, and admin (who is not always immediately available) has to start it manually anyway (especially as it is not clear what to do with possibly unsynced timestamps) -- only after the unnecessary downtime. So, the question is: why on earth can't we add a single line of code to dovecot to restart itself after terminating? Kind of reminds me of the "fsck_y_enable=YES" option in rc.conf. Without it, if fsck does not like someting during reboot, the server would just sit there in single-user prompt, waiting for (expensive) console operations. Best wishes Eugene

5 6

Re: [Dovecot] thunderbird sane config (OT)
by Moser 15 May '08

15 May '08

rosenfield.albert(a)gmail.com schrieb: > The simplest approach in my situation seems to be the XPI one, where > users can install an XPI into Thunderbird and get a template that > requires only entering username and password. > > Haven't figured how to put the CA certificate that Dovecot uses for > SSL IMAP into the XPI for installation into Thunderbird's certificate > store, but things are definitely improving :-). Isn't this one click at accessing the server the first time!? "Accept this certificate permanently"? But if you figured out, how to add it, let me know! :) Hans

2 1

[Dovecot] Allow_nets + MySQL failing when using range notation
by Javier García 15 May '08

15 May '08

Hello all, I am testing my dovecot installation in order to restrict access via POP3 for IPs outside my network. I have read and understood the instructions in the wiki and I have reached a configuration that works ONLY when single IPs are listed in allow_nets but not when ranges in the notation x.x.x.x/y are listed. Some examples should be more explanatory. I am using 1.0.rc15 patched as for last week as distributed in Debian etch. First of all, everything related to this is stored in a MySQL database, here is my password query: password_query = SELECT u.password as password, t.allow_nets as allow_nets FROM users u, access_type t WHERE u.ID_access_type = t.ID_access and ( t.%Ls = 1 ) and u.mail = '%u' This one should validate all mail addresses when the protocol used is marked as 1 in table access_type and when the allow_nets value in this same table contains the IP used for the access request. The, if access_type looks like: ID_access pop3 imap allow_nets 3 0 1 10.34.128.0/23, 10.34.133.0/24, 192.168.0.0/24 users with ID_access=3 fail to login by either pop3 (normal, value is 0) or imap. Here is the corresponding excerpt from dovecot.log: dovecot: 2008-03-31 11:29:04 Info: auth-worker(default): sql(user(a)domain.com,10.34.133.104): query: SELECT u.password as password, t.allow_nets as allow_nets FROM users u, access_type t WHERE u.ID_access_type = t.ID_access and ( t.imap = 1 ) and u.mail = 'user(a)domain.com' dovecot: 2008-03-31 11:26:39 Info: auth-worker(default): auth(user(a)domain.com,10.34.133.104): allow_nets: Matching for network 192.168.0.0/24 dovecot: 2008-03-31 11:26:39 Info: auth-worker(default): auth(user(a)domain.com,10.34.133.104): allow_nets: Matching for network 10.34.128.0/23 dovecot: 2008-03-31 11:26:39 Info: auth-worker(default): auth(user(a)domain.com,10.34.133.104): allow_nets: Matching for network 10.34.133.0/23 dovecot: 2008-03-31 11:26:39 Info: auth-worker(default): passdb(user(a)domain.com,10.34.133.104): allow_nets check failed: IP not in allowed networks but if it looks like ID_access pop3 imap allow_nets 3 0 1 10.34.133.105, 10.34.133.104 then access is allowed by IMAP dovecot: 2008-03-31 11:34:01 Info: auth-worker(default): sql(user(a)domain.com,10.34.133.104): query: SELECT u.password as password, t.allow_nets as allow_nets FROM users u, access_type t WHERE u.ID_access_type = t.ID_access and ( t.imap = 1 ) and u.mail = 'user(a)domain.com' dovecot: 2008-03-31 11:34:01 Info: auth-worker(default): auth(user(a)domain.com,10.34.133.104): allow_nets: Matching for network 10.34.133.105 dovecot: 2008-03-31 11:34:01 Info: auth-worker(default): auth(user(a)domain.com,10.34.133.104): allow_nets: Matching for network 10.34.133.104 dovecot: 2008-03-31 11:34:01 Info: auth(default): client out: OK 1 user=user(a)domain.com while POP3 still disallowed as expected: dovecot: 2008-03-31 11:34:25 Info: auth-worker(default): sql(user(a)domain.com,10.34.133.104): query: SELECT u.password as password, t.allow_nets as allow_nets FROM users u, access_type t WHERE u.ID_access_type = t.ID_access and ( t.pop3 = 1 ) and u.mail = 'user(a)domain.com' dovecot: 2008-03-31 11:34:25 Info: auth-worker(default): sql(user(a)domain.com,10.34.133.104): unknown user So, is there a bug related to the IP class notation or am I doing something wrong? I have tried to leave a single class (10.34.133.0/24), to explicitly erase any spaces after the commas, but nothing of these worked. Also, note that using 0.0.0.0/0 behaves as expected, this is, access for any IP is allowed. Thanks in advance, Javier

3 8