- dovecot - dovecot.org

Delivering email to Maildir PreINBOX
by Paulo Matos 24 Aug '15

24 Aug '15

Hi all, I have a running dovecot with: $ dovecot -n # 2.2.18: /etc/dovecot/dovecot.conf # OS: Linux 4.1.0-x86_64-linode59 x86_64 Fedora release 22 (Twenty Two) ext4 auth_debug = yes auth_mechanisms = plain login digest-md5 cram-md5 auth_verbose = yes auth_verbose_passwords = yes default_internal_user = root imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_debug = yes mail_location = maildir:/home/vmail/%d/%n/Maildir maildir_very_dirty_syncs = yes mbox_write_locks = fcntl namespace { inbox = yes location = prefix = INBOX. separator = . type = private } namespace inbox { 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 { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } postmaster_address = pmatos protocols = imap quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = $default_internal_user } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes driver = static } protocol lda { auth_socket_path = /var/run/dovecot/auth-master deliver_log_format = msgid=%m: %$ log_path = /home/vmail/dovecot-deliver.log } protocol imap { mail_max_userip_connections = 100 } I started to filter my email with imapfilter running on the same host as dovecot. I would therefore like to deliver email to a folder called PreINBOX so that imapfilter then sorts the email and ends up delivering only the useful email to INBOX. How can I change the name of the inbox dovecot delivers to? Best, -- Paulo Matos

1 1

IMAP Folder Mail Separator
by Alex 23 Aug '15

23 Aug '15

Hi, I have a fedora21 install with dovecot-2.2.18, and when creating a new subfolder with thunderbird, the actual folder name is "Folder1^Folder2" with a carat as a separator, instead of creating Folder2 in the Folder1 directory. Is this a thunderbird problem? I don't recall having this problem prior to upgrading to fedora21, so thought maybe it's a dovecot problem. Maybe the separator character is customizable? Thanks, Alex

3 5

migrating servers
by chris 23 Aug '15

23 Aug '15

Hi I am trying to migrate from a Centos dovecot 1.0.7 install to a debian dovecot 2.1.7 install. I thought simply replicating the maildirs would be fine (using rsync) but when I fetch mail from the new server using IMAP thunderbird wants to download all the messages again as duplicates. I searched the wiki over to see if I could find a solution and while it appeared I could use doveadm backup that seems to only work pushing changes from the new server to the old (wrong direction) and that program does not exist on the earlier version of dovecot on the old server. If I can be very blunt the documentation on the wiki assumes far too much knowledge from the reader. It is often hard to decipher exactly what is meant by many of the obtuse instructions. But that is an aside can anyone give me pointers on how to do this migration for all my users so they don't need to sort through hundreds of duplicated emails? Chris

2 1

Delivering email to Maildir PreINBOX
by Paulo Matos 22 Aug '15

22 Aug '15

Hi all, I have a running dovecot with: $ dovecot -n # 2.2.18: /etc/dovecot/dovecot.conf # OS: Linux 4.1.0-x86_64-linode59 x86_64 Fedora release 22 (Twenty Two) ext4 auth_debug = yes auth_mechanisms = plain login digest-md5 cram-md5 auth_verbose = yes auth_verbose_passwords = yes default_internal_user = root imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_debug = yes mail_location = maildir:/home/vmail/%d/%n/Maildir maildir_very_dirty_syncs = yes mbox_write_locks = fcntl namespace { inbox = yes location = prefix = INBOX. separator = . type = private } namespace inbox { 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 { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } postmaster_address = pmatos protocols = imap quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = $default_internal_user } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes driver = static } protocol lda { auth_socket_path = /var/run/dovecot/auth-master deliver_log_format = msgid=%m: %$ log_path = /home/vmail/dovecot-deliver.log } protocol imap { mail_max_userip_connections = 100 } I started to filter my email with imapfilter running on the same host as dovecot. I would therefore like to deliver email to a folder called PreINBOX so that imapfilter then sorts the email and ends up delivering only the useful email to INBOX. How can I change the name of the inbox dovecot delivers to? Best, -- Paulo Matos

4 5

Error: User initialization failed
by ＠lbutlr 19 Aug '15

19 Aug '15

OK, I obviously forgot something when setting up new user accounts (which I did via postfix admin to add them to the MySQL database): dovecot: lda(chance(a)example.com): Error: User initialization failed: Namespace '': Ambiguous mail location setting, don't know what to do with it: /usr/local/virtual/chance@ example.com (try prefixing it with mbox: or milder:) I have lots of mysql users defined and working, but do I need to manually create the mail store for new ones? (Sorry, it’s been quite a long time since I had to add accounts). -- You start a conversation you can't even finish it You're talkin' a lot, but you're not sayin' anything When I have nothing to say, my lips are sealed Say something once, why say it again?

2 3

logging into user mailboxes with admin credentials
by Noam Birnbaum 19 Aug '15

19 Aug '15

Hey folks, We are planning a migration away from Dovecot (sorry) to Google Apps and are trying to figure out how to migrate the contents of user mailboxes to the new provider. Normally we would use an IMAP migration tool to log into each user's mailbox on the old and new providers and transfer the data that way. However, there is no central directory service; all accounts are local. We have a large number of users and for both management and security reasons it's not feasible to compile a list of all IMAP passwords. Is there a way to log into user IMAP accounts on Dovecot using a central administrative credential? Thanks! Warmest and bestest, Noam 510-332-3828 cell Noam Birnbaum Mac Daddy http://www.maccentricsolutions.com 877.luv.macs x666 tweet @noamb Tech support ---> 877.luv.macs or support(a)maccentricsolutions.com Luvvv us? _Yelp us!_ <http://www.yelp.com/biz/maccentric-solutions-san-francisco>

2 1

NFSv4 delegation
by brd 18 Aug '15

18 Aug '15

hi all, i'm managing a large installation of a dovecot cluster in director + NFS backend architecture and we are moving from NFSv3 to NFSv4. Our NFS server is a Netapp in clustered mode and reading technical specs of NFSv4 delegation feature it seems that enabling delegation in this type of dovecot architecture should bring great benefits: only one backend server access a specific mailbox at a time (even deliveries are managed by director hashing via LMTP) so the getattr rpc calls should decrease significantly while the risk of conflicting delegations is very low (impacting negatively on the benefits obtainable). Can anyone confirm this hypothesis? I've heard that the linux implementation of NFSv4 delegation is mature only for read delegation (and not yet for write delegation): is this true? And, if true, could this fact limit the benefits of activating NFS delegation feature? Best regards -brd

4 11

pop3-login: Disconnected (tried to use disallowed plaintext auth)
by Benjamin Cimerman 18 Aug '15

18 Aug '15

Hi I have problem with dovecot 2.2.10 - plaintext auth without SSL is not working. I'm upgrading old server and want that settings "stay same" as on old server. SSL has to be optional. /var/log/maillog *pop3-login: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=_._._._, lip=_._._._, session=<cxPkm4Ud5gBb7YZ/>* my settings: [root@mail dovecot]# grep ssl * -R -n *conf.d/10-ssl.conf:8:ssl = yes* *conf.d/10-ssl.conf:40:ssl_verify_client_cert = no* *conf.d/10-auth.conf:90:auth_ssl_require_client_cert = no* *dovecot.conf:7:ssl = yes* [root@mail dovecot]# grep plain * -R -n *conf.d/10-auth.conf:11:disable_plaintext_auth = no* *conf.d/10-auth.conf:101:auth_mechanisms = plain login* Thanx you for any help.

1 0

Segfaults after upgrade to Debian Jessie
by Andrew Beverley 18 Aug '15

18 Aug '15

Hi, I've just upgrade from Debian Wheezy to Debian Jessie and am getting: Fatal: master: service(lmtp): child 6761 killed with signal 11 (core dumped) It seems to be something to do with sieve. When I disable that from lmtp then everything works fine. OS: Debian Jessie Dovecot version: 2.2.13 CPU: x86 This is the gdb output: Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/lmtp'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f8e4c94f626 in sieve_validator_register_command () from /usr/lib/dovecot/libdovecot-sieve.so.0 And dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 8.1 ext3 auth_mechanisms = plain login dict { sieve = mysql:/etc/dovecot/pigeonhole-sieve.dict } mail_location = maildir:/var/mail/vhosts/%d/%n mail_privileged_group = mail 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 vnd.dovecot.extdata 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 } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = dict:proxy::sieve;name=active sieve_dir = ~/sieve sieve_extdata_dict_uri = proxy::sieve sieve_plugins = sieve_extdata } protocols = " imap lmtp sieve" service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service dict { unix_listener dict { mode = 0600 user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/ssl/certs/ctrlo.com.pem ssl_key = </etc/ssl/private/ctrlo.com.key userdb { driver = passwd } userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } protocol imap { mail_max_userip_connections = 20 } Any ideas? Thanks, Andy

2 16

multiple messages per second to a single mailbox
by Chad M Stewart 18 Aug '15

18 Aug '15

Dovecot 2.2.18 on CentOS 6 I have a pair of servers setup with MySQL, Postfix, and Dovecot. Replication is setup and working between the two dovecot instances. The problem I'm running into is that a single mailbox receives a lot of messages, at times the rate is multiple messages per second. Delivery from Postfix to Dovecot is via tcp based LMTP. When I do 'ps -aef|grep lmtp|wc -l' I get 62 and does not appear to go higher than that. At the moment I have 4500 and 8300 messages queued on two Postfix instances waiting to deliver via LMTP to the same dovecot instance. Deliveries only happen via LMTP and only one of the two nodes actually gets the deliveries. What I'm seeing is very high load on the system (40) and queues building on the Postfix side. Replication is keeping up. Looking at the logs now I see anywhere from 4-7 messages per second delivered to this single mailbox. I would like to increase that rate a lot. These machines are VMs hosted on Xenserver 6.x. I have them setup with 8 vCPUs (2 sockets with 4 cores per socket), the dom0 machines have dual HBA connectors back to a SAN and have 128 CPUs and 256GB of RAM and are not taxed. I added a 2nd virtual disk that is used for storing mailbox data. It is ext4 and has noatime set during mount. /var is also mounted with noatime. The performance graphs in XenCenter show nearly all 8 vCPUs at about 50%, and the writes on the mailbox data disk are about 20%. iostat is showing mostly <5 for await times for the disks, though I do see a 10 now and again. I'm guessing that maybe I'm hitting a mailbox locking issue and not sure how to reduce the contention and thereby increase the delivery rate to this mailbox. -Chad

5 12