- dovecot - dovecot.org

[Dovecot] postfix dovecot sieve lda
by Benny Pedersen 07 Jul '09

07 Jul '09

Hi Dovecot users i like to know how i can make dovecot not bounce when i have a sieve rule that says reject :/ my postfix is configured as in wiki with the pipe to deliver lda in dovecot, how do i solve this ? problem comes from the part that sieve vacation need to bounce to get returned mail added to vacation response, but a sieve rule with reject, accept and bounce in my setup :( postfix 2.5.5 dovecot 1.1.7 http://wiki.dovecot.org/LDA/Postfix -- xpoint

4 3

[Dovecot] AUTH PLAIN error with Thunderbird and Dovecot 1.2
by Bernhard Schmidt 07 Jul '09

07 Jul '09

Hi, a few days ago I started to get some complaints about authentication delays from Thunderbird POP3 users. After some debugging it turned out that the problem was introduced somewhere between 1.2rc3 and 1.2rc7 (1.2.0 is still affected). A session with Thunderbird 2.0.0.22 against 1.2rc3 looks like this: <<< +OK Dovecot ready. >>> CAPA <<< +OK <<< CAPA <<< TOP <<< UIDL <<< RESP-CODES <<< PIPELINING <<< STLS <<< USER <<< SASL PLAIN LOGIN <<< . >>> AUTH PLAIN <<< + >>> <base64> <<< +OK Logged in. and with 1.2.0 (same client, same config, just replaced the server binaries) <<< +OK Dovecot ready. >>> CAPA <<< +OK <<< CAPA <<< TOP <<< UIDL <<< RESP-CODES <<< PIPELINING <<< STLS <<< USER <<< SASL PLAIN LOGIN <<< . >>> AUTH PLAIN [ 2 seconds delay ] <<< -ERR Authentication failed. >>> AUTH LOGIN [ 5 seconds delay ] <<< + <base64> >>> <base64> <<< + <base64> >>> <base64> <<< +OK Logged in. In the log I see mail dovecot: auth(default): plain(?,77.2.39.xx): invalid input Does anyone have an idea? # dovecot -n # 1.2.0: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28.2 x86_64 Debian squeeze/sid ext4 protocols: imap imaps pop3 pop3s managesieve listen: *, [::] ssl_cert_file: /etc/ssl/private/pop3.mucip.net.crt ssl_key_file: /etc/ssl/private/pop3.mucip.net.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/dovecot/managesieve-login login_process_per_connection: no verbose_proctitle: yes mail_uid: 5000 mail_gid: 5000 mail_location: maildir:/var/mail/vmail/%1u/%u:INDEX=/var/cache/dovecot/%1u/%u maildir_stat_dirs: yes mail_executable(default): /usr/lib/dovecot/dovecot/imap mail_executable(imap): /usr/lib/dovecot/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/dovecot/managesieve mail_plugins(default): quota imap_quota fts fts_squat mail_plugins(imap): quota imap_quota fts fts_squat mail_plugins(pop3): mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/managesieve imap_idle_notify_interval(default): 900 imap_idle_notify_interval(imap): 900 imap_idle_notify_interval(pop3): 120 imap_idle_notify_interval(managesieve): 120 auth default: mechanisms: plain login verbose: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: path: /var/spool/postfix-mailout/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: quota: maildir quota_rule: *:storage=500M Thanks, Bernhard

2 2

[Dovecot] troubles with broken clients (iPhone) - again
by Federico Bianchi 07 Jul '09

07 Jul '09

The PC (Outlook) is accessing the mailbox via POP3, the iPhone is using IMAP; please consider we are talking about a user's home setup, so it's pretty difficult to have a more detailed report on his part (Outlook version, iPhone OS version, xDSL router type and configuration, etc.). The mail server 'dovecot -n' output is attached. The symptoms: when the Mail application is "closed" on the iPhone, Outlook still says the mailbox is in use; a Dovecot imap process is still active for that user even after a few minutes (manually killing it releases the lock, thereby leaving the inbox available for Outlook). >From the client side, there is a seemingly relevant article at http://blogs.sun.com/chienr/entry/iphone_supports_imap_idle it describes, among others, the "Settings / Mail / Auto-Check" and "Settings / General / Auto-Lock" parameters; from my point of view, however, being able to solve the problem directly on the server would be far better, and might also accomodate other broken clients we haven't seen yet: that's why I asked you whether there is a way to tell Dovecot only one POP3 or IMAP process from the same user, the latest one, can be active at the same time, closing and disconnecting all the others. Regards, and thanks a lot again for your help Federico Bianchi Dipartimento di Storia delle Arti Universita` di Pisa piazza S.Matteo in Soarta, 2 - I56127 Pisa (Italy) fax.+39-050-580128; e-mail: <f.bianchi(a)arte.unipi.it> =================================================== !DISCLAIMER!: my e-mail reflects _my_own_ opinions! ===================================================

3 3

[Dovecot] Ambiguous mail location setting
by Shawn 07 Jul '09

07 Jul '09

"Using Dovecot v1.0.alpha4 on OpenBSD 3.8 (same problem find using Dovecot v1.0.alpha3 on OpenBSD 3.7) Log output: _________________________________ dovecot: Nov 04 11:15:28 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AHl2cmlAbjN1dHJpbm4uaXQAeXVyaW6zgXRyaW1v dovecot: Nov 04 11:15:28 Info: auth(default): sql(myuser at mydomain.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot>,127.0.0.1): query: SELECT password FROM user_accounts WHERE username='myuser at mydomain.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot>' dovecot: Nov 04 11:15:28 Info: auth(default): client out: OK 1 user=myuser at mydomain.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot> dovecot: Nov 04 11:15:28 Info: auth(default): master in: REQUEST 5 32206 1 dovecot: Nov 04 11:15:28 Info: auth(default): sql(myuser at mydomain.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot>,127.0.0.1): SELECT '/var/mail/'||mailbox AS mail, uid, gid FROM user_accounts WHERE username='myuser at mydomain.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot>' dovecot: Nov 04 11:15:28 Info: auth(default): master out: USER 5 myuser at mydomain.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot> mail=/var/mail/mydomain.com/myuser uid=10001 gid=10001 dovecot: Nov 04 11:15:28 Error: imap(myuser at mydomain.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot>): Ambiguous mail location setting, don't know what to do with it: /var/mail/mydomain.com/myuser (try prefixing it with mbox: or maildir:) dovecot: Nov 04 11:15:28 Error: imap(myuser at mydomain.com <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot>): Failed to create storage with data: /var/mail/mydomain.com/myuser _________________________________ I verified that "default_mail_env" on my dovecot configuration file are "maildir:" correctly prefixed: "default_mail_env = maildir:/var/mail/%d/%n" and ... permissions of /var/mail/mydomain and /var/mail/mydomain/myuser are 2755 and owner is root:mail. I'm sure that isn't an authentication problem. I've tried some days to understand and to find over internet and here in the dovecot mailing list but I've not find a solution yet. I think it's a dovecot internal bug. Someone know what I'm talking about?" Set permissions on the mail folder to 2775 because dovecot runs as its own user and group and you need the mail file in that folder to accept writes from mail and from dovecot groups. Also in the config file dovecot.conf you need to specify if the files are maildir or mbox. They are probably mbox but try both for the error messages.

4 3

[Dovecot] libsieve compilation error on AIX 5.3
by Jonathan Siegle 07 Jul '09

07 Jul '09

Dovecot revision: 9186:f70192e7ff3c libsieve revision: 958:e86a81f4bf28 Using IBM c compiler version 8. Trying to compile libsieve(64 bit mode if it matters): "sieve-ast.c", line 302.9: 1506-045 (S) Undeclared identifier last. "sieve-ast.c", line 302.9: 1506-045 (S) Undeclared identifier result. "sieve-ast.c", line 320.9: 1506-275 (S) Unexpected text node encountered. "sieve-ast.c", line 320.9: 1506-045 (S) Undeclared identifier node. "sieve-ast.c", line 324.9: 1506-045 (S) Undeclared identifier last. "sieve-ast.c", line 324.9: 1506-045 (S) Undeclared identifier result. gmake[4]: *** [sieve-ast.lo] Error 1 Thanks, Jonathan

3 4

[Dovecot] Released Sieve v0.1.7 and ManageSieve v0.11.6 for Dovecot v1.2.0
by Stephan Bosch 07 Jul '09

07 Jul '09

Hello Dovecot users, I hereby release new versions of the Sieve packages for the recently released Dovecot v1.2.0 (Congrats Timo!). Apart from small changes to make things compile with Dovecot again, a few other bugs were fixed as well. Unfortunately, the (FreeBSD-specific) 8kb script truncation bug remains. Although it is reported for Dovecot v1.1.16, I see no reason why it should not surface in v1.2.0 as well. Any help is appreciated. Changelog Sieve v0.1.7: + Improved consistency of sieve tool documentation and fixed missing parameters in internal tool help output. + Enhanced extensions configuration, allowing to specify the enabled extensions relatively to the default (patch by Steffen Kaiser). - Forgot to initialize script execution status in Sieve plugin, causing segfaults on compile errors in specific conditions. - Fixed logging in Sieve plugin for execution of default main script (went to STDERR). Changelog ManageSieve v0.11.6: * Adjusted to changes in Dovecot regarding client idle timeout vs authentication timeout. This release now depends on Dovecot v1.2.rc6 or newer. - Fixed CRLF line breaks in compile errors (bug reported by Pascal Volk). - Corrected directory/file creation behavior with respect to mode bits and gid (bug reported by Pascal Volk). - Improved handling of script truncation bugs: connection is now closed and and error is logged (bug itself not fixed yet). - Prevented temp script name from showing up in error output. -- The releases are available as follows: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.7.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.7.tar.gz.sig ManageSieve (package + patch): http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.6.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.6.tar.gz.s… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.0-managesieve-0.11.6.diff.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.0-managesieve-0.11.6.diff.g… -- Have fun testing the new releases and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 4

[Dovecot] Dovecot-sieve version compatability
by Phill Edwards 07 Jul '09

07 Jul '09

I'm thinking of upgrading my dovecot version to 1.2 so that I can use the Dovecot sieve plugin instead of the CMU Sieve plugin. My RPM repo for dovecot is ATrpms so I could get dovecot-1.2.0-0_95.el5.i386.rpm from the bleeding ATrpms repo. Would this be compatible with dovecot-sieve-1.1.6-9.el5.i386.rpm which is in the stable repo, or would I need to find a later dovecot-sieve version somewhere? Regards, Phill

1 0

[Dovecot] Can´t deliver Mails into Subfolders with Sieve....
by Bernd Schmelter 06 Jul '09

06 Jul '09

Hello, can`t sort Mails with sieve in Subfolders. Mails only delivered in my INBOX. System: Debian Testing, Postfix, Dovecot 1.2.0 (1.2.0-0~auto+7_i386.deb), Squirrelmail + Avelsieve Postfix delivers fine in my INBOX via mailbox_command = /usr/lib/dovecot/deliver in main.cf. deliver seems not to use the existing sieve-script created and uploadet with avelsieve. Postfix delivers in maildir-format into ~/Maildir/new The Link/.dovecot.sieve --> ~/sieve/phpscript.sieve exist. dovecot -n: # 1.2.0: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-486 i686 Debian squeeze/sid protocols: imap imaps managesieve login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_location: maildir:~/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/passwd.dovecot userdb: driver: passwd plugin: sieve: ~/.dovecot.sieve sieve: ~/.dovecot.sieve sieve_storage: ~/sieve But where is my configurationserror in dovecot.conf? Benn

2 3

[Dovecot] Connecting to dovecot
by Grant Lowe 06 Jul '09

06 Jul '09

Hi All, I've got a brand new dovecot installation. I'm new to dovecot, so please be gentle :-) Anyway, I'm getting some errors when I try to connect to dovecot. I've tried searching the web and haven't been able to find a lot of information. Here's the config info: # dovecot --version 1.1.2 # dovecot -n sudo dovecot -n # 1.1.2: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: /var/mail/%u auth default: verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=vmail gid=vmail home=/var/mail/%u # Here are the errors I'm getting. dovecot: Sep 16 18:44:15 Info: imap-login: Login: user=<wfoatst>, method=PLAIN, rip=172.20.58.4, lip=172.20.8.215 dovecot: Sep 16 18:44:15 Error: IMAP(wfoatst): mail_location not set and autodetection failed: Mail storage autodetection failed with ho me=/var/mail/wfoatst Thanks!

3 3

[Dovecot] mbox sync failure2
by Alnis Morics 06 Jul '09

06 Jul '09

Hello, list, I'm new here and also new to Dovecot. On Friday evening (perhaps not the best moment...) I sent the following question but it seems to have been lost somehow: Yesterday I had to reboot my server machine and I think there was an email client connected from the LAN during the reboot which I did not notice then. Now that mailbox is no longer accessible: as soon as I try to connect, it lets me wait forever while openin the folder, and cycles endlessly this message in the logs: Jul 2 19:40:37 myhostname dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=#.#.#.#, lip=#.#.#.#, TLS Jul 2 19:40:37 myhostname dovecot: IMAP(username): unlink(/var/mail/username.lock) failed: Permission denied Jul 2 19:40:48 myhostname dovecot: IMAP(username): file mbox-sync.c: line 1372 (mbox_sync_handle_eof_updates): assertion failed: (trailer_size <= 2) Jul 2 19:40:48 myhostname dovecot: IMAP(username): Raw backtrace: imap [0x80b2081] -> imap [0x80b1f99] -> imap [0x807a536] -> imap [0x807ae71] -> imap(mbox_sync+0x422) [0x807d3c2] -> imap(mbox_storage_sync_init+0x3e) [0x807d8de] -> imap(imap_sync_nonselected+0x1c) [0x806446c] -> imap(_cmd_select_full+0xc3) [0x805be83] -> imap(cmd_select+0x19) [0x805c059] -> imap [0x805d5ef] -> imap [0x805d690] -> imap(_client_input +0x74) [0x805dd64] -> imap(io_loop_handler_run+0xf0) [0x80b7e20] -> imap(io_loop_run+0x18) [0x80b7338] -> imap(main+0x478) [0x8066388] -> /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7e36455] -> imap [0x8058561] Jul 2 19:40:48 myhostname dovecot: child 2459 (imap) killed with signal 6 (I have Debian Lenny with dovecot 1.0.15.; protocol: imaps; mailbox: mbox; lock: dotlock) I tried to add the user dovecot to the group mail and give the group mail write permission to the mailbox. The permission errors stopped appearing but everything else is still there, including .lock file and 3 imap-login processes that resume as soon as I try to kill them. There are also 2 unimportant mailboxes that still work. I can view the beginning of the "username" mailbox with mc inner viewer, but it hangs as I go to the end of file. Tried to copy the file so I could freely experiment with it but the copying hung up when it reached 87 % (the file is 1.1 GB). The copied part was unreadable. Tried to formail -ds < /var/mail/username >> /backup/usernameJul3 but with the same result. Is there a way to repair the synchronization of the mbox? Or at least a way to recover its content? ------------------------------------------------------- After that I also tried to "shutdown -F -r now" but to no effect. (filesystem is ext3) Now I'm really in trouble. Could someone, please, suggest what I could try to do to solve this? Thanks.

5 7