- dovecot - dovecot.org

[Dovecot] IMAP goes down from time to time
by Juan Felipe Estrada 20 Oct '09

20 Oct '09

Good Afternoon I´m really new at this and i don´t know if i´m posting at the right place. My problem is that our Dovecot IMAP is stopping from time to time with no info in the log, i just realize about this when our support person call me saying that the whatsup monitor is showing the IMAP4 process down. I can figure about this too by trying to get in our webmail Horde and i cannot login. Here i post my Dovecot -n command i´ll appreciate any help. /# 1.0.7: /etc/dovecot.conf protocols: imap pop3 imaps pop3s ssl_cert_file: /etc/httpd/conf/ssl.crt/unimail.uninorte.edu.co.crt ssl_key_file: /etc/httpd/conf/ssl.key/unimail.uninorte.edu.co.key ssl_cipher_list: ALL:!LOW:!SSLv2 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 mail_location: maildir:/home/vmail/%u/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/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 auth default: mechanisms: plain login cache_size: 300 cache_ttl: 600 worker_max_count: 200 passdb: driver: ldap args: /etc/dovecot-ldap.conf passdb: driver: pam userdb: driver: static args: uid=500 gid=500 home=/home/vmail/%u userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix / Thanks so much Juan Felipe Estrada Universidad del Norte Barranquilla Colombia

3 2

[Dovecot] Question about IMAP IDLE (and Palm Pre)
by Ingo Thierack 20 Oct '09

20 Oct '09

Hello, i try to understand, how it works (IDLE). Try to get it successfully work with my new Palm Pre ;-) which looks like to have a lot issues wir imap... so i'll blame not dovecot for the issues. Sent a mail, from googlemail. processed by dovecot ad 12:11. what me now confusing, is, that there in the out-log is nothing visible, I expected, to see there was sent an notification, there was a new mail. Do i miss something? After arounde 15 minutes the Palm sent a "DONE" and reconnect. then the messages was received. Regards Ingo email come in 2009-10-19 12:11:27 | dovecot: | deliver(xxxxxxx(a)ghostdive.org): sieve: msgid=<ac2e3a8f0910190311t381d9e33j99e6aa4d1e07c88a(a)mail.gmail.com>: stored mail into mailbox 'INBOX' outfile-log * OK [RAWLOG TIMESTAMP] 2009-10-19 12:09:33 <<<~~A4 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in >>> <<<* CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CH ILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH ~~A5 OK Capability completed. >>> <<<* FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk \*)] Flags permitted. * 42 EXISTS * 0 RECENT * OK [UIDVALIDITY 1252956599] UIDs valid * OK [UIDNEXT 156] Predicted next UID * OK [HIGHESTMODSEQ 132] Highest ~~A6 OK [READ-WRITE] Select completed. >>> <<<* SEARCH 124 125 126 127 128 129 130 131 132 133 134 136 137 138 139 140 141 142 144 145 146 147 148 149 150 155 ~~A7 OK Search completed (0.000 secs). >>> <<<* SEARCH ~~A8 OK Search completed (0.000 secs). >>> <<<* SEARCH ~~A9 OK Search completed (0.000 secs). >>> <<<* SEARCH ~~A10 OK Search completed (0.000 secs). >>> <<<* SEARCH 155 ~~A11 OK Search completed (0.000 secs). >>> <<<+ idling >>> * OK [RAWLOG TIMESTAMP] 2009-10-19 12:14:36 <<<* OK Still here >>> * OK [RAWLOG TIMESTAMP] 2009-10-19 12:19:36 <<<* OK Still here >>> in-log <<<~~A5 capability >>> <<<~~A6 select "Inbox" >>> <<<~~A7 UID SEARCH ALL UID 124:* >>> <<<~~A8 uid search unseen UID 124:* >>> <<<~~A9 uid search answered UID 124:* >>> <<<~~A10 uid search flagged UID 124:* >>> <<<~~A11 uid search deleted UID 124:* >>> <<<~~A12 IDLE >>> <<<DONE >>>

2 2

[Dovecot] deliver and stale NFS file handles
by Leon Meßner 20 Oct '09

20 Oct '09

Hello, since updating two of our backup mailservers from dovecot 1.1.16 to 1.2.4 i get the following errors from dovecot-deliver when receiving (smtp) mail. Oct 16 00:10:42 mail3 dovecot: deliver(user): write_full(/home/r/user/.temp.backupmail.22774.d17050a07b2108e8) failed: Stale NFS file handle Oct 16 00:10:42 mail3 dovecot: deliver(user): copy: i_stream_read() failed: Stale NFS file handle Oct 16 00:10:43 mail3 dovecot: deliver(user): msgid=<d0acb2021be1922ae2d35fbd6b09994c.squirrel(a)www.physik.tu-berlin.de>: save failed to INBOX: Internal error occurred. Refer to server log for more information. [2009-10-16 00:10:42] It nearly never happens with text/plain mails but _very_ often when mails have attachments of some different type. This is inside a 7.2-RELEASE-p2 FreeBSD jail. The NFS export is mounted from the machine that is running the jail. Locking with lockf works. Following is the output of `dovecot -n` from the mailserver. Please tell me if you need any further information. Thanks in Advance, Leon $ dovecot -n # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-RELEASE-p2 amd64 log_path: /var/log/dovecot.log protocols: imaps pop3s managesieve listen: mail3.physik.tu-berlin.de ssl_cert_file: /etc/private/backupmail.pem ssl_key_file: /etc/private/backupmail_privatekey.pem 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_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_processes_count: 6 login_max_processes_count: 256 verbose_proctitle: yes first_valid_uid: 200 first_valid_gid: 300 mail_privileged_group: mail mail_location: maildir:~/maildir mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: 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_executable(managesieve): /usr/local/libexec/dovecot/managesieve 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 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ location: mbox:~/mail list: yes subscriptions: yes lda: postmaster_address: postmaster(a)physik.tu-berlin.de log_path: info_log_path: mail_plugins: sieve quota_full_tempfail: yes sendmail_path: /usr/sbin/sendmail auth default: mechanisms: gssapi plain login username_format: %Lu krb5_keytab: /etc/mail3.krb5.keytab gssapi_hostname: backupmail worker_max_count: 120 passdb: driver: pam args: session=yes failure_show_msg=yes max_requests=100 dovecot userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/.sieve

4 4

[Dovecot] Unknown setting: driver
by Rodolfo González González 20 Oct '09

20 Oct '09

Hi, the conversion from courier was done without problems, but now I have a problem with my auth config. I followed the sql example included in the latest dovecot source, and put driver=mysql in dovecot.conf (outside any section), and now I get: --- Error: Error in configuration file /usr/local/etc/dovecot.conf line 50: Unknown setting: driver Fatal: Invalid configuration in /usr/local/etc/dovecot.conf Starting DovecotError: Error in configuration file /usr/local/etc/dovecot.conf line 50: Unknown setting: driver Fatal: Invalid configuration in /usr/local/etc/dovecot.conf --- So I'm lost... what's wrong? if I followed the example :o Then, another question: I had to go back to courier so my users still can work, but I already created the files using the migration script: do I need to rerun the migration script? or what do I need to do when I manage to fix the error above and run dovecot? Thanks.

3 2

[Dovecot] clarify 'type', 'executable' & 'path' in 2.0 master.conf?
by PGNet Dev 19 Oct '09

19 Oct '09

@2.0's master.conf, there's, e.g., service config { type= config executable =config unix_listener { path = config mode = 0666 } } can someone please explain function/usage for the 'type', 'executable' & 'path' fields? and, for any file paths, are the presumed to be _relative_ to the dovecot executable? in $PATH? can they accept full/absolute paths? thanks.

4 45

[Dovecot] Can't use string ("0") as a HASH ref while "strict refs" in use at /usr/local/sbin/courier-dovecot-migrate.pl line 300.
by Rodolfo González González 19 Oct '09

19 Oct '09

Hello, I need to migrate from courier-imap to dovecot. I'm trying to use courier-dovecot-migrate.pl to migrate the users' maildirs but I'm getting these messages: --- # courier-dovecot-migrate.pl --to-dovecot --recursive mydomain.com Testing conversion to Dovecot format Finding maildirs under mydomain.com mydomain.com/contact/./Maildir: No imap/pop3 uidlist files mydomain.com/someone/./Maildir/courierpop3dsizelist: Broken header: /1 9 Can't use string ("0") as a HASH ref while "strict refs" in use at /usr/local/sbin/courier-dovecot-migrate.pl line 300. --- The courierpop3dsizelist files have contents like this one: --- /1 9 1181869523.M278844P24357V000000000000080CI006E803B_0.email,S=1216:2, 1241 8 --- and it seems that the script is failing with all the maildirs with courierpop3dsizelist. I use courier-imap 4.6.0, access using pop3 causes no problems. Any hint on what's wrong is appreciated, thanks. Salut, Rodolfo.

2 3

[Dovecot] Detect client application
by Thu NGUYEN 19 Oct '09

19 Oct '09

Hello, Do you have any way to detect the client which is connecting to our IMAP server? I actually have an mail server which use dovecot but I just want to allow mobile device access to this server to get email, not desktop as Outlook, Thunderbird ... Thanks for your advice. -- Regards, Thu NGUYEN

4 6

[Dovecot] Dovecot deliver with AD LDAP userdb
by Mark Schaub 19 Oct '09

19 Oct '09

Good Afternoon, I have my virtual users stored in an Active Directory database. As far as mail info goes the 2 important fields are: mail (their primary email address) and otherMailbox (a multivalue attribute containing their mail aliases). Right now all email addresses belong in the same domain and there are no immediate plans to change this. If I use Postfix to do the lookups and delivery only using Dovecot for passdb Pam driver and a static userdb then everything delivers fine to mail and otherMailbox addresses. I have been working on switching over to Dovecot's deliver process in order to integrate sieve capability. I have configured userdb ldap and passdb ldap in Dovecot and have set up master and client sockets. Before I describe my problem let me show you my configuration (as I think the dovecot-ldap.conf in particular needs to be explained). Here are the important parts of dovecot.conf: auth default { socket listen { master { path = /usr/var/run/dovecot/auth-master mode = 0666 user = vmail group = vmail } client { path = /var/spool/postfix/private/auth mode = 0666 user = postfix group = postfix } } passdb ldap { args = /etc/dovecot-ldap.conf } userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap-example.conf args = /etc/dovecot-ldap.conf } and my dovecot -n: lda: postmaster_address: postmaster(a)sau24.org mail_plugins: sieve auth default: mechanisms: plain login debug: 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: 438 user: postfix group: postfix master: path: /usr/var/run/dovecot/auth-master mode: 438 user: vmail group: vmail plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve sieve_storage: ~/sieve Further, here is my dovecot-ldap.conf: hosts = delldb.sau24.org:3268 base = dc=sau24, dc=org ldap_version = 3 dn = cn=Mail User,cn=Users,dc=sau24,dc=org dnpass = secret auth_bind = yes scope = subtree user_attrs = sAMAccountName=home=/home/vmail/%$,=uid=501,=gid=501 pass_attrs = sAMAccountName=user user_filter = (&(objectclass=person)(|(sAMAccountName=%n)(mail=%n@sau24.org)(otherMailbox=%n@sau24.org))) pass_filter = (&(objectclass=person)(|(sAMAccountName=%n)(mail=%n@sau24.org)(othermailbox=%n@sau24.org))) Now, you'll notice that the user_filter and pass_filter have the domain statically placed after the mail and othermailbox attributes. This reason for this is that this ldap configuration is used for both authentication purposes and local delivery, so its not always being passed the domain info (for authentication it gets the users IP address). Since all my users are on the same domain I can statically set this here. This setup authenticates users to imap and pop (users use their sAMAccountName as their username when they log in), and pulls their correct home directory. Checking mail is not a problem at all. Further, this setup will deliver mail correctly to mail addressed to the value in the "mail" attribute. The problem seems to be in the otherMailbox attribute, it cannot lookup the users sAMAccountName based off of the otherMailbox field. Here is what it looks like in the logs for mail sent to my "mail" attribute (mark.schaub(a)sau24.org) Oct 14 12:36:19 auth(default): Info: master in: USER 1 mark.schaub(a)sau24.org service=deliver Oct 14 12:36:19 auth(default): Info: ldap(mark.schaub(a)sau24.org): user search: base=dc=sau24, dc=org scope=subtree filter=(&(objectclass=user)(|(sAMAccountName=mark.schaub)(mail=mark.schaub@sau24.org)(otherMailbox=mark.schaub@sau24.org))) fields=sAMAccountName Oct 14 12:36:19 auth(default): Info: ldap(mark.schaub(a)sau24.org): result: sAMAccountName(home=/home/vmail/%$)=/home/vmail/mschaub Oct 14 12:36:19 auth(default): Info: master out: USER 1 mark.schaub(a)sau24.org home=/home/vmail/mschaub uid=501 gid=501 Oct 14 12:36:19 deliver(mark.schaub(a)sau24.org): Info: sieve: msgid=<6b71e3a70910140936v4e8cd6fdwd847a1721a9d9786(a)mail.gmail.com>: stored mail into mailbox 'INBOX' But this is what I get when I try to send to an address listed in my otherMailbox field (tech(a)sau24.org) Oct 14 12:30:58 auth(default): Info: master in: USER 1 tech(a)sau24.org service=deliver Oct 14 12:30:58 auth(default): Info: ldap(tech(a)sau24.org): user search: base=dc=sau24, dc=org scope=subtree filter=(&(objectclass=user)(|(sAMAccountName=tech)(mail=tech@sau24.org)(otherMailbox=tech@sau24.org))) fields=sAMAccountName Oct 14 12:30:58 auth(default): Info: ldap(tech(a)sau24.org): Unknown user Oct 14 12:30:58 auth(default): Info: master out: NOTFOUND 1 As a test I tried modifying my dovecot-ldap.conf to use different fields instead of otherMailbox. Sending to some of those attributes worked, others didnt. I could use the "sn" and "givenName" attributes, but "postalCode" and "title" would give the same error as otherMailbox. My question is this: is there something wrong with my configuration or can Dovecot only query certain fields in the user_attr string? Thanks, ~ Mark

4 7

[Dovecot] Released Sieve v0.1.13 for Dovecot v1.2.6
by Stephan Bosch 19 Oct '09

19 Oct '09

Hello Dovecot users, After about a month of silence, I finally release a new version of Pigeonhole Sieve. This release fixes problems in the multiscript support and improves the body extension further towards RFC compliance. The body extension still needs work, however, since some content types still give erroneous results. Changelog Sieve v0.1.13: + Body extension: implemented proper handling of the :raw transform and added various new tests to the test suite. However, :content "multipart" and :content "message/rfc822" are still not working. + Fixed race condition occuring when multiple instances are saving the same binary (patch by Timo Sirainen). + Test suite: added support for testing multiscript execution. - Made compiler more lenient towars missing CRLF at the end of the script in a hash comment. - Body extension: don't give SKIP_BODY_BLOCK flag to message parser, we want the body! (patch by Timo Sirainen). - Fixed handling of implicit side effects for multiscript execution. - Fixed bugs in multiscript support; subsequent keep actions were not always merged correctly and implicit side effects were not always handled correctly. - Fixed a segfault bug in the sieve-test tool occuring when compile fails. - Fixed segfault bug in action procesing. It was triggered while merging side effects in duplicate actions. - Fixed bug in the Sieve plugin that caused it to try to stat() a NULL path, yielding a 'Bad address' error. The release is available as follows: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.13.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.13.tar.gz.sig Refer to http://pigeonhole.dovecot.org for more information. Have fun testing the new release and don't hesitate to notify me when there are problems. Releases for Dovecot v2.0 are still under development... Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] Convert to DBox
by Jeff Grossman 17 Oct '09

17 Oct '09

I am thinking of trying out dbox format. I am currently using maildir. Is it possible for me to switch just one user account to dbox while keeping all of my other users on maildir? If so, how would I go about doing that? Here is a copy of my dovecot -n: # 1.2.5: /usr/local/etc/dovecot.conf # OS: Linux 2.6.30-1-amd64 x86_64 Debian squeeze/sid ext3 base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/stikman-godaddy.crt ssl_key_file: /etc/ssl/private/stikman-godaddy.key 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 mail_location: maildir:/home/vmail/%u 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 lda: postmaster_address: postmaster(a)stikman.com mail_plugins: cmusieve sendmail_path: /usr/sbin/sendmail auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login username_format: %Lu passdb: driver: pam userdb: driver: passwd args: uid=vmail gid=vmail home=/home/vmail/%u socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: sieve: sieve Thanks, Jeff

2 1