January 2011 - dovecot

[Dovecot] Problems with dovecot 2.0, sieve and mdbox
by Patrick Westenberg 13 Mar '11

13 Mar '11

Hi guys, I tried to use a global sieve skript to sort spam mails into a subfolder of INBOX. I´m using mdbox. The log shows that the script is called and executed but it is not able to find or create the mailbox: Sep 4 15:18:55 mercury dovecot: lmtp(6237, mail(a)steulerfliesen.de): Debug: Namespace : Permission lookup failed from /var/mail/steulerfliesen.de/mail/mdbox/mailboxes/Spamverdacht Sep 4 15:18:55 mercury dovecot: lmtp(6237, mail(a)steulerfliesen.de): Debug: Namespace : Using permissions from /var/mail/steulerfliesen.de/mail/mdbox: mode=0700 gid=-1 Sep 4 15:22:37 mercury dovecot: lmtp(6261, mail(a)steulerfliesen.de): Debug: Namespace : Permission lookup failed from /var/mail/steulerfliesen.de/mail/mdbox/mailboxes/INBOX.Spamverdacht Sep 4 15:22:37 mercury dovecot: lmtp(6261, mail(a)steulerfliesen.de): Debug: Namespace : Using permissions from /var/mail/steulerfliesen.de/mail/mdbox: mode=0700 gid=-1 My skript looks like this: require "fileinto"; if header :contains "X-Spam-Flag" "YES" { fileinto "Spamverdacht"; } I also tried: require "fileinto"; if header :contains "X-Spam-Flag" "YES" { fileinto "INBOX.Spamverdacht"; } How can I fix this? Regards Patrick

5 7

[Dovecot] dovecot 1.2.3: TB fails to unsubscribe folder after deletion
by Max Dittrich 07 Mar '11

07 Mar '11

Hi, I'm running dovecot 1.2.3 with "imap_client_workarounds = tb-extra-mailbox-sep" and noticed that after deleting a folder (moving to Trash and emptying it on exit) that folder in Trash still keeps subscribed. I think the reason for that behavior is that the call for mailbox_list_set_subscribed() in imap/cmd-subscribe.c (line 84) is fed with the original mailbox name and not the stripped version in verify_name. Assigning verify_name to mailbox in the workaround-conditional fixes this issue for me. I'm not very familiar with C programming but while tracing cmd_subscribe_full() I stumbled upon another thing. In mail_namespace_find_mask() (lib-storage/mail-namespace.c at line 413) mailbox is reassigned with a local string (not t_strduped). I think this might be a problem when mailbox is dereferenced after returning from that function?! .max

3 10

[Dovecot] Multiple Concurrent IMAP Connections For Same User
by Nigel Webber 05 Mar '11

05 Mar '11

Hi I've been using courier for some time, but have just built a new box and am using dovecot (V1.2.9), Ubuntu 10.04LTS. I have a question regarding multiple concurrent imap connections and how to get dovecot to behave in the same way that courier does. I have searched the wiki, but find little relevant to my specific issue. Courier-Imap Behaviour If I have thunderbird pointed at the 'Inbox' folder via IMAP, then connect another IMAP client to the same mail account (in this case an iPhone), and then delete an email using the iphone, then after a couple of seconds, the inbox shown by Thunderbird updates, removing the now deleted email. It does this without my having to touch Thunderbird. Dovecot behaviour Performing the same test on a different mailbox, this time hosted via Dovecot, I again see the two views, one in Thunderbird and one on the iPhone, but when I delete the email on the iPhone, the change is not reflected in the view on Thunderbird. If I select the email on Thunderbird, then it has no content. If I restart thunderbird, the deleted email is still shown. I have to delete (the already deleted) the email also in thunderbird before it finally dissapears. How can I get the courier behaviour where the inbox in one email client automagically reflects the changes made to that inbox in another client? If I am better sticking to Courier to get this functionality, thats fine, but if I can configure the behaviour I desire and still retail the benefits of dovecot then thats even better! Kind Regards Nigel

7 12

[Dovecot] expire plugin and sieve
by cvb＠kruemel.org 03 Mar '11

03 Mar '11

Hi. I am running dovecot 1.2.9 here, allowing users to filter their mails with the sieve plugin, and am using sieve to move mail tagged as probably spam into the spam folder. I'm now looking to get the expire plugin working as well. It does work as described in the wiki: Once I manually move messages into other folders, the mysql database is filled with entries. However, the combination of sieve and expire does not seem to be working: When sieve moves messages into a folder, no entry is created in the database. Don't these plugins work together, or did I misconfigure something? # dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-27-server x86_64 Ubuntu 10.04.1 LTS fuse.glusterfs log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/dovecot/imapd.pem ssl_key_file: /etc/dovecot/imapd.pem disable_plaintext_auth: no 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 login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_user: postfix login_process_per_connection: no login_process_size: 128 first_valid_uid: 113 mail_privileged_group: mail mail_location: maildir:/home/vmail/%Ld/%Ln:INDEX=/var/indexes/%u mail_debug: yes mail_nfs_storage: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): expire mail_plugins(imap): expire mail_plugins(pop3): expire mail_plugins(managesieve): 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 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail 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): managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(pop3): bytes=%i/%o managesieve_logout_format(managesieve): bytes ( in=%i : out=%o ) namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)example.com mail_plugins: expire mail_plugins: sieve auth default: mechanisms: plain login user: nobody verbose: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%Ld/%Ln allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: root master: path: /var/run/dovecot/auth-master mode: 438 user: vmail group: vmail plugin: sieve: /home/vmail/%Ld/%Ln/.dovecot.sieve sieve_global_path: /home/vmail/globalsieverc sieve_dir: ~/sieve sieve_global_dir: /var/lib/dovecot/sieve/global/ expire: INBOX.Trash 7 INBOX.Mailing-Lists.* 30 INBOX.Spam 14 expire_dict: proxy::expire dict: expire: mysql:/etc/dovecot/dovecot-dict-expire.conf Thanks, Christian

2 2

[Dovecot] Smart IMAP proxying with imapc storage
by Timo Sirainen 28 Feb '11

28 Feb '11

I just committed a very early initial implementation of "imapc" storage backend to v2.1 hg: http://hg.dovecot.org/dovecot-2.1 You can't really do anything except open INBOX and read mails from it, so it's currently only intended for initial testing. It sucks in many ways right now, but I'll be improving it. The idea is that you could set for example: mail_location = imapc:imap.gmail.com And then Dovecot could act as a proxy to gmail. It won't actually work currently with gmail, because there's no SSL support for outgoing connections. Currently index files are forcibly disabled, but it would be easy to enable them, allowing Dovecot to do caching locally to improve performance. In future perhaps it will also support caching message headers/bodies to avoid unnecessary traffic. Besides the mail_location setting, you'll need to also forward the user's password to imap process in "pass" userdb extra field. How to do that depends on what passdb/userdb you're using. While testing you could simply set a static password: plugin { pass = yourpassword }

6 16

[Dovecot] Rewrite the mailbox copy functions works in imap but don't work in doveadm import command
by Alex Baule 22 Feb '11

22 Feb '11

Hi Timo !! I rewrite the copy function from mailbox (using a plugin) My rewrite is like this: static int emexis_antispam_copy(struct mail_save_context *ctx, struct mail *mail){ struct mailbox *box = ctx->transaction->box; union mailbox_module_context *zbox = EMEXIS_CONTEXT(box); struct mail_private *_mail = (struct mail_private *)mail; union mail_module_context *zmail = EMEXIS_MAIL_CONTEXT(_mail); struct istream *input; const char *headerFile; char *bodyFile; int fd; int increment; ......Do some stuffs and verifications OK.... // GETTING THE FILE TO READ SOME STUFF FROM HEADER. if (zmail->super.get_stream(mail, NULL, NULL, &input) >= 0){ i_warning("GET STREAM COPY OK..."); }else{ i_warning("GET STREAM COPY NOT OK..."); } // REALLY COPY EMAIL copyret = zbox->super.copy(ctx, mail); } OK, when i use the IMAP , using a client and copy a email, it's works fine. But, when i use a doveadm import command, the part "(zmail->super.get_stream(mail, NULL, NULL, &input) >= 0)" fails, with no error message, only a segfault.... doveadm[14980]: segfault at 9c ip b7698000 sp bf83d7d0 error 4 in libdovecot.so.0.0.0[b7663000+6d000] doveadm[14983]: segfault at 9c ip b7661000 sp bf9c9ee0 error 4 in libdovecot.so.0.0.0[b762c000+6d000] doveadm[14986]: segfault at 9c ip b75b3000 sp bfcd82e0 error 4 in libdovecot.so.0.0.0[b757e000+6d000] doveadm[14989]: segfault at 9c ip b7684000 sp bfa5d3c0 error 4 in libdovecot.so.0.0.0[b764f000+6d000] There is difference between imap using a client , and doveadm import command ? If have some difference, can i identify and do some workarround ? Tks Timo !!

2 1

[Dovecot] Can't connect to auth server
by Phill Edwards 13 Feb '11

13 Feb '11

I'm trying to phase out procmail and move to dovecot-sieve instead. It ain't proving easy. I'll describe my setup: - Centos 5.2 box with dovecot 1.1.4 and dovecot-sieve 1.1.6 from ATrpms. - A single user account is used to store all our email (the account is called maildb). - Getmail is being used to fetch the email from various ISP mailboxes. I want to deliver mail to different folders in maildb's Maildir/ depending on who the email is addressed to (the procmail recipes currently do that). - Getmail destination section looks like this: [destination] type = MDA_external path = /usr/libexec/dovecot/deliver arguments = ("-d", "maildb") allow_root_commands = true - When I run getmail I get this error in dovecot.log: deliver(maildb): May 04 22:15:26 Error: Can't connect to auth server at /var/run/dovecot/auth-master: No such file or directory It's true that I don't have a file called auth-master. I guess I should have but until I started this dovecot-sieve work it was never a problem. I have no idea what that file should look like. As I installed from binary RPMs I would have thought one would have come with the install. Can anyone help? Regards, Phill

4 6

[Dovecot] /var/mail/<user> and mail group privileges
by Michal Hlavinka 10 Feb '11

10 Feb '11

Hi Timo, I'm facing problem with mail group privileges (again), because I've heard a few complains. I was looking at old emails and list archives, but still does not know the answer. In default (fedora/rhel) setup mail group and 0660 privileges are used. This means that when mail_location = mbox:~/mail:INBOX=/var/mail/%u is used, dovecot fails with first (and only first) attempt to select inbox (imap) or login (pop3). Shouldn't mkdir and chown make together a transaction? When it fails just for first time, it confuses some admins (this is the reason why I'm getting complains (bug reports) just because missing/wrong configuration). I think it a) should work even for first connection (ignore chown failure) or b)it should not work for following connection, so the behavior should be more consistent. Also it seems unclear what configuration option is required for making this work in new dovecot versions where configuration is split to mail_privileged_group and mail_access_groups. I see that after reading documentation in 10-mail.conf, some admins expects mail_privileged_group to be enough while mail_access_group is required to prevent fchown failure. Would it be possible to explicitly mention in the config file what option is required? I can add patch with this to our rpm, but we always prefer to be as close to the upstream as possible. Thanks Michal

2 4

[Dovecot] Access rights after dsync
by Joan Moreau 10 Feb '11

10 Feb '11

Hi, It looks like the access rights are not correctly preserved after a dsync I have rwXr-X-- from my original folder (which is right) I have rwXrwXrwX in the "mirrored" fodler (which is very wrong) Not sure what cause this, but it looks like a bug Best, jm

2 1

[Dovecot] Dovecot 2.0.7 doesn't disassociate STDERR when it daemonizes.
by Virgil Champlin 10 Feb '11

10 Feb '11

At least it appears that way on my FreeBSD 8.1 system. This is probably unnoticeable in regular use but I happen to use CFengine(v2) for system configuration & monitoring. If it notices dovecot not running it tries to start it and hangs. I believe cfengine (cfagent) has created a pipe to monitor the start commmand's stderr and is waiting for this pipe to close. This never happens because the pipe has been inherited by dovecot which, in version 2, doesn't release stderr as part of its daemonization. Although cfengine could be more defensive, I believe dovecot should be disassociating from the inherited stderr. Looking at master/main.c, I see stdin, stdout & stderr being set to /dev/null in main() if they are inherited unassigned: do { null_fd = open("/dev/null", O_WRONLY); if (null_fd == -1) i_fatal("Can't open /dev/null: %m"); fd_close_on_exec(null_fd, TRUE); } while (null_fd <= STDERR_FILENO); But stderr is missing when a later dup2() is used to release any inherited values not covered by the above: if (dup2(null_fd, STDIN_FILENO) < 0 || dup2(null_fd, STDOUT_FILENO) < 0) i_fatal("dup2(null_fd) failed: %m"); Adding a dup2 for stderr to the above statement works in my simple test case but I'm unsure if there are other issues which may require delaying it. Dovecot 1.2.16 approaches this a little differently & does slightly delay the stderr dup2. The appended diff (v2.0.7) works for me but a more informed opinion might have a better suggestion. Thank you very much for your time. I just started using Dovecot and really like it. -virgil --- main.c.orig 2010-11-04 11:58:48.000000000 -0700 +++ main.c 2011-01-05 18:11:45.000000000 -0800 @@ -717,7 +717,8 @@ } if (dup2(null_fd, STDIN_FILENO) < 0 || - dup2(null_fd, STDOUT_FILENO) < 0) + dup2(null_fd, STDOUT_FILENO) < 0 || + dup2(null_fd, STDERR_FILENO) < 0) i_fatal("dup2(null_fd) failed: %m"); pidfile_path = -=-=-=-=-=-=-=-=-=-=-

2 1