- dovecot - dovecot.org

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

Syncing two mail servers?
by Knute Johnson 17 Aug '15

17 Aug '15

I currently have a mail server using Dovecot and sendmail. I was thinking I would like to have a backup of my mail and an additional server in case of hardware failure. Is it possible to run two identical or nearly identical server setups and sync the mail files between them? If it is possible, in general terms how would one go about this? Thanks, -- Knute Johnson

2 2

Re: Duplicate mails with pop3 + dsync replication
by Nikolaos Milas 17 Aug '15

17 Aug '15

On 17/8/2015 2:29 μμ, Wolfgang Hennerbichler wrote: >> I was wondering if the same behavior persists with latest version(s), for example 2.2.18. > I don’t know, I have to deal with the packages that come with my distribution’s repository. > >> >If so, how do you overcome this issue? What is the suggested practice? > All I can say is that it works for me with the above setting and a cron-job that runs every minute which expunges mails for the pop3 users. > Thank you for your reply. I am on CentOS 5 and 6, but I am building RPMs for our test and production servers. I recently built v2.2.18 and I decided to give it a try. (I run it with postfix - also just upgraded to 2.11.6.) The issue seems to not occur any more. I had already tested on two test servers, and I hoped someone could provide independent feedback before I decided to upgrade production servers. However, I now also upgraded our two production servers and things seem to be running smoothly. All the best, Nick

1 0

sieve-filter failure problems
by Jost Krieger 17 Aug '15

17 Aug '15

I use sieve-filter for postprocessing misclassified mail. For false positives I use the following script: require [ "variables", "include", "fileinto" ]; global [ "FORCENOSPAM", "ext", "ext1" ]; set "FORCENOSPAM" "YES"; fileinto "JUNK-PRENOUCE"; if header :matches "Delivered-To" "*+*@*" { set "ext" "${2}"; set "ext1" "${2}"; } include :personal "production"; FORCENOSPAM suppresses the spam handling and the Delivered-To stuff tries to regenerate envelope info. This is my crontab entry: 1-57/4 * * * * cd ~kriegjcb; /usr/local/dovecot/bin/sieve-filter -v -e -W -u kriegjcb -m Spam/U0-failed ~kriegjcb/sieve/nospamfilter.sieve Spam/U0 Most things work fine, but a few of my rules will try to forward mail. This will fail and my idea was I handle this manually from the folder Spam/U0-failed. Unfortunately the mail will arrive there but will also be left in the source folder Spam/U0 and will be processed again every 4 minutes ... This is probably not intentional? Yours Jost Krieger -- | Jost.Krieger+sig(a)ruhr-uni-bochum.de Please help stamp out spam! | | Postmaster, JAPH, resident answer machine at RUB Comp. Center | | Sincere words are not sweet, sweet words are not sincere. | | Lao Tse, Tao Te King 81 |

2 2

Duplicate mails with pop3 + dsync replication
by Wolfgang Hennerbichler 17 Aug '15

17 Aug '15

Hi, When I enable (and it only happens when it is actually running) replication over TCP my users get duplicate mails via pop3. Here’s what happens: * User gets mail * Mail appears in (Maildir) new/ folder on both replicas * user retrieves mail (retr), calls dele. Mail still exists in new/ folder on both replicas. * user runs retr (and gets the duplicate) and dele a second time, the mail is actually removed. If I disable replication this behaviour goes away. I use dovecot from debian stable resources. Any help would _really_ be appreciated. I found one german thread that dealt with the same problem, but no solution for it (http://www.dovecot-buch.de/mailingliste/pop3-fehler-bei-delete-und-dsync-re…) wogri # dovecot --version 2.2.13 # dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.0 ext4 auth_verbose = yes doveadm_password = XXX first_valid_gid = 113 first_valid_uid = 108 last_valid_gid = 113 last_valid_uid = 108 mail_gid = dovecot mail_location = maildir:/var/mail/%n mail_plugins = quota fts fts_lucene virtual notify replication mail_temp_dir = /var/lib/dovecot/tmp mail_uid = dovecot namespace { list = children location = virtual:/var/mail/%n/virtual prefix = virtual. separator = . } namespace inbox { inbox = yes list = yes location = mailbox "Deleted Messages" { auto = subscribe special_use = \Trash } mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } [48/4646] mailbox Trash { special_use = \Trash } prefix = separator = . subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { default_language = de fts = lucene fts_lucene = whitespace_chars=@. mail_replica = tcp:172.16.1.1:12345 quota = maildir:User quota quota_rule = *:storage=4G quota_rule2 = Trash:storage=+100M quota_rule3 = Spam:ignore quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = /etc/sieve/%n.sieve sieve_default = /etc/sieve/default.sieve sieve_dir = ~/sieve sieve_extensions = +editheader } postmaster_address = postmaster(a)wogri.at protocols = " imap lmtp pop3" service aggregator { fifo_listener replication-notify-fifo { user = dovecot } unix_listener replication-notify { user = dovecot } } service doveadm { inet_listener { port = 12345 } } service imap { process_limit = 1024 } } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 2003 } user = dovecot } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service pop3 { process_limit = 1024 } service quota-warning { executable = script /usr/local/sbin/quota-warning.sh unix_listener quota-warning { user = dovecot } user = dovecot } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl = required ssl_cert = </etc/exim4/server.cert.pem ssl_key = </etc/exim4/server.key.pem userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = quota sieve virtual notify replication } protocol lda { mail_plugins = quota fts fts_lucene virtual notify replication sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = quota fts fts_lucene virtual notify replication imap_quota }

2 3

sieve and antispam
by Andrew McN 17 Aug '15

17 Aug '15

I have a fairly standard antispam/dspam setup: postfix delivers to dspam, which classifies and tags the mail, and then passes it to postfix which uses sieve to put mail into the appropriate folders based on dspam's classification. I also have the antispam plugin watching mail being moved between folders and re-training dpsam accordingly. If I now add some sieve filter rules which put incoming mail into appropriate folders, possibly overriding what would normally result from dspam's classification, will that be seen by the antispam plugin and used for training dspam? Regards, Andrew McNaughton

2 1

Re: Multidomain / IP Address Setup (Dovevot 2.2.10 on CentOS7 ) is failing: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM
by Christian Kivalo 16 Aug '15

16 Aug '15

>But can you explain why you use globally: > >ssl_cert = </etc/ssl/dovecot.pem >ssl_key = </etc/ssl/private/dovecot.pem > >and certs for any additional Domain each? > >## >local_name mail.pettijohn-web.com { > ssl_cert = </etc/ssl/mail.pettijohn-web.com.crt > ssl_key = </etc/ssl/private/mail.pettijohn-web.com.key >} >## he configured the top level "default" ssl_{cert,key} as requested by the documentation i may quote myself >from the dovecot ssl wiki page http://wiki2.dovecot.org/SSL/DovecotConfiguration >Multiple SSL certificates >Different certificates per IP and protocol > >[snip] > >Note that you will still need a top-level "default" ssl_key and ssl_cert as well, or you will receive errors. i think, but untested, this default ssl_{cert,key} are used for those clients that don't support SNI (as with apache, which uses the cert of the first site). >I configured it the way you do, but within the default >/etc/dovecot/confd structure but >i had no luck. I testet local_name (SNI), local, local <IPv6> >(dedicated >IPv6 Address but had no lock it should make no difference whether you use one large config file or the conf.d structure. your doveconf -n output would really be helpful regards - c >Configinfo: >1) MTA (Postfix 2.10.1) and MDA (Dovecot 2.2.10) configured on IPv6 >Addresses >2) The MTA and MDA are connected to MariaDB (the default MySQL >replacement on CentOS7 now for virtual domains, users, passwords, >aliaes ect >3) Postfix uses Dovecots SASL Implementation and Postfix and Dovecot >talking via LMTP and UNIX Sockets. > >Details: >### yum info postfix ### >Name : postfix >Arch : x86_64 >Epoche : 2 >Version : 2.10.1 >Release : 6.el7 >Size : 12 M >From : installed > From Source : debian.n-ix.net_centos_7_os_x86_64_ >Summary : Postfix Mail Transport Agent >URL : http://www.postfix.org >License : IBM and GPLv2+ >Description : Postfix is a Mail Transport Agent (MTA), supporting LDAP, > >SMTP AUTH (SASL), TLS > >### yum info dovecot ### >Name : dovecot >Arch : i686 >Epoche : 1 >Version : 2.2.10 >Ausgabe : 4.el7_0.1 >Größe : 3.2 M >Quelle : debian.n-ix.net_centos_7_os_x86_64_ >Summary : Secure imap and pop3 server >URL : http://www.dovecot.org/ >Lizenz : MIT and LGPLv2 >Description : Dovecot is an IMAP server for Linux/UNIX-like systems, >written with security > : primarily in mind. It also contains a small POP3 >server. It supports mail > : in either of maildir or mbox formats. > >Cheers, >Drav

1 0