August 2014 - dovecot

[Dovecot] Disk Encryption
by Simon Brereton 17 Oct '14

17 Oct '14

Hi As I understand it email headers need to be unencrypted (otherwise DKIM doesn't work). From the MUA to either Postfix, or Dovecot the connection is (or can/should be) secured with TLS/SSL. What I would like to know is if it is possible to encrypt the mailstore? Postfix is using Dovecot for delivery so it's only Dovecot that would need to encrypt/decrypt the mailstore. Is this possible? Is there a terrible reason to do it even if it is possible? I realise that from MTA to MTA there's no guarantee of encryption (and in fact it's very unlikely unless keys have been exchanged), but my primary goal is supplement the physical security of the mail store of mails we already have or have sent. Mostly just idle curiosity as to what has been done, or what could be done. What is worth doing is a separate thread entirely. Thanks. Simon

11 28

Sieve filter extracting wrong header value on certain mail messages
by gowen (dovecot) 09 Oct '14

09 Oct '14

# 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.15.4-x86_64-linode45 x86_64 openSUSE 12.3 (x86_64) Short version: 1) I filter out spam by using a dovecot sieve filter to act based on a header inserted by bogofilter 2) In some cases, sieve fails to correctly file based on this header 3) Testing with sieve-test indicates that it's testing the wrong header 4) Suggestions? Am I doing something wrong? Is there a problem with these headers that bends test-sieve out of shape? 5) Test files from below are also available via http://www.swynwyr.com/sieve-test/ Any help is appreciated!!! Long version with full details: Here is the simple sieve filter I'm using to test, and two different variants of an email which triggers this problem. I basically deleted things one by one from an original email (1) to get minimal testcases that triggered (2) or did not trigger (3) the problem. The filter: === begin test.sieve === require ["fileinto", "body", "regex"]; if header :contains "X-Bogosity" "Spam," { fileinto "SPAM.SPAM"; stop; } elsif header :contains "X-Bogosity" "Unsure," { fileinto "SPAM.UNSURE"; stop; } keep; stop; === end test.sieve === Here is an example email that will cause this filter to not function as expected: === begin message.2 === Return-Path: <alora(a)promosforusio.org> Subject: =?utf-8?B?QUhTIEtpdGNoZW4gTWFrZW92ZXIgR2l2ZWF3YXkg?= Subject: ÎHS KitÑhen ÎakÐµovÐµr GivÐµaway Subject: =?ISO-8859-1?Q?AHS Kitchen Makeover Giveaway =A0=A0=A0?= Subject: Subject: AHS Kitchen Makeover Giveaway X-Bogosity: Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3 Home Warranty Summer Giveaway === end message.2 === If I run test-sieve on this, we can clearly see in the trace log that when it's supposed to test for header "X-Bogosity" it in fact looks at one of the multiple "Subject" headers. Note that the result is storing in INBOX rather than SPAM.SPAM, and that the "matching value" for "X-Bogosity headers" is actually the contents of the final "Subject" header in the test on line 3. In the second test, on line 6, it uses a different and correct value for the same header! But too late to help as the first test was the one it should have had a match on. === begin session === $ sieve-test -t trace2.log -Tlevel=matching test.sieve message.2 Performed actions: * store message in folder: INBOX Implicit keep: (none) sieve-test(gowen): Info: final result: success $ cat trace2.log ## Started executing script 'test' 3: header test 3: starting `:contains' match with `i;ascii-casemap' comparator: 3: extracting `X-Bogosity' headers from message 3: matching value `AHS Kitchen Makeover Giveaway' 3: with key `Spam,' => 0 3: finishing match with result: not matched 3: jump if result is false 3: jumping to line 6 6: header test 6: starting `:contains' match with `i;ascii-casemap' comparator: 6: extracting `X-Bogosity' headers from message 6: matching value `Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3' 6: with key `Unsure,' => 0 6: finishing match with result: not matched 6: jump if result is false 6: jumping to line 11 11: keep action; store message in default mailbox 12: stop command; end all script execution ## Finished executing script 'test' $ === end session === Now lets remove the "Return-Path" from that message. (Of the original 26 headers, all but the 7 shown in message.2 could be removed and still have this message break the filter). This alters thing enough that sieve starts working as expected (in fact, removing any one of the 6 non-X-Bogosity headers will cause this to start working). === begin message.3 === Subject: =?utf-8?B?QUhTIEtpdGNoZW4gTWFrZW92ZXIgR2l2ZWF3YXkg?= Subject: ÎHS KitÑhen ÎakÐµovÐµr GivÐµaway Subject: =?ISO-8859-1?Q?AHS Kitchen Makeover Giveaway =A0=A0=A0?= Subject: Subject: AHS Kitchen Makeover Giveaway X-Bogosity: Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3 Home Warranty Summer Giveaway === end message.3 === Now when we run test-sieve it works as expected, filing into SPAM.SPAM and showing the correct matching value for line 3: === begin session === $ sieve-test -t trace3.log -Tlevel=matching test.sieve message.3 Performed actions: * store message in folder: SPAM.SPAM Implicit keep: (none) sieve-test(gowen): Info: final result: success $ cat trace3.log ## Started executing script 'test' 3: header test 3: starting `:contains' match with `i;ascii-casemap' comparator: 3: extracting `X-Bogosity' headers from message 3: matching value `Spam, tests=bogofilter, spamicity=1.000000, version=1.2.3' 3: with key `Spam,' => 1 3: finishing match with result: matched 3: jump if result is false 3: not jumping 4: fileinto action 4: store message in mailbox `SPAM.SPAM' 5: stop command; end all script execution ## Finished executing script 'test' $ === end session ===

3 3

[Dovecot] mdbox-files over 2 MB
by Hardy Flor 01 Oct '14

01 Oct '14

Hello, I received an e-mail, this includes 9 forwarding, each with a file. These files are not removed from the e-mail and stored in the attachments-directory, although they are larger than 16 KB. For all files the "Content-Transfer-Encoding: base64" is set. The email is stored in completely in "m.00000034" ------------------------------------- doveconf: # 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 ext4 mail_attachment_dir = /var/mail/attachments mail_attachment_hash = %{md5} mail_attachment_min_size = 16 k mail_location = mdbox:/var/mail/user/%n mdbox_rotate_interval = 1 weeks mdbox_rotate_size = 2 M ------------------------------------- directory: root@xxx:/var/mail/user/xxx/storage# ls -al ... -rw------- 1 vmail mail 14433784 Mär 16 13:51 m.00000034 ...

6 8

How to configure dovecot imap to listen on multiple ports?
by Rick Thomas 26 Sep '14

26 Sep '14

I need my dovecot imap server to listen on ports 143, 993, and also 30143 and 30993. What syntax do I use in (I presume) the /etc/dovecot/conf.d/10-master.conf file to do this? Thanks! Rick

4 10

Exit status code 134; what is it, in the context of Dovecot Antispam plug-in?
by Ben Johnson 17 Sep '14

17 Sep '14

Hello! I just migrated from Ubuntu 12.04 LTS to 14.04 LTS and thereby from Dovecot 2.0.19 to 2.2.9. I've been using dovecot-antispam plugin with great success for the past year with 2.0.19, but after this migration, I've been seeing the exit status code 134 in the syslog when attempting to debug the Dovecot Antispam plugin not working after the migration. I have some debugging output in my pipe script; the output looks something like this: Copying message contents to temporary file for debugging purposes; file is: /tmp/sendmail-msg-7662.txt Checking if the command-line input argument string (--spam) contains the string "ham" or "spam" Mode is "SPAM" Calling (as user vmail) '/usr/lib/dovecot/deliver -d "sa-training(a)example.com" -m "Training.SPAM" -p "/tmp/sendmail-msg-7662.txt"' Exit status was 134 Yet, I'm able to copy the above command and execute it manually, via the command-line, and it works (and by "works", I mean to say that the behavior is correct and exactly as expected; I receive the "Spam" email at the designated mailbox). Here's how I'm calling it when it works perfectly well (as "root"): # su -c '/usr/lib/dovecot/deliver -d "sa-training(a)example.com" -m "Training.HAM" -p "/tmp/sendmail-msg-7460.txt"' vmail Any idea what status 134 might be or how to work around it? It looks to be some kind of "temporary failure exception", but that is less than informative in this context. "doveconf -n" output is appended. Thanks for any help! -Ben # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-32-generic x86_64 Ubuntu 14.04.1 LTS auth_mechanisms = plain login disable_plaintext_auth = no listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_privileged_group = vmail 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 passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /bin/bash antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = SPAM;JUNK antispam_trash_pattern_ignorecase = trash;Deleted * antispam_verbose_debug = 1 quota = dict:user::file:/var/vmail/%d/%n/.quotausage quota_rule2 = Trash:storage=+100M quota_rule3 = Junk:ignore quota_rule4 = INBOX:storage=+100M quota_warning = storage=100%% quota-reached 100 %u %d quota_warning2 = storage=95%% quota-warning 95 %u %d quota_warning3 = storage=80%% quota-warning 80 %u %d quota_warning4 = -storage=100%% quota-below below %u %d sieve = /var/vmail/%d/%n/.sieve } postmaster_address = postmaster(a)example.com protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service config { unix_listener config { group = vmail mode = 0600 user = vmail } } service imap-login { client_limit = 1000 process_limit = 500 } service quota-below { executable = script /usr/local/bin/quota-below.sh unix_listener quota-below { group = vmail mode = 0666 user = vmail } user = vmail } service quota-reached { executable = script /usr/local/bin/quota-reached.sh unix_listener quota-reached { group = vmail mode = 0666 user = vmail } user = vmail } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0666 user = vmail } user = vmail } ssl_cert = </root/ssl/example.com/example.com.crt ssl_key = </root/ssl/example.com/example.com.key userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota antispam } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { info_log_path = log_path = mail_plugins = sieve quota }

4 10

replicator only starts for users who log in at least once
by Alan McGinlay 17 Sep '14

17 Sep '14

Hi! I recently setup a second with replication to the other. Both machines run ubuntu 12.04 with dovecot 2.2.13 (6bb26098a45c). All users mail accounts are currently synced manually to the first (mb1) using a dsync script, they are synchronised from a cyrus imap server. Users are still logging into the cyrus server. It appears that the only accounts that are replicated are ones who have logged into either of the dovecot servers at least once, is this how it is supposed to work? I was hoping to get full replication of all mail accounts before starting to move users into the new system. Thanks, Alan

1 1

Replication problem
by Ve (HOME) 10 Sep '14

10 Sep '14

Hi, I'm using mdbox and replication. Due to configuration error synchronization was not able to be done last week. Since then the problem has been corrected but synchronisation for some mailbox always failed in I/O stalled timeout for 600 seconds. The link between the two servers is quite slow and multiple sync are done in parallel leading to congested link. I can't replicate with rsync as change in the mdbox has been done on the two servers to get back to a working state. What do you think could be done to resynchronized the two dovecot server. Another question is what is this timeout ? Timeout of communication i.e no data received during 600 seconds ( to me that looks unlikely ) or 600 seconds for doing the full sync or 600 seconds for one mail sync. Thanks for any help. Regards, Vincent

3 5

preserving flags for shared mailbox when migrating from cyrus to dovecot
by Jogi Hofmüller 10 Sep '14

10 Sep '14

Dear all, Despite all the progress we are making in our attempt to make the migration as smooth and transparent for our users there are still some important unsolved issues. One thing that I can't figure out is how to preserve a user's flags that s/he has for mail in a shared mailbox. So far we tried 'doveadm backup -R' as well as the cyrus2dovecot script from here [1]. Both work well for individual mailboxes but do not migrate subscriptions for shared mailboxes and -- more importantly -- flags for mail in a shared mailbox. Reconstructing subscriptions is quite easy but I have no clue on how to reconstruct a user's flags. Any hint is greatly appreciated! [1] http://cyrus2dovecot.sw.fu-berlin.de/index.html -- j.hofmüller mur.sat -- a space art project http://sat.mur.at/

3 5

Creating a backup of incoming mail
by LuKreme 10 Sep '14

10 Sep '14

This is my master.cf line for dovecot virtual users: dovecot unix - n n - - pipe flags=DRhu user=vpopmail:vchkpw argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${user}@${nexthop} -m ${extension} I would like to also write every mail, before delivery to the user, to a backup location like /backup/imap/mm/dd Possible? -- 'On whose authority?' demanded Wert. Trymon turned his grey eyes on him. 'Mine. I need no other.' --The Light Fantastic

5 11

Dovecot Enterprize repository access
by Spyros Tsiolis 05 Sep '14

05 Sep '14

Hello all, in regards to the Enterprise repository access : 1. There's no version of v7.x for CentOS 2. There's no download section anywhere Any ideas ? s.

3 4