- dovecot - dovecot.org

[Dovecot] imaptest.c
by sergey ivanov 02 Nov '07

02 Nov '07

Timo, can you, please, update imaptest.c to be compatible with recent 1.1 beta5 dovecot sources? -- WBR, Sergey Ivanov.

2 1

[Dovecot] v1.0.6 released
by Timo Sirainen 02 Nov '07

02 Nov '07

http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz.sig * IDLE: Interval between mailbox change notifies is now 1 second, because some clients keep a long-running IDLE connection and use other connections to actually read the mails. * SORT: If Date: header is missing or broken, fallback to using INTERNALDATE (as the SORT draft nowadays specifies). + deliver: If message begins with a "From " line, ignore it. + zlib plugin: If maildir file has a "Z" flag, open it with zlib. - CREATE: Don't assert-crash if trying to create namespace prefix. - SEARCH: Fixes to handling NOT operator with sequence ranges. - LDAP reconnection fixes - Maildir: Don't break when renaming mailboxes with '*' or '%' characters and children. - mbox: Fixed "file size unexpectedly shrinked" error in some conditions. - quota+mbox: Don't fail if trying to delete a directory. - Fixes to running from inetd

5 12

[Dovecot] "Can't sync delivery mail"
by Rich Winkel 02 Nov '07

02 Nov '07

Dovecot 1.0.3 Deliver is saying this on two specific emails. Other emails to these 2 users are going through fine. Looking at the mail headers the only thing questionable I see is: From: "AMS Publication Division"@ams.org Is this the problem? # 1.0.3: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_disable: yes shutdown_clients: 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 login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no first_valid_uid: 100 mail_extra_groups: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u:INDEX=/var/spool/dovecot_indexes/%u lock_method: flock mbox_read_locks: flock mbox_write_locks: flock 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 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 432 user: dovecot group: dovecot

2 4

[Dovecot] Bug within Authentication Caching
by Matthias Waffenschmidt 02 Nov '07

02 Nov '07

Hello, there seems to be a bug in the authentication caching code when using it in combination with username_translation (using the current version 1.0.7 on FreeBSD 6). I've set username_translation to +@:@ to allow usernames of the form test+dom.ain or test:dom.ain (historical reasons force us....). If someone has a successful login using the username test(a)dom.ain, the subsequent authentication information is read from the cache, no matter which of the 3 possible usernames the client uses the next time. But if someone has a successful login using the username test+dom.ain, the following data has or has not been found in the cache: test+dom.ain: miss test(a)dom.ain: miss test:dom.ain: hit If the first username is test:dom.ain the behaviour is the following: test:dom.ain: miss test(a)dom.ain: miss test+dom.ain: hit I've added the information if the username changes for better debugging possibilities. In practice the username is of course always the same. The complete authentication part of the tested config: auth default: cache_size: 10000 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@:+ username_translation: +@:@ verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /var/pop/%d/Accounts.passwd userdb: driver: static args: uid=70 gid=70 home=/var/emtpy It looks as if Dovecot does some wrong username translations before inserting/lookup up the data in the cache. BTW: a SIGUSR2 signal to the dovecot-auth process does not give any information as suggested in http://wiki.dovecot.org/Authentication/Caching. Please do not only answer to the list as I am not subscribed. Thanks. -- Gruss / Best regards | LF.net GmbH | fon +49 711 90074-411 Matthias Waffenschmidt | Ruppmannstr. 27 | fax +49 711 90074-33 mw(a)LF.net | D-70565 Stuttgart | http://www.lf.net

2 1

[Dovecot] Dovecot] Postfix and Dovecot Deliver LDA
by Jerry Yeager 02 Nov '07

02 Nov '07

On Nov 2, 2007, at 9:48 AM, dovecot-request(a)dovecot.org wrote: > ------------------------------ > > Message: 4 > Date: Fri, 02 Nov 2007 13:00:56 +0100 > From: spammy <spam(a)rogerp.org> > Subject: [Dovecot] Postfix and Dovecot Deliver LDA > To: dovecot(a)dovecot.org > Message-ID: <472B1178.2060200(a)rogerp.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi all, > > Having problems moving from postfix/dovecot/mysq/maildrop existing > intall to dovecot LDA > > dovecot -n > > stuff chomped out > deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Info: auth input: > gid=5000 > deliver(vaina(a)neenux.com): 2007-11-02 12:32:40 Fatal: setuid(5000) > failed: Operation not permitted > > I'm using vmail:vmail (5000:5000) for all my virtual users and postfix (snipped some more out) > > roger Hello Roger, Try this: cd to the path where the dovecot deliver app is. Then, sudo chmod u+s deliver You may or may not need to do sudo chmod g+s deliver -- probably not. This is in the Sendmail - LDA part of the docs. Recent changes to Dovecot seem to have brought this to Postfix - LDA as well. Jerry

1 0

[Dovecot] dovecot + LDAP + SASL?
by hadmut＠danisch.de 02 Nov '07

02 Nov '07

Hi, I would like to setup an IMAP server with SASL and LDAP support. As far as I can see dovecot supports SASL and LDAP, but not the way I need it. If I understand dovecot correctly, it has it's own set of SASL mechnisms and uses the LDAP server just to store the plaintext password. In case of authentication dovecot fetches the plaintext password from LDAP and then performs the SASL steps internally. I need to support proprietary SASL mechanisms built into an LDAP server, which are not based on just a single password. So is there a way to configure dovecot to just pass SASL through to LDAP, allowing the IMAP client to talk SASL with the LDAP server through dovecot? regards Hadmut

2 1

[Dovecot] Successful experience with auth_winbind module
by Dmitry Butskoy 02 Nov '07

02 Nov '07

Hi, Recently the support of Samba's ntlm_auth helper was added to dovecot-auth (mech-winbind.c etc.). It is alrready in 1.1, the patch for 1.0 is here: http://dovecot.org/patches/1.0/dovecot-1.0.3-winbind.patch . It allows auth against NT or AD domain. I would like to infrom all that we successfully use this new feature during 2 month and ~300 users 24x7 (an energy power company). No any failures at all! This feature allows to specify "SPA" (Secure Password Authentication) option in OE, and to avoid explicit user passwords in mail accounts. Some random notes: - In the mixed environment (both plain and ntlm methods in use), you have to specify: mechanisms = plain ntlm login i.e. "ntlm" before "login". When sending mails, OE just catch first seen and try to use it, even if you specify to use SPA in the mail account preferences. - It seems that MS Outlook requires the specifying of password even when SPA is in effect - When OE has several identities, and one of the identities has SPA for SMTP set (outgoing mail), it wins over all another identities. - "The Bat" mailer supports NTLM for reading, not sending, and requires password too. Regards, Dmitry Bustkoy http://www.fedoraproject.org/wiki/DmitryButskoy P.S. We use NTLM only, GSS-SPNEGO still not tested.

1 0

Re: [Dovecot] Dovecot push imap/imap notify support?
by Alan Ferrency 02 Nov '07

02 Nov '07

Mart Pirita <sysadmin(a)e-positive.ee> wrote: > Tried search, no luck, does the Dovecot include push imap/imap notify support? If you're looking for something iPhone-compatible, then "no." Theirs is a proprietary system which from what I've read, seems to use SMS in combination with IMAP. Wacky. (If you aren't talking about iPhone compatibility, I'm less knowledgeable, but dovecot does support IDLE-style "imap push" style notification.) Alan Ferrency

5 4

[Dovecot] mail-sql.tar.gz: missing mailbox-list-private.h
by Paolo 02 Nov '07

02 Nov '07

hi, I'm trying to compile with plugin in subject, but I get this error: In file included from mail-sql-plugin.c:4: sql-storage.h:5:34: mailbox-list-private.h: No such file or directory In file included from mail-sql-plugin.c:4: sql-storage.h:26: error: field `module_ctx' has incomplete type make[5]: *** [mail-sql-plugin.lo] Error 1 there's no such mailbox-list-private.h in the whole src tree, though seems it should be in the sql-plugin tarball. Is it in 1.1? thanks -- paolo GPG/PGP id:0x1D5A11A4 - 04FC 8EB9 51A1 5158 1425 BC12 EA57 3382 1D5A 11A4

2 2

[Dovecot] mail_location and master_user rel 1.0.x
by Robert Heller 02 Nov '07

02 Nov '07

login me(a)mymail.net*theboss thebossespwd this is a great piece of software, but it has some frustrating issues. i have included my two configurations below, just FYI. the one (older) system is 1.0rc7 on mandriva 2007.0 and postfix 2.3.3 and amavisd and spamassassin and using a maildir configuration the newer system is 1.0.5 (soon to be 7) on mandriva 2008.0 and postfix 2.4.5 amavisd and spamassassin and using a maildir configuration first, i followed the instructions in this document http://wiki.dovecot.org/Authentication/MasterUsers to the letter and it works for neither the old server nor the new. specifically i was using the first example configuration. all i ever got was: Connected to mail.mailserver.com Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS STARTTLS AUTH=LOGIN AUTH=PLAIN AUTH=DIGEST-MD5] Dovecot ready. login him(a)mailserver.com*theboss thebossespwd login BAD Error in IMAP command received by server. and the auth_debug information was completely useless. if someone goes to the trouble of writing great examples they really should test to make sure they actually work. secondly: this configuration on the old server (1.0rc7) works fine: ## Dovecot 1.0 configuration file base_dir = /var/lib/dovecot protocols = imap pop3 imaps log_path = /var/log/dovecot/error.log info_log_path = /var/log/dovecot/info.log first_valid_uid = 60000 last_valid_uid = 60000 first_valid_gid=15 last_valid_gid=15 default_mail_env = maildir:/var/spool/mail/%d/%u mailbox_check_interval = 60 maildir_copy_with_hardlinks = yes mbox_locks = fcntl umask = 0077 auth default { mechanisms = plain digest-md5 user = dovecot passdb pgsql { /etc/dovecot/dovecot-pgsql.conf } userdb pgsql { /etc/dovecot/dovecot-pgsql.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = postfix group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = mail } } } but the same configuration on the newer version 1.0.5 does not work, the problem being in mail location (note changed from default_mail_location to mail_location). so i had to make a number of changes... ## Dovecot configuration file base_dir = /var/lib/dovecot/ protocols = imap pop3 imaps disable_plaintext_auth = no log_path = /var/log/dovecot/error.log info_log_path = /var/log/dovecot/info.log ssl_cert_file = /etc/pki/tls/certs/dovecot.pem ssl_key_file = /etc/pki/tls/private/dovecot.pem login_dir = /var/lib/dovecot/login mail_location = maildir:/var/spool/mail/%d/%n: namespace private { prefix = location = maildir:/var/spool/mail/%d/%n inbox = yes } mail_extra_groups = mail first_valid_uid = 60000 last_valid_uid = 60000 first_valid_gid=15 last_valid_gid=15 maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = yes mbox_read_locks = fcntl mbox_write_locks = fcntl protocol imap { login_greeting_capability = yes } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = postmaster(a)example.com } auth default { mechanisms = login plain digest-md5 passdb sql { args = /etc/postfix/mysql/dovecot.conf } userdb sql { args = /etc/postfix/mysql/dovecot.conf } socket listen { master { path = /var/lib/dovecot/auth-master mode = 0660 user = nobody group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = mail } } } dict { } plugin { } or from the dovecot -n command: # 1.0.5: /etc/dovecot.conf base_dir: /var/lib/dovecot/ log_path: /var/log/dovecot/error.log info_log_path: /var/log/dovecot/info.log protocols: imap pop3 imaps ssl_cert_file: /etc/pki/tls/certs/dovecot.pem ssl_key_file: /etc/pki/tls/private/dovecot.pem disable_plaintext_auth: no login_dir: /var/lib/dovecot/login login_executable(default): /usr/lib64/dovecot/imap-login login_executable(imap): /usr/lib64/dovecot/imap-login login_executable(pop3): /usr/lib64/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no first_valid_uid: 60000 last_valid_uid: 60000 first_valid_gid: 15 last_valid_gid: 15 mail_extra_groups: mail mail_location: maildir:/var/spool/mail/%d/%n: maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mbox_write_locks: fcntl mail_executable(default): /usr/lib64/dovecot/imap mail_executable(imap): /usr/lib64/dovecot/imap mail_executable(pop3): /usr/lib64/dovecot/pop3 mail_plugin_dir(default): /usr/share/dovecot//imap mail_plugin_dir(imap): /usr/share/dovecot//imap mail_plugin_dir(pop3): /usr/share/dovecot//pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private location: maildir:/var/spool/mail/%d/%n inbox: yes auth default: mechanisms: login plain digest-md5 passdb: driver: sql args: /etc/postfix/mysql/dovecot.conf userdb: driver: sql args: /etc/postfix/mysql/dovecot.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/lib/dovecot/auth-master mode: 432 user: nobody group: mail what i found was that i HAD to add a namespace in order to be able to define my maildir location. that was ok, /*except */that the mail_location value is no longer being used for the pop3 server mail location. so i could pick up mail using IMAP no problem, but POP wasn't working. after a number of hours i modified my SQL script with 'CONCAT(path, maildir)' so that the 'mail' path is returned complete from the sql statement: in my initial SQL statement, works on the old server and the new version 1.0.5 IMAP as: user_query = SELECT maildir AS mail, 60000 AS uid, 15 AS gid FROM mailbox WHERE username = '%u' AND active='1' but in order to get the POP3 version working i had to change it thus: user_query = SELECT CONCAT('/var/spool/mail/', maildir) AS mail, 65534 AS uid, 12 AS gid FROM mailbox WHERE username = '%u' AND active='1' one would have expected changing the SQL statement to this new format would have resulted in a location for the IMAP server now being constructed as: /var/spool/mail/var/spool/mail/domain/user but that did not happen. they both (POP & IMAP) now can find the mail and folders. like i said, thanks very much for writing this s/ware. it is great...but needs some tweaking. thanks for listening

2 1