- dovecot - dovecot.org

[Dovecot] cmusieve auto-reply and quota
by Mauro Faccenda 27 Mar '10

27 Mar '10

Hi there, I'm quite new to Dovecot, but already can tell that it is a really great work, congrats to the developers! But I'm having a little problem and couldn't figure it out how to solve. First, let me talk about my setup: I'm running Debian 5 (Lenny) with it's default Dovecot (common, pop3 and imap) packages (version 1:1.0.15-2.3+lenny1), I really would like to keep it this way unless I haven't another option. All authentication is made through a MS Active Directory and messages delivered to a virtual mailbox (/var/vmail/<domain>/<mailbox>), using Postfix as SMTP, that uses procmail (just for filtering the messages, not to deliver) that calls Dovecot's deliver like this: -- :0 w | $DELIVER -d $RECIPIENT -e -- $DELIVER points to /usr/lib/dovecot/deliver and $RECIPIENT is fed by Postfix in it's master.cf All this work great. Then I needed to enable quotas it's working as well. Here is the section that show how I've set it up: -- protocol lda { mail_plugin_dir = /usr/lib/dovecot/modules/lda mail_plugins = cmusieve quota postmaster_address = postmaster(a)do.ma.in hostname = mybox.do.ma.in auth_socket_path = /var/run/dovecot/auth-master quota_full_tempfail = no } -- I also want to run some sieve scripts just to be able to do some auto-replies (i.e. Out of office), and also it works well. Here is an example of a sieve I was using in some tests: -- require ["fileinto", "vacation"]; if header :contains "X-DSPAM-Result" "Spam" { stop; } vacation :days 1 :subject "Out of office reply" :addresses ["john.doe(a)do.ma.in", "jd(a)do.ma.in"] "I'm out of office, please contact Joan Doe instead. Best regards John Doe"; -- And as I said it works. But when I send a message to this mailbox that could exceed it's quota I get this on my logs: -- Mar 25 14:02:25 mybox postfix/pickup[21407]: 68D1DA82F: uid=103 from=<> Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): msgid=<4BAB9728.6000601(a)other.do.ma.in>: sent vacation response to <faccenda(a)other.do.ma.in> Mar 25 14:02:25 mybox postfix/cleanup[22119]: 68D1DA82F: message-id=<dovecot-1269536545-332912-0(a)do.ma.in> Mar 25 14:02:25 mybox postfix/qmgr[17299]: 68D1DA82F: from=<>, size=623, nrcpt=1 (queue active) Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): msgid=<4BAB9728.6000601(a)other.do.ma.in>: save failed to INBOX: Quota exceeded Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): sieve runtime error: Keep: Generic Error Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): sieve_execute_bytecode(/var/vmail/do.ma.in/john.doe/.dovecot.sievec) failed Mar 25 14:02:25 mybox deliver(john.doe(a)do.ma.in): msgid=<4BAB9728.6000601(a)do.ma.in>: Rejected: Quota exceeded Mar 25 14:02:25 mybox postfix/pipe[22086]: 7C666A825: to=<john.doe(a)do.ma.in>, relay=procmail, delay=1.1, delays=0.39/0/0/0.68, dsn=4.3.0, status=deferred (temporary failure) -- And every time the server tries again to deliver that message it re-sends the auto-reply. Is it an undesirable behavior, isn't it? Does anyone knows how to address it? Also, I thought that that configuration (using the -e parameter to deliver) and the "quota_full_tempfail = yes" would make give an permanent error, not trying to deliver that message again. What is wrong about it? Thanks in advance,

2 1

[Dovecot] A questions about consume_results (driver-pgsql.c)
by Rainer Weikusat 27 Mar '10

27 Mar '10

Code -------------- static void consume_results(struct pgsql_db *db) { do { if (!PQconsumeInput(db->pg)) break; if (PQisBusy(db->pg)) return; } while (PQgetResult(db->pg) != NULL); if (PQstatus(db->pg) == CONNECTION_BAD) io_remove_closed(&db->io); else io_remove(&db->io); db->querying = FALSE; if (db->queue != NULL && db->connected) queue_send_next(db); } --------------- This is the only part of the driver-pgsql.c code where a CONNECTION_BAD does not result in driver_pgsql_close being called. This will likely happen after the next query (from queue or a new one) failed because the connection was bad. Is there a reason for this?

2 2

[Dovecot] v2.0.beta4 released
by Timo Sirainen 27 Mar '10

27 Mar '10

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig I think this release is finally feature complete. There are still some bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1 should hopefully be out in a couple of weeks. After that v2.0.0 will be released after no serious bugs have been found for a couple of weeks. Major changes since beta3: - auth process now runs as $dovecot_internal_user ("dovecot") by default. Auth worker processes still run as root by default, so this won't break PAM etc, but it could break passwd-file configurations. - It can now read v1.2's dovecot.conf file. If you find that it won't read your config, let me know and I'll see about adding code to fix it. It'll log warnings about each obsolete setting it sees. The easiest way to get rid of the warnings is to just translate your old config to v2.0: doveconf -n -c old.conf > new.conf - auth passdb/userdb configuration in example-config is now a bit different .. hopefully less confusing to new people than the old one. - added support for auth settings (including passdb/userdb) inside protocol sections, so it'll affect only those protocols - mail_plugins can now be set more easily. you can have a single global mail_plugins and then add more plugins to it like protocol imap { mail_plugins = $mail_plugins imap_quota } - doveconf finally shows all settings, including all protocol, local and remote sections - doveadm quota get|recalc command added. This is a plugin (yeah, doveadm now supports plugins!), so you must have a global mail_plugins=quota setting for the command to show up. - doveadm kick user/network to kick out logged in users (by sending TERM signal to processes). This was written by Pascal Volk. - and of course tons and tons of fixes all around

6 11

[Dovecot] dovecot 2.0 fails self-tests
by Michal Hlavinka 27 Mar '10

27 Mar '10

Hi, is it expected that dovecot 2.0.beta4 pass all of it's self-tests or some failures are normal? I've tried make check and everything passed up to this test: ... message_date_parse(7) ................................................ : ok 0 / 8 tests failed test-message-decoder.c:67: Assert failed: message_decoder_decode_next_block(ctx, &input, &output) test-message-decoder.c:78: Assert failed: output.size == 3 test-message-decoder.c:84: Assert failed: output.size == 14 test-message-decoder.c:85: Assert failed: memcmp(output.data, " bar", 14) == 0 message decoder ...................................................... : FAILED 1 / 1 tests failed Regards, Michal Hlavinka

2 3

[Dovecot] CentOS yum update causing died unexpectedly
by dovecot＠corwyn.net 26 Mar '10

26 Mar '10

Running CentOS 5.x running a postfix/dovecot implementation. Dovecot 1.1.8. I just ran a full system update in my dev environment, and now I'm occasionally getting: Mar 26 07:15:43 example dovecot: auth(default): worker-server(test222(a)int.example.com,127.0.0.1): Aborted: Worker process died unexpectedly in /var/log/maillog. Any suggestions on where to look to figure out what's causing this? I don't see that error at all in the past 4 weeks of logs in production. Thanks Rick Rick Steeves http://www.sinister.net In reality nothing is more damaging to the adventurous spirit within a man than a secure future - Alexander Supertramp

2 1

[Dovecot] quota dict with mysql 4.0
by Andre Hübner 26 Mar '10

26 Mar '10

Hello, i use successfully mysql-quotasystem with dovecot 1.2.11 on different servers except for mysql 4.0 servers dovecot internally uses sql: "ON DUPLICATE KEY UPDATE" which was introduced in mysql 4.1 Is there a chance to make this statement mysql 4.0 compatible or should i update mysql? i want to avoid updating mysql because some old software is running which is not compatible to higher mysql versions. Thanks, Andre

5 6

[Dovecot] test
by total＠example.com 25 Mar '10

25 Mar '10

test

4 3

[Dovecot] outgoing mails
by Ing. Hugo Ruiz de Huidobro 25 Mar '10

25 Mar '10

Hello, I need to restrict outgoing email. I am using RedHat CentOS 4.7 and Dovecot 0.99.11 Today all users can send emails to Internet. But some people should only be able to send email to other user in this mail server. Just a few persons can send emails to the Internet. How can I do that? THANKS! Hugo

2 1

[Dovecot] Dovecot 2.0beta4
by Renaud Allard 25 Mar '10

25 Mar '10

Hello, It seems dovecot 2.0 beta4 still behave strangely without tcpwrap. I still get the errors: 2010-03-25_17:26:59.33848 Fatal: service(tcpwrap) access(/opt/dovecot/libexec/dovecot/tcpwrap) failed: No such file or directory 2010-03-25_17:27:00.36108 Fatal: service(tcpwrap) access(/opt/dovecot/libexec/dovecot/tcpwrap) failed: Permission denied It's easy to solve by touching and chmodding 0755 that file, but prod version shouldn't exhibit that behavior. Best Regards

2 1

[Dovecot] 1.2.11 nfs_flush_file_handle_cache_dir problems
by Ade Fewings 25 Mar '10

25 Mar '10

Hi chaps We're using the mbox_snarf plugin to snarf mail from /var/mail/%U to ~%U/Mail/inbox and using dotlocking on all accesses. This is on Solaris with NFS mounted home directories. We're getting a few (very few) of these for just a couple of users: Error: nfs_flush_file_handle_cache_dir: rmdir(/var/mail) failed: Device busy Which, having searched, I see some discussion of in the past, but not with 1.2. We're using: mail_privileged_group = mail For the /var/mail 'inboxes', which I thought would tackle this problem. Couple of questions, if you don't mind: 1. Does dovecot user need to be a member of the mail group? 2. Does this error message represent a real problem that needs solving? It's very strange how rare it is and that only a few select users have encountered. Full dovecot.conf below: > # 1.2.11: /usr/local/dovecot-1.2.11-b/etc/dovecot.conf > # OS: SunOS 5.10 sun4v > log_path: /usr/local/dovecot/var/dovecot.log > protocols: imap imaps pop3 pop3s > listen(default): *:143 *:10143 *:20143 *:30143 *:40143 *:50143 > listen(imap): *:143 *:10143 *:20143 *:30143 *:40143 *:50143 > listen(pop3): *:110 > ssl_listen(default): *:993 *:10993 > ssl_listen(imap): *:993 *:10993 > ssl_listen(pop3): *:995 > ssl: no > ssl_cipher_list: MEDIUM:!LOW > disable_plaintext_auth: no > shutdown_clients: no > login_dir: /usr/local/dovecot-1.2.11-b/var/run/dovecot/login > login_executable(default): > /usr/local/dovecot-1.2.11-b/libexec/dovecot/imap-login > login_executable(imap): > /usr/local/dovecot-1.2.11-b/libexec/dovecot/imap-login > login_executable(pop3): > /usr/local/dovecot-1.2.11-b/libexec/dovecot/pop3-login > max_mail_processes: 1024 > verbose_proctitle: yes > mail_privileged_group: mail > mail_location: mbox:~/Mail:INBOX=/var/mail/%u > mail_debug: yes > mmap_disable: yes > mail_nfs_storage: yes > mail_nfs_index: yes > lock_method: dotlock > mbox_read_locks: dotlock > mbox_write_locks: dotlock > mail_executable(default): /usr/local/dovecot-1.2.11-b/libexec/dovecot/imap > mail_executable(imap): /usr/local/dovecot-1.2.11-b/libexec/dovecot/imap > mail_executable(pop3): /usr/local/dovecot-1.2.11-b/libexec/dovecot/pop3 > mail_plugins: mbox_snarf > mail_plugin_dir(default): /usr/local/dovecot-1.2.11-b/lib/dovecot/imap > mail_plugin_dir(imap): /usr/local/dovecot-1.2.11-b/lib/dovecot/imap > mail_plugin_dir(pop3): /usr/local/dovecot-1.2.11-b/lib/dovecot/pop3 > auth default: > verbose: yes > debug: yes > passdb: > driver: pam > passdb: > driver: passwd > args: blocking=yes > userdb: > driver: passwd > args: blocking=yes > plugin: > mbox_snarf: ~/Mail/inbox Much appreciate your time, it has made an amazing difference here, I'm just seeking absolute perfection I think (well, mbox perfection anyway). ~~ Ade -- Centre for Advanced Software Technology Limited is a limited company registered in England and Wales. Postal Address: C.A.S.T. Limited, Technium CAST, Ffordd Penlan, Parc Menai, Bangor, Gwynedd. LL57 4HJ. Registered Number: 04473521. Registered Office: Finance Office, Bangor University, College Road, Bangor, Gwynedd. LL57 2DG. www.techniumcast.com

2 4