August 2013 - dovecot

[Dovecot] v2.2.5 released
by Timo Sirainen 06 Aug '13

06 Aug '13

http://dovecot.org/releases/2.2/dovecot-2.2.5.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.5.tar.gz.sig So, I'm back from the first vacation I've had in about 10 years. (Well, maybe there were a few short ones.) I was planning on coding it the whole time, but looks like I didn't manage to get anything at all done. Maybe that's a good vacation?.. Anyway, I've still a few more pending things to look into, but it's been too long since v2.2.4 so here are the fixes so far. + SSL: Added support for ECDH/ECDHE cipher suites (by David Hicks) + Added some missing man pages (by Pascal Volk) + quota-status: Added quota_status_toolarge setting (by Ulrich Zehl) - director: Users near expiration could have been redirected to different servers at the same time. - pop3: Avoid assert-crash if client disconnects during LIST. - mdbox: Corrupted index header still wasn't automatically fixed. - dsync: Various fixes to work better with imapc and pop3c storages. - ldap: sasl_bind=yes caused crashes, because Dovecot's lib-sasl symbols conflicted with Cyrus SASL library. - imap: Various error handling fixes to CATENATE. (Found using Apple's stress test script.)

4 5

[Dovecot] Please HELP: how to delete all messages older than X days from the server?
by Răzvan Sandu 06 Aug '13

06 Aug '13

Hello, Would you please help me solve the following case? My (CentOS) server runs dovecot and allows both POP3 and IMAP service. Users are virtual users (no home directories), with messages stored in Maildir directories under /var/spool/mail/vhosts/example.com/username Some of them use mobile devices (without local storage space), so I must allow IMAP access, not just POP3. But the storage on the server must be for a strictly *limited* period of time. As an admin, I'm trying to force each user to: - download *locally* received messages when they arrive at the office - don't let copies of messages on the server (incoming, sent, trash, drafts, etc.) For various reasons, e-mail client configuration is not under my control (I can't rely on client configuration for implementing this). Implementing filesystem quotas is not an option because a. presently, all virtual users share same UID/GID on the server and b. administrative reasons (the "full quota" situation may occur unexpectedly and this is not tolerable in corporate policy). So I need EITHER: 1. a method of downloading locally *all* messages from the server (incoming, sent, trash, drafts, etc.) to the workstation, when the user consults his/her mailbox from a POP3 desktop client, thus completely *emptying* the user's mailbox on the server OR 2. an automatic, elegant but forceful method of deleting all messages older than X days (incoming, sent, trash, drafts, etc.) I've tried to use a line such as: doveadm expunge -u john.doe(a)example.com before 4w run as root, from a script in crontab, but for "expunge" doveadm won't let me skip the "-u" parameter (to perform the expunge for *all* users). Could you please help? Any sugestion is welcomed. Thanks a lot, Răzvan

2 1

[Dovecot] Using ldap and pam
by Bo Lynch 06 Aug '13

06 Aug '13

Having some issues with ldap logins. I am using Centos 5,dovecot-1.0.13-1.el5.rfx and openldap-servers-2.3.43-25.el5_8.1 Trying to get this to work with the SoGo interface. First I converted all my standard system users to ldap using the openldap-tools. This worked fine, however when a user changes there password they can no longer see there email. If they change it back to the original password mail can be seen. This has stumped me for a day or so so I was hoping someone could shed some light. /etc/dovecot.conf protocols = imap imaps disable_plaintext_auth = no mbox_read_locks = fcntl mbox_write_locks = fcntl protocol imap { } protocol pop3 { } protocol lda { postmaster_address = postmaster(a)example.com } auth default { mechanisms = plain login passdb pam { } passdb ldap { args = /etc/dovecot-ldap.pass } userdb passwd { } user = root user = root socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } dict { } plugin { } /etc/dovecot-ldap.conf hosts = 127.0.0.1:389 sasl_bind = no auth_bind = yes auth_bind = no ldap_version = 3 deref = never dn = cn=sogo,dc=ameliaschools,dc=com dnpass=password base = dc=ameliaschools,dc=com scope = subtree pass_attrs = uid=user, userPassword=password pass_filter = (uid=%u)

3 5

[Dovecot] How to troubleshoot LDA or LMTP?
by John Williams 06 Aug '13

06 Aug '13

Please forgive me if these are silly questions. I am a normal user, not a system administrator. I am using Dovecot as a kind of IMAP caching proxy, i.e. reading IMAP mail via Gnus + Dovecot + Offlineimap. I am trying to enable sieve functionality. *Desired behaviour* When Gnus (or whatever MUA) asks for new mail from Dovecot, that before Dovecot returns and answer, the sieve rules are executed. Please tell me if I completely misunderstand how the mail system works in this instance. *Actual behaviour* As far as I can tell, not only are the sieve rules not executed, but also neither LDA or LMTP is invoked. *What works* Running the scripts manually via `sieve-filter` works fine. The next time I read from my local dovecot server the mail is all in the desired place. Also, the LMTP service is running, listening on port 24. *What doesn't work* I thought the next step would be to execute dovecot-lda manually (as is suggested on the wiki and in numerous newsgroup posts), but I can't figure out how to do this. When I execute it as root and provide my non-root username via the -u option, it hangs. I can see that it spawns a child process that executes as the non-root user (specified with the -u option). So, could someone tell how to execute dovecot-lda manually please? Also, when does LMTP process messages? When sending mail via SMTP, or when reading mail via IMAP? I would prefer to use LMTP rather than LDA. *My environment* Fedora 19 & sendmail. Is any other information relevant, apart from the dovecot configuration? Thank you, John .2.4: /etc/dovecot/dovecot.conf # OS: Linux 3.10.4-300.fc19.x86_64 x86_64 Fedora release 19 (Schrödinger’s Cat) auth_socket_path = /var/run/dovecot/auth-userdb debug_log_path = /var/log/dovecot-debug.log disable_plaintext_auth = no hostname = falcon.novoalexandrovsk.ru info_log_path = /var/log/dovecot-info.log lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_greeting = Dovecot ready, folks! mail_access_groups = mail mail_debug = yes mail_location = mbox:~/mail/mailboxes:DIRNAME=mBoX-MeSsAgEs:INDEX=~/mail/index:CONTROL=~/mail/control:INBOX=/var/spool/mail/%u managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/lib/dovecot/sieve/global/ sieve_global_path = /var/lib/dovecot/sieve/default.sieve } postmaster_address = johnfrombluff(a)gmail.com protocols = imap lmtp sieve service auth { unix_listener auth-userdb { mode = 0600 user = mail } } service lmtp { executable = lmtp -L inet_listener lmtp { address = 192.168.0.101 127.0.0.1 ::1 port = 24 } user = mail } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 1 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 10 } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } protocol lmtp { info_log_path = /var/log/dovecot-lmtp-info.log log_path = /var/log/dovecot-lmtp-debug.log mail_plugins = " sieve" } protocol lda { info_log_path = /var/log/dovecot-lda-info.log log_path = /var/log/dovecot-lda-errors.log mail_plugins = " sieve" } protocol sieve { mail_max_userip_connections = 10 managesieve_implementation_string = Dovecot Pigeonhole, Asshole! managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 }

3 2

[Dovecot] The "<" sign in config files
by Frank Elsner 06 Aug '13

06 Aug '13

Hallo experts, what is the meaning of the "<" sign in config files as in ssl_key = </etc/pki/tls/private/dovecot.key ^ | ? --Frank Elsner

2 1

[Dovecot] dovecot, spamassasin and lmtp
by alfdc 06 Aug '13

06 Aug '13

Hi, Ok, so I got rid of my procmail in favor of dovecot lmtp as my MDA. However, I lost the ability to tag the emails as SPAM or not. Before, this is done by procmail. Filtering is done by the Evolution client. Is there a way to do something similar now? I still want my filtering to be done by the Evolution. So I need something similar what procmail is doing i.e. altering the email header and putting some tag on it if it is a SPAM. Thanks. -- View this message in context: http://dovecot.2317879.n4.nabble.com/dovecot-spamassasin-and-lmtp-tp43709.h… Sent from the Dovecot mailing list archive at Nabble.com.

3 5

[Dovecot] script to test CATENATE
by Mike Abbott 05 Aug '13

05 Aug '13

Attached please find a perl script which tests the CATENATE support in dovecot. I used this to test my CATENATE implementation a few years ago and it runs fine against dovecot in OS X Server. When run against dovecot-2.2.4 though it always fails or hangs, which in some cases means we interpreted RFCs differently and in other cases means it's finding bugs; both conditions are worthy of scrutiny. (It's random-number driven so every run is different.) A couple months ago I reported a few simple bugs which this script found and you fixed them; thanks. Then it started finding problems for which it's harder to isolate simple reproducible test cases. Vacations and other work interceded but now Apple is pleased to give you the script itself to allow you to iterate faster. Here are some examples of it running. One time only, pass the --init argument to store some template messages used by the real tests: $ ./catenate.pl --host your.test.server --user testuser --password 1234 --init connecting (imaps)... capability... logging in... deleting old templates mailbox... creating templates mailbox... append1... Append succeeded append2... Append succeeded logout... success $ ./catenate.pl --host your.test.server --user testuser --password 1234 connecting (imaps)... capability... logging in... append1... Append failed as it should have (bad url): <append1 NO [BADURL ;invalid;] Invalid IMAP URL: Unexpected IMAP URL path segment: `;invalid;'.> append2... Append failed as it should have (bad url): <append2 NO [BADURL /inbox/;uid=99999999] Message not found.> append3... Append succeeded [...] All tests passed. $ If it concludes with anything other than "All tests passed" or hangs then it found something that it didn't expect and that should be examined. Use the --verbose option to see the entire client-server conversation. We hope that you find this script helpful to harden your CATENATE code. I will be happy to answer any questions.

3 5

[Dovecot] problems with expire plugin
by Felix Rubio Dalmau 05 Aug '13

05 Aug '13

Hi all, I'm experiencing problems to set-up the expire plugin in dovecot. This is the relevant part of my dovecot configuration dict { expire = mysql:/etc/dovecot/dovecot-dict-expire.conf.ext } plugin { expire = Trash 15 Junk 15 expire_dict = proxy::expire } protocol imap { mail_plugins = quota zlib expire imap_quota } File dovecot-dict-expire.conf.ext looks like: connect = host=127.0.0.1 dbname=virtual_email user=<user> password=<passw> map { pattern = shared/expire/$user/$mailbox table = virtual_expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } and the mysql schema for table virtual_expires is: +--------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +--------------+--------------+------+-----+---------+-------+ | username | varchar(75) | NO | PRI | NULL | | | mailbox | varchar(255) | NO | PRI | NULL | | | expire_stamp | int(11) | NO | | NULL | | +--------------+--------------+------+-----+---------+-------+ However, when I delete any mail from the Inbox, the table is not updated, and there are no messages in the log, although mail_debug is set to "yes" Does anybody has any idea on how to solve this issue? Regards! Felix

3 9

[Dovecot] Corrupted mboxes with v2.2.4, posix_fallocate and GFS2
by Francesco Prelz 05 Aug '13

05 Aug '13

Hi, on a clustered Dovecot server installation that was recently moved from a shared GPFS filesystem to GFS2, occasional corruptions in the users' INBOXes started appearing, where a new incoming message would be appended directly after a block of NUL bytes, and be scanned by dovecot as being glued to the preceding message. I traced this to the file extension operation performed in mbox_sync_handle_eof_updates, where the 'file_set_size' call is used. If available, file_set_size will use the posix_fallocate call. In GFS2 posix_fallocate increases the file size in 4 kB chunks (there seems to be no guarantee anyway that posix_allocate will extend a file by the exact size requested). After a successful posix_fallocate call, mbox_sync_handle_eof_updates currently proceeds in rewriting the mailbox starting from the originally intended 'file_size': 1306 if (file_set_size(sync_ctx->write_fd, 1307 file_size + -sync_ctx->space_diff) < 0) { 1308 mbox_set_syscall_error(sync_ctx->mbox, 1309 "file_set_size()"); 1310 if (ftruncate(sync_ctx->write_fd, file_size) < 0) { 1311 mbox_set_syscall_error(sync_ctx->mbox, 1312 "ftruncate()"); 1313 } 1314 return -1; 1315 } 1316 mbox_sync_file_updated(sync_ctx, FALSE); 1317 1318 if (mbox_sync_rewrite(sync_ctx, mail_ctx, file_size, 1319 -sync_ctx->space_diff, padding, 1320 sync_ctx->need_space_seq, 1321 sync_ctx->seq) < 0) 1322 return -1; When posix_fallocate extends the mailbox beyond the requested 'file_size', a variable size block of NUL bytes is left behind at the tail of the mailbox, with the side effects described above. I successfully worked around this issue by undefining HAVE_POSIX_FALLOCATE, as the performance penalty with falling back to direct block appends seems small. At least a size check (and possible truncation) after the mbox_sync_file_updated call above should probably be added. I thought that the issue would be anyway worth bringing to your attention. Thanks. Francesco Prelz INFN - Sezione di Milano

2 2

[Dovecot] problems with doveadm
by listserv 05 Aug '13

05 Aug '13

Hello, since few weeks i have problems with the command: doveadm expunge -A mailbox Trash savedbefore 7d => kernel: doveadm[11609]: segfault at 10 ip b75f146a sp bf856ad0 error 4 in libdovecot.so.0.0.0[b7585000+c8000] but for a single user it's works fine: doveadm expunge -u test(a)vtlx.de mailbox Trash savedbefore 30h doveconf -n # 2.2.4 (f16816a69130): /etc/dovecot/dovecot.conf # OS: Linux 3.2.45.stk32 i686 Debian jessie/sid ext3 I hope there is a solution for this. with regards Mario -- 中華人民共和國

3 8