- dovecot - dovecot.org

dovecot replication (active-active) - server specs
by Martin Schmidt 11 Oct '14

11 Oct '14

Hello, i have some questions about the new dovecot replication and mdbox format. my company has currently 3 old dovecot 2.0.x fileserver/backend with ca. 120k mailboxes and ca. 6 TB data used. They are synchronised per drbd/corosync. Each fileserver/backend have ca. 40k mailboxes im Maildir format. Our MX server is delivering ca. 30 GB new mails per day. Two IMAP proxy server get the connections from the users. Atm. without dovecot director. We've got around 700k connections per day (imap 200k / pop3 500k) The system is getting issues because the fileserver still have old slow HDDs. Users sometime get connection timeouts, because the fileserver can not answer fast enough due to I/O waiting lag. So we want to make a new system. We desire the new system to use mdbox format ( bigger files, less I/O) and replication through dovecot replication (active/active) instead of drbd. Each fileserver should know every mailbox/user and for the time being 2 dovecot proxies for the user connections (IMAP/POP). (later after the migration from the old system to the new, dovecot director instead of proxies, for caching reasons). we've got 2 new fileservers, they have each SSD HDDs for "new-storage" and 7200rpm SATA HDDs on RAID 5 with 10 TB for "alt-storage" 32 GB RAM per Server Do you have some tips for the system? Do you believe 32 GB RAM are enough for one fileserver each and have you experience with the I/O Waiting problem with huge amounts of Data on the alt-storage? Could there be issues with the RAM, if one fileserver has a downtime, so the second one has to take over all mailboxes for a short amount of time? In general are only 2 new fileserver enough or should we think in bigger dimensions, like 4 fileserver Storage expansion in the new servers should not be a problem (bigger HDDs and a few slots free, so we can expand the raid 5). thank you kind regards Martin Schmidt

4 4

Re: question: dovecot lda running as special user (vmail) or normal user (marcel)?
by marcel.cochem 11 Oct '14

11 Oct '14

Dear Mailing List, (version and dovecot -n at the bottom) (Sorry for the bad English in this mail :) ) I'm new to dovecot and wanted to build my own mailserver using dovecot+postfix. I currently have a Problem with Permissions with my mailfolder. I could solve it easily if i set it with chmod to 777. but thats no real solution. While reading my log files i see a lot messages like: Oct 10 05:19:52 lda(owncloud): Error: user owncloud: Initialization failed: Initializing mail storage from mail_location setting failed: stat(/home/vmail/example.com/owncloud/mail) failed: Permission denied (euid=100(owncloud) egid=1004(owncloud) missing +x perm: /home/vmail, dir owned by 5000:5000 mode=0700) Oct 10 05:19:52 lda(owncloud): Fatal: Invalid user settings. Refer to server log for more information. So Currently two Users need to acces the mail-folder: 1. The user itself (here: owncloud) 2. The vmail user I want to use dovecot with virtual users. Now the question is: shouldn't the directory be accessed only by the vmail user? and not by the owncloud user? Second Quest: If it's correct that the access is made by 2 users: what rights do they need? I Cant add all users to the group vmail and set g+rwx Permissions (every user could read mails from other users, and even edit them!) Thanks a Lot. Kind Regards, Marcel ------------------------------ ------------------------------------------------------------------------------------ dovecot --version 2.2.13 dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-37-generic x86_64 Ubuntu 14.04.1 LTS ext4 auth_mechanisms = plain login auth_verbose = yes info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_home = /home/vmail/example.com/%n mail_location = maildir:/home/vmail/example.com/%n/mail:LAYOUT=fs 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 duplicate namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = username_format=%u scheme=ssha512 /etc/dovecot/passwd.db driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_after = /home/vmail/sieve-after sieve_before = /home/vmail/sieve-before sieve_dir = ~/sieve } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/ssl_main.crt ssl_cipher_list = ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AES:RSA+3DES:!ADH:!AECDH:!MD5:!DSS ssl_client_ca_dir = /etc/ssl/certs ssl_key = </etc/ssl/private/ssh_main_insecure userdb { args = uid=5000 gid=5000 home=/home/vmail/example.com/%n driver = static } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 10 } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster(a)example.com quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } On Fri, Oct 10, 2014 at 10:13 AM, marcel.cochem < marcel.cochem(a)googlemail.com> wrote: > Dear Mailing List, > > (version and dovecot -n at the bottom) > (Sorry for the bad English in this mail :) ) > > I'm new to dovecot and wanted to build my own mailserver using > dovecot+postfix. > I currently have a Problem with Permissions with my mailfolder. > I could solve it easily if i set it with chmod to 777. but thats no real > solution. > > While reading my log files i see a lot messages like: > Oct 10 05:19:52 lda(owncloud): Error: user owncloud: Initialization > failed: Initializing mail storage from mail_location setting failed: > stat(/home/vmail/example.com/owncloud/mail) failed: Permission denied > (euid=100(owncloud) egid=1004(owncloud) missing +x perm: /home/vmail, dir > owned by 5000:5000 mode=0700) > Oct 10 05:19:52 lda(owncloud): Fatal: Invalid user settings. Refer to > server log for more information. > > So Currently two Users need to acces the mail-folder: > 1. The user itself (here: owncloud) > 2. The vmail user > > I want to use dovecot with virtual users. Now the question is: shouldn't > the directory be accessed only by the vmail user? and not by the owncloud > user? > > Second Quest: > If it's correct that the access is made by 2 users: what rights do they > need? > I Cant add all users to the group vmail and set g+rwx Permissions (every > user could read mails from other users, and even edit them!) > > Thanks a Lot. > Kind Regards, > > Marcel > > ------------------------------------------------------------------------------------------------------------------ > > dovecot --version > 2.2.13 > > dovecot -n > # 2.2.13: /etc/dovecot/dovecot.conf > # OS: Linux 3.13.0-37-generic x86_64 Ubuntu 14.04.1 LTS ext4 > auth_mechanisms = plain login > auth_verbose = yes > info_log_path = /var/log/dovecot-info.log > log_path = /var/log/dovecot.log > mail_home = /home/vmail/example.com/%n > mail_location = maildir:/home/vmail/example.com/%n/mail:LAYOUT=fs > 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 duplicate > namespace inbox { > inbox = yes > location = > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > mailbox Junk { > auto = subscribe > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox "Sent Messages" { > auto = subscribe > special_use = \Sent > } > mailbox Trash { > auto = subscribe > special_use = \Trash > } > prefix = > } > passdb { > args = username_format=%u scheme=ssha512 /etc/dovecot/passwd.db > driver = passwd-file > } > plugin { > sieve = ~/.dovecot.sieve > sieve_after = /home/vmail/sieve-after > sieve_before = /home/vmail/sieve-before > sieve_dir = ~/sieve > } > protocols = imap sieve > service auth { > unix_listener /var/spool/postfix/private/dovecot-auth { > group = postfix > mode = 0660 > user = postfix > } > } > ssl_cert = </etc/ssl/certs/ssl_main.crt > ssl_cipher_list = > ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AES:RSA+3DES:!ADH:!AECDH:!MD5:!DSS > ssl_client_ca_dir = /etc/ssl/certs > ssl_key = </etc/ssl/private/ssh_main_insecure > userdb { > args = uid=5000 gid=5000 home=/home/vmail/example.com/%n > driver = static > } > protocol imap { > imap_client_workarounds = delay-newmail tb-extra-mailbox-sep > mail_max_userip_connections = 10 > } > protocol lda { > deliver_log_format = msgid=%m: %$ > mail_plugins = sieve > postmaster_address = postmaster(a)example.com > quota_full_tempfail = yes > rejection_reason = Your message to <%t> was automatically rejected:%n%r > } > >

2 2

]UG] Dovecot 2.2.9 SSL client cert verification fails: openssl verify: OK
by Daniel Dickinson 11 Oct '14

11 Oct '14

Greetings all, I have verified a bug that has long been attributed to lack of knowledge on the part of the user. Dovecot rejects StartSSL client certificates due to reject StartSSL root CA when doing client verification even though the appropriately constructed ca-bundle.pem has been created and applied vi ssl_ca = </etc/dovecot/ca-bundle.pem. openssl verify -CAfile ca-bundle.pem -crl_check_all -policy_check -x509_strict -verbose client-cert.pem returns: client-cert.pem: OK However dovecot reports the following: Oct 11 01:41:17 hostname dovecot: imap-login: Invalid certificate: unable to get local issuer certificate: /C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Certification Authority Oct 11 01:41:17 hostname dovecot: imap-login: Invalid certificate: certificate not trusted: /C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Certification Authority Oct 11 01:41:17 hostname dovecot: imap-login: Invalid certificate: unable to get certificate CRL: /C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Certification Authority Oct 11 01:41:17 hostname dovecot: imap-login: Valid certificate: /C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Class 1 Primary Intermediate Client CA Also reports the client certificate as valid. The certificate bundle was created as follows: openssl x509 -in sub.class1.client.pem -subject -issuer >ca-bundle.pem cat class1-client-crl.pem >>ca-bundle.pem openssl x509 -in startcom-root-ca.pem -subject -issuer >>ca-bundle.pem cat startcom-root-ca-crl.pem >>ca-bundle.pem Furthermore exim, Thunderbird, and Firefox are all perfectly happy with the certificates (and exim has no problem verifying the client certificates). Further, there are many more messages regarding issues with users of dovecot having issues with StartCom client certificates who have reported following all the steps than with Cyrus or Courier. Oh, and client verification of server-side certificate works fine with server-side certificate bundle (cat server.pem startcom-intermediate.pem startcom-root-ca.pem >dovecot.pem) Relevant dovecot -n included below: auth_debug = yes auth_mechanisms = plain login digest-md5 cram-md5 otp auth_ssl_require_client_cert = yes auth_verbose = yes ssl = required ssl_ca = </etc/dovecot/ca-bundle.pem ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem ssl_verify_client_cert = yes verbose_ssl = yes OS is Debian Wheezy with latest updates and (just today in hopes it had been fixed, same error occurs with Wheezy's dovecot = 2.1.7) dovecot 2.2.9 from backports. amd64 architecture. Please CC me as I am not subscribed to the list. Regards, Daniel

1 0

Error with dovecot 2.2.14rc1
by Mark Sapiro 10 Oct '14

10 Oct '14

I don't know if this is significant or not, but it is at least unusual here. First we see this: > Oct 9 10:10:03 sbh16 dovecot: imap(mark): Error: Sync failed for mbox file /var/spool/mail/mark: seq=393 uid=201517 uid_broken=0 originally needed 0 bytes, now needs 66 bytes which has apparently added 66 bytes to UID 201517 Then, later we see: > Oct 9 11:26:19 sbh16 dovecot: imap(mark): Error: Cached message size larger than expected (32353 > 32287) > Oct 9 11:26:19 sbh16 dovecot: imap(mark): Error: Corrupted index cache file /home/mark/Mail/.imap/INBOX/dovecot.index.cache: Broken physical size for mail UID 201517 > Oct 9 11:26:19 sbh16 dovecot: imap(mark): Error: read(/var/spool/mail/mark) failed: Cached message size larger than expected (32353 > 32287) (FETCH BODY[] for mailbox INBOX UID 201517) > Oct 9 11:26:19 sbh16 dovecot: imap(mark): Disconnected: FETCH read() failed in=10948 out=1206206 As of now (almost 22 hours later) these are the only dovecot Error messages in the log. Going back a full month, we see this under dovecot 2.2.13 > Sep 9 10:18:01 sbh16 dovecot: imap(mark): Error: Sync failed for mbox file /var/spool/mail/mark: seq=198 uid=198968 uid_broken=0 originally needed 0 bytes, now needs 66 bytes but no subsequent errors like yesterday. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Migrating to Dovecot EE
by Philipp Resch 10 Oct '14

10 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone! I am currently running dovecot 2.2.9 on my Debian Wheezy system. As this version is a bit outdated and I'm not too keen on compiling Dovecot myself I was thinking about moving to the Dovecot EE repository. I already have access to the repository, and now before I starting "apt-getting" all kinds of packages: What would be the best way on moving to the Dovecot EE repository? Just doing an apt-get install dovecot-ee? Will it replace the current version? Or should the old version be removed before installing the new one? Has anyone ever done this and has some advice for me? Thanks in advance, Philipp -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJUN50yAAoJEC6sCbYfpzg9ilcH/iREEyhyygKEVrCyLRjutcLm iLa63KHCFGFjU3b5igZFD+Jv1uZmHfyLh+ZFz0ditHmS1jbNE49WKGawAuoBb3lv VqMCex3qsOA9OVdAbPYUCecs7K18Oo8DjwFpI4Sn70flsaFpo3JS32I/dZ9OMF7d p9O/G1PfJ4mw4zWC0HGgE7kluYytPBJTw2rqqAyjHXypQhcpiF+HHtFm/pX9SF4U b4K5YqfFJE/Bk7YYEdnQFyribcDxkllIzeAt09EhpEwZHK8MTWi92PwnHDcTX3M4 P7JnmSO3YtfSphbqDOFZgAYz2otEAPgysXu3v4asLkcoiPQb/H7hUlcNZyzLeIo= =fu6j -----END PGP SIGNATURE-----

2 1

question: dovecot lda running as special user (vmail) or normal user (marcel)?
by marcel.cochem 10 Oct '14

10 Oct '14

Dear Mailing List, (version and dovecot -n at the bottom) (Sorry for the bad English in this mail :) ) I'm new to dovecot and wanted to build my own mailserver using dovecot+postfix. I currently have a Problem with Permissions with my mailfolder. I could solve it easily if i set it with chmod to 777. but thats no real solution. While reading my log files i see a lot messages like: Oct 10 05:19:52 lda(owncloud): Error: user owncloud: Initialization failed: Initializing mail storage from mail_location setting failed: stat(/home/vmail/example.com/owncloud/mail) failed: Permission denied (euid=100(owncloud) egid=1004(owncloud) missing +x perm: /home/vmail, dir owned by 5000:5000 mode=0700) Oct 10 05:19:52 lda(owncloud): Fatal: Invalid user settings. Refer to server log for more information. So Currently two Users need to acces the mail-folder: 1. The user itself (here: owncloud) 2. The vmail user I want to use dovecot with virtual users. Now the question is: shouldn't the directory be accessed only by the vmail user? and not by the owncloud user? Second Quest: If it's correct that the access is made by 2 users: what rights do they need? I Cant add all users to the group vmail and set g+rwx Permissions (every user could read mails from other users, and even edit them!) Thanks a Lot. Kind Regards, Marcel ------------------------------ ------------------------------------------------------------------------------------ dovecot --version 2.2.13 dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-37-generic x86_64 Ubuntu 14.04.1 LTS ext4 auth_mechanisms = plain login auth_verbose = yes info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_home = /home/vmail/example.com/%n mail_location = maildir:/home/vmail/example.com/%n/mail:LAYOUT=fs 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 duplicate namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = username_format=%u scheme=ssha512 /etc/dovecot/passwd.db driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_after = /home/vmail/sieve-after sieve_before = /home/vmail/sieve-before sieve_dir = ~/sieve } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/ssl_main.crt ssl_cipher_list = ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AES:RSA+3DES:!ADH:!AECDH:!MD5:!DSS ssl_client_ca_dir = /etc/ssl/certs ssl_key = </etc/ssl/private/ssh_main_insecure userdb { args = uid=5000 gid=5000 home=/home/vmail/example.com/%n driver = static } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 10 } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster(a)example.com quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r }

1 0

Keywords & sync
by Ralf Hildebrandt 10 Oct '14

10 Oct '14

We're using keywords within Thunderbird, and we're syncing those using IMAP. When using more than 5 keywords, we're envcountering problems - they're only partially being synced (between two clients, but not all clients). Any idea why this could be happening? The introduction of tagging in Thunderbird is described here: <https://bugzilla.mozilla.org/show_bug.cgi?id=114656> -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

6 5

Send an alert on master user login
by Andre Rodier 09 Oct '14

09 Oct '14

Hello, I want to know if there is an option in Dovecot to send an alert, or run a script when someone is using the master user facility. I can do something myself with fail2ban, but maybe there is an option in Dovecot? Thanks. André.

2 4

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

mailbox in different filesystem
by Héctor Moreno Blanco 08 Oct '14

08 Oct '14

Hello everyone, We have Dovecot 2.1.6 with Maildir. We would like to perform some kind of mail archiving with a mailbox in a different storage, for example a mailbox called ARCHIVED, with different disks (slower...). Is possible to locate this mailbox in other storage (SAS, Fiber...) and how can we do it? Thank you very much in advanced. Kind regards. Héctor Moreno P Please consider the environment before printing this e-mail. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________

2 2