- dovecot - dovecot.org

delete/archive old mail
by sottilette＠rfx.it 13 Oct '14

13 Oct '14

Hi everybody, I store user's mail in the old mbox format. I have many scripts to manage users that works fine with mbox. I use the very old Expire_mail.pl script to delete mail older than NN days for selected users (nightly cron job). Still works fine with my CentOS dovecot-2.0.16. Now I want move the mail to a sort of archive folder instead of simply deleting it from the inbox for some users. Is there a similar script or some simple triks? Thanks, F.

2 1

2.2.14rc1 - dsync in backup mode still changes source permissions
by Peter Mogensen 13 Oct '14

13 Oct '14

Hi, It seems we are still able to reproduce this: http://www.dovecot.org/list/dovecot/2014-May/096367.html However... there's no longer any error-messages. It just silently changes permissions on some dovecot files in the source maildir. (most often dovecot-uidlist) We're running dsync as root, with hardwired userdb values for other reasons. So it has the OS permissions to change source. But still, running in "backup" shouldn't change source ever, should it? The command line is of this format - running on destination-host: # dsync -R -o mail_home=/users/user/maildir backup ssh -c arcfour -o StrictHostKeyChecking=no -i /root/.ssh/id-rsa-dsync source-host "dsync -o mail_home=/users/user/maildir" /Peter

2 4

Permissions for shared mail don't work
by Damien Desfontaines 12 Oct '14

12 Oct '14

Good morning, I'm using dovecot v.2.1.7 on Debian Sid, and the output of dovecot -n is available here: http://paste.fulltxt.net/C-O I'm trying to make the mailbox of (system) user "spam" available to user "ted". I followed these instructions: http://wiki2.dovecot.org/SharedMailboxes/Permissions and it doesn't seem to work. To be more precise: - I manually (and recursively) changed the permissions of all files in ~spam/Mail to 660 (and 770 for the directories); - I manually (and recursively) changed the group owner of everything in ~spam/Mail to "mailperso", where "mailperso" is a group whose users are spam and ted; - I added « mail_access_groups=mailperso » into my dovecot config; - and I restarted dovecot. But still, when I send a new email to spam, it appears as being owned by group "spam" and having permissions set to 600, so I can't access it with user "ted". I also tried to set the setgid bit for ~spam/Mail, it didn't change anything, and when I recursively set the setgid for all subdirectories of ~spam/Mail, it gives new mails the correct group (mailperso) but not the correct permissions. Have I missed something, or is this a bug? Thanks in advance and best regards, Damien

1 0

Re: New to list / SQL AUTH
by Gedalya 12 Oct '14

12 Oct '14

On 10/11/2014 05:36 PM, Jorge Bastos wrote: > For each new user, does the directories on the filesystem will be > auto-created on 1st login? Yes, as far as permissions on parent directories allow.

1 0

courier-imap to dovecot
by Luciano Gabriel Andino 12 Oct '14

12 Oct '14

Hello! I am here since my boxes (40000 emails in folders) are not usable with roundcube and courier-imap. Server is core 2 quad, 4GB RAM and 1TB HD. Which are steps for migration for about 40 Maildir boxes to dovecot? -- Saludos!! Luciano Andino GNU/Linux user #185103 Santa Fe - Argentina -----------------------------------------------

1 0

New to list / SQL AUTH
by Jorge Bastos 12 Oct '14

12 Oct '14

Hi, I'm new to dovecot, and I was reading the manual, to use SQL auth along with virtual domains. So far, it's perfect and does what I need, except for one thing. For each new user, does the directories on the filesystem will be auto-created on 1st login? Thanks in advanced,

1 0

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