- dovecot - dovecot.org

[Dovecot] Clarification wanted on mail_access_groups vs. mail_privileged_group
by Mark Sapiro 07 May '08

07 May '08

I have just upgraded to dovecot 1.0.13. All the documentation I can find in the example .conf file and the NEWS and ChangeLog files seems to say that the mail_privileged_group = mail setting is all I should need to make dovecot use group mail to create dotlock files. My understanding from what I read is that mail_privileged_group is used to set the group used while creating dotlock files in (in my case) /var/spool/mail, and mail_access_groups is used to set the group used to actually access the mailbox. In my case, /var/spool/mail is group 'mail and group writable/searchable drwxrwxr-x 2 root mail 4096 May 7 08:35 /var/spool/mail and the individual mailboxes are owned by the respective users. So it seems that I would need "mail_privileged_group = mail" do be able to create dotlock files in /var/spool/mail, and that I would not need any mail_access_groups as the users can access their own mailboxes. But this doesn't work. With "mail_privileged_group = mail" and mail_access_groups unset, I get May 6 12:48:54 sbh16 dovecot: POP3(xxx): file_lock_dotlock() failed with mbox file /var/spool/mail/xxx: Permission denied Yet with "mail_access_groups = mail" and mail_privileged_group unset, it works with no problem. Is my understanding wrong? Is the documentation wrong? Is the implementation wrong? Or is there just something wierd in my case (possibly pop3_lock_session = yes)? # dovecot -n # 1.0.13: /usr/local/etc/dovecot.conf protocols: pop3 pop3s ssl_cert_file: /etc/postfix/grizz-cert.pem ssl_key_file: /etc/postfix/grizz-key.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_access_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_lock_session: yes pop3_uidl_format: %08Xu%08Xv auth default: mechanisms: plain apop login worker_max_count: 5 passdb: driver: passwd-file args: /usr/local/etc/dovecot.passwd passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2

[Dovecot] Error in dovecot-auth logging
by Antonio Casado Rodríguez 07 May '08

07 May '08

Hi, i have this in /var/log/messages May 7 09:29:59 blade25 dovecot-auth: pam_ldap: ldap_result Timed out May 7 09:29:59 blade25 dovecot-auth: pam_ldap: ldap_result Can't contact LDAP server but i defined log_path and info_log_path in dovecot.conf "dovecot -n not show different values for "protocol lda"? Regards # dovecot -n # 1.0.10: /etc/dovecot.conf log_path: /Correo/log/dovecot/dovecot.log info_log_path: /Correo/log/dovecot/dovecot.info protocols: imaps pop3 managesieve ssl_cert_file: /etc/pki/dovecot/certs/mycert.crt ssl_key_file: /etc/pki/dovecot/private/mycert.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 login_executable(managesieve): /usr/libexec/dovecot/managesieve-login first_valid_uid: 200 mail_location: maildir:%h/.. mail_executable(default): /usr/local/sbin/post-login-imap-dovecot mail_executable(imap): /usr/local/sbin/post-login-imap-dovecot mail_executable(pop3): /usr/local/sbin/post-login-pop3-dovecot mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve namespace: type: private separator: / location: maildir:%h/.. inbox: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: maildir:storage=1048576

2 1

[Dovecot] dovecot pop3 proxy with AUTH PLAIN
by Luis Barrueco 07 May '08

07 May '08

Hi, I tried as hard as I could, but I couldn't get this working. So here I come begging for help :) I need to configure dovecot to proxy some users' incoming pop3 connections to another server running the Zimbra Collaboration Suite, trying to log into zimbra via a master password. The problem I found is that zimbra only allows me to log in as a master user with the "AUTH PLAIN" mechanism, but it seems that dovecot uses the "USER.... PASS" authentication when proxying. Am I missing something? Has anyone ever tried to do the proxy+master password to zimbra? I'll post my configurations down here. I really appreciate your help- ----------------------------- dovecot version: 1.0.13 ----------------------------- "dovecot -n" output: # 1.0.13: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/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 mail_privileged_group: mail 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): %08Xu%08Xv auth default: passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd ----------------------------- /usr/local/etc/dovecot-sql.conf: driver = mysql connect = host=172.16.0.252 dbname=dovecot user=usuario_dovecot password=miclave password_query = SELECT password, 'secret_zimbra' as pass, host, destuser, 'Y' AS proxy FROM proxy WHERE user = '%u' ----------------------------- sudo tcpdump -w output_tcpdump -i eth0 dst host 172.16.0.20 and dst port 110: .........USER mnunez master ......... .........PASS secret_zimbra ----------------------------- I hope this information was helpful! Cheers.

2 1

[Dovecot] Wish: change default log_timestamp
by Steffen Kaiser 07 May '08

07 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'd suggest to change the default value of log_timestamp to something with complete date and time. Currently the string is missing the year. Maybe, %F (ISO date) would fit best. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIHz1uVJMDrex4hCIRAqIiAJsEBSsnhIZg2nGnuzPmJbiSf7VjrwCdHPTX T31joYCErSgOt5OAXa/11OM= =6cC1 -----END PGP SIGNATURE-----

2 1

[Dovecot] FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919
by Adam McDougall 07 May '08

07 May '08

This happened a while back, I was running 1.1rc3 up until today so I have no idea if it would have an effect. Sorry if its something that has been fixed. The error below was repeated many many times, I deleted the index so the user would stop getting disconnected (although I didn't hear any complaints). I have not seen this happen repeatedly in this manner to any other user yet. Apr 15 11:26:48 boomhauer dovecot: IMAP(username): FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919 Apr 15 11:26:48 boomhauer dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 5003 Apr 15 11:26:48 boomhauer dovecot: IMAP(username): Disconnected: Disconnected bytes=139/145074 Apr 15 11:27:08 boomhauer dovecot: IMAP(username): FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919 Apr 15 11:27:08 boomhauer dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 5003 Apr 15 11:27:08 boomhauer dovecot: IMAP(username): Disconnected: Disconnected bytes=139/145074 Apr 15 11:28:50 boomhauer dovecot: IMAP(username): FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919 Apr 15 11:28:50 boomhauer dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 5003 Apr 15 11:28:50 boomhauer dovecot: IMAP(username): Disconnected: Disconnected bytes=139/145074 Apr 15 11:38:02 boomhauer dovecot: IMAP(username): FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919 Apr 15 11:38:02 boomhauer dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 5003 Apr 15 11:38:02 boomhauer dovecot: IMAP(username): Disconnected: Disconnected bytes=139/145074 Apr 15 11:38:52 boomhauer dovecot: IMAP(username): FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919 Apr 15 11:38:52 boomhauer dovecot: IMAP(username): Corrupted index cache file /home/username/Maildir/dovecot/private/indexes/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 5003 Apr 15 11:38:52 boomhauer dovecot: IMAP(username): Disconnected: Disconnected bytes=139/145074 >From dovecot-uidlist: 5003 W38919 S38270 :1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 1208208981.7303_0.hill:2,S # ls -l .snapshot/*/1208208981.7303_0.hill* -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.0/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.1/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.10/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.11/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.12/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.13/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.14/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.15/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.16/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.17/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.18/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.19/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.2/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.20/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.21/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.22/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.3/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.4/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.5/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.6/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.7/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.8/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/hourly.9/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/nightly.0/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/nightly.1/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/nightly.2/1208208981.7303_0.hill:2,S -rw------- 1 username faculty 5236 Apr 14 17:36 .snapshot/nightly.3/1208208981.7303_0.hill:2,S # mv dovecot.index.cache dovecot.index.cache.broken

2 1

[Dovecot] dovecot + exim + verify recipient / reject bad recipient at SMTP time
by Peter Hudec 07 May '08

07 May '08

hello, I'm quite new to dovecot. My instalation is working good Debian Etch - exim: 4.63-17 - dovecot: 1.0.rc15 I'm using virtual user setup, with LDA delivery method. There is no database backend at this time. Is there any way to configure exim to reject non-existing user /asking dovecot lda/ at SMTP time. The standard exim configuration in ACL section do not work: --- cut --- require message = e-mail address is not valid ($local_part@$domain / $recipient_verify_failure) domains = +virtual_domains verify = recipient --- cut --- Please, have any work working example ? This setup work good witch cyrus-imap and LMTP. best regards Peter Hudec

2 1

[Dovecot] Manual thread breaking from Thunderbird
by Christian Jaeger 07 May '08

07 May '08

Hello I'm looking for a way to manually break threads apart when independent threads are mixed up, mostly by users which aren't aware that they should not be replying to existing threads when starting a new one. Since Thunderbird afaik does the threading itself, it would require a solution that actually changes the In-Reply-To header (and maybe also that other (non-standard?) header which is being sent by the M$ clients). For me modifying the actual emails on disk would be fine, i.e. renaming the In-Reply-To header to Old-In-Reply-To and such. (I'd actually *prefer* a solution that modifies the server side store, as opposed to one which keeps that info on the client side only like mutt seems to be doing.) Is there a way to do this already? Seems like a task for a dovecot plugin--or for the xexec plugin and an external perl script or some such? For triggering the renaming, a hacky solution could be to misuse labels (e.g. marking a message starred and "Later" and "Important" at the same time would trigger the modification and remove the labels). When implementing such a thing: maybe also offer a way to modify subjects (for those cases where people are using short meaningless and recurring subjects--to both help breaking up the ensuing threading as well as giving them a useful replacement), maybe as an IMAP extension or such (to be used by Thunderbird plugins (?), or by web apps). (I can code in C and Perl, but don't generally have much time.) Christian.

6 21

[Dovecot] Problem finding inbox and pam_authenticate failed problem
by Chris Beech 07 May '08

07 May '08

Testing installation of Dovecot. Log is showing two errors. Any ideas how to fix this thing??? dovecot: May 07 05:19:06 Error: auth-worker(default): pam(Yoda,127.0.0.1): pam_authenticate() failed: User not known to the underlying authentication module dovecot: May 07 05:21:48 Error: IMAP(Yoda): open() failed with mbox file /var/mail/Yoda: Permission denied Here's the dovecot.conf file # 1.1.rc4: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:10100 ssl_disable: yes 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 first_valid_uid: 1000 last_valid_uid: 5000 mail_privileged_group: mail mail_location: mbox:/var/empty:INBOX=/var/mail/%u:INDEX=MEMORY mail_debug: yes mbox_write_locks: fcntl mbox_very_dirty_syncs: 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 auth default: debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: passwd passdb: driver: shadow passdb: driver: passwd-file args: /usr/local/etc/dovecot.passdb userdb: driver: passwd userdb: driver: passwd-file args: /usr/local/etc/dovecot.passdb socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: dovecot group: mail ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

1 0

[Dovecot] Question about Maildir automatic cleanup.
by José Ildefonso Camargo Tolosa 07 May '08

07 May '08

Hi! I want to automatically delete old messages from one user's Maildir, and I was thinking on running something like this: find /home/user/Maildir/cur/ /home/user/Maildir/new/ -daystart -mtime +15 -delete but I'm not sure if by deleting messages "manually" I will break the dovecot.index* files. What do you think? Thanks! Ildefonso. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

3 2

[Dovecot] 1.07 to 1.0.13 mail_extra_groups
by Mark Sapiro 06 May '08

06 May '08

I have just upgraded from 1.0.7 to 1.0.13. I read the comments in the example .conf file and it seemed what I needed to enable dotlock access to mailboxes in /var/spool/mail (writable by 'mail' group) was "mail_privileged_group = mail" so I removed the "mail_extra_groups = mail" that I had in 1.0.7 and added "mail_privileged_group = mail", but I got errors like the following: May 6 12:48:54 sbh16 dovecot: POP3(xxx): file_lock_dotlock() failed with mbox file /var/spool/mail/xxx: Permission denied May 6 12:48:54 sbh16 dovecot: POP3(xxx): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2008-05-06 12:48:54] May 6 12:48:54 sbh16 dovecot: POP3(xxx): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 May 6 12:48:54 sbh16 dovecot: pop3-login: Login: user=<xxx>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured I then put "mail_extra_groups = mail" back in the configuration. This seems to have the effect of setting both "mail_privileged_group = mail" and "mail_access_groups = mail" as well as issuing "Warning: mail_extra_groups setting was often used insecurely so it is now deprecated, use mail_access_groups or mail_privileged_group instead" when dovecot is started. So my question is what do I need. I thought it would be just "mail_privileged_group = mail", but that doesn't work. Do I need both "mail_privileged_group = mail" and "mail_access_groups = mail" or just "mail_access_groups = mail". Also, are the comments describing these in the example .conf file correct, or are they reversed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0