- dovecot - dovecot.org

Duplicate mails on pop3 expunge with dsync replication on 2.2.35 (2.2.33.2 works)
by Gerald Galster 27 Mar '18

27 Mar '18

Hello, consider the following setup with dovecot 2.2.35: smtp/587 (subject: test 1535) | | mx2a.example.com --> dsync/ssh --> mx2b.example.com | pop3 fetch/expunge (uid 23) | !! dsync (copy from INBOX -> uid 24) /| dsync (expunge uid 23) / The pop3 client deletes mail from the server which triggers a copy from INBOX before it is expunged. On the next pop3 fetch you get the copy of the mail you thought had been expunged. This occurs only if mail is received by smtp on mx2a, synced to mx2b via dsync/ssh and then expunged via pop3 on mx2b. It does not occur if mail is received and expunged on mx2b. As a temporary workaround the system has been downgraded to 2.2.33.2. There are no duplicate emails after expunge with this version. 2.2.34 has not been tested. Does anyone know if there were changes in the dsync code from 2.2.33.2 to 2.2.35? Log: (mail received on mx2a.example.com and delivered via dsync to mx2b.example.com, then expunged via pop3 on mx2b.example.com -> copy/duplicate) Mar 26 15:35:57 mx2b.example.com dovecot[3825]: pop3-login: Login: user=<poptest(a)example.com>, method=PLAIN, rip=91.0.0.1, lip=188.0.0.1, mpid=3922, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Mar 26 15:35:58 mx2b.example.com dovecot[3825]: pop3(poptest(a)example.com): expunge: box=INBOX, uid=23, msgid=<ACD482CD-443E-479A-A9E9-67549E186E35(a)example.com>, size=1210, subject=test 1535 Mar 26 15:35:58 mx2b.example.com dovecot[3825]: pop3(poptest(a)example.com): Disconnected: Logged out top=0/0, retr=1/1259, del=1/1, size=1242 Mar 26 15:35:58 mx2b.example.com dovecot[3825]: doveadm: Error: dsync-remote(poptest(a)example.com): Info: copy from INBOX: box=INBOX, uid=24, msgid=<ACD482CD-443E-479A-A9E9-67549E186E35(a)example.com>, size=1210, subject=test 1535 Mar 26 15:35:58 mx2b.example.com dovecot[3825]: doveadm: Error: dsync-remote(poptest(a)example.com): Info: expunge: box=INBOX, uid=23, msgid=<ACD482CD-443E-479A-A9E9-67549E186E35(a)example.com>, size=1210, subject=test 1535 (mail received on mx2b.example.com and expunged via pop3 on mx2b.example.com -> no copy/duplicate) Mar 26 15:36:09 mx2b.example.com dovecot[3825]: pop3-login: Login: user=<poptest(a)example.com>, method=PLAIN, rip=91.0.0.1, lip=188.0.0.1, mpid=3927, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Mar 26 15:36:09 mx2b.example.com dovecot[3825]: pop3(poptest(a)example.com): expunge: box=INBOX, uid=24, msgid=<ACD482CD-443E-479A-A9E9-67549E186E35(a)example.com>, size=1210, subject=test 1535 Mar 26 15:36:09 mx2b.example.com dovecot[3825]: pop3(poptest(a)example.com): Disconnected: Logged out top=0/0, retr=1/1259, del=1/1, size=1242 Mar 26 15:36:10 mx2b.example.com dovecot[3825]: doveadm: Error: dsync-remote(poptest(a)example.com): Info: expunge: box=INBOX, uid=24, msgid=<ACD482CD-443E-479A-A9E9-67549E186E35(a)example.com>, size=1210, subject=test 1535 Thanks for looking into this Gerald

1 0

BUG: Unknown command in userdb socket: CPID?2625
by Vladimir Tiukhtin 26 Mar '18

26 Mar '18

Hi guys. I am getting strange error: BUG: Unknown command in userdb socket: CPID?2625 I am using service auth to authenticate users on postfix. *My OS*: # cat /etc/os-release NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION=" *My dovecot:* # dovecot --version 2.2.10 *My config*: service auth { unix_listener auth-userdb { mode = 0600 user = postfix group = postfix } } *My Postfix:* # rpm -qa | grep postf postfix-2.10.1-6.el7.x86_64 *Log*: Mar 25 16:52:33 mail-server postfix/smtpd[2625]: connect from unknown[10.254.200.202] Mar 25 16:52:33 mail-server dovecot[2621]: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Mar 25 16:52:33 mail-server dovecot[2621]: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so Mar 25 16:52:33 mail-server dovecot[2621]: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Mar 25 16:52:33 mail-server dovecot[2621]: auth: Debug: Read auth token secret from /var/run/dovecot//auth-token-secret.dat Mar 25 16:52:33 mail-server dovecot[2621]: auth: Debug: master in: CPID 2625 Mar 25 16:52:33 mail-server dovecot[2621]: auth: Error: BUG: Unknown command in userdb socket: CPID?2625 Mar 25 16:52:33 mail-server postfix/smtpd[2625]: fatal: no SASL authentication mechanisms Mar 25 16:52:34 mail-server postfix/master[2424]: warning: process /usr/libexec/postfix/smtpd pid 2625 exit status 1 Mar 25 16:52:34 mail-server postfix/master[2424]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling The interesting thing is IF I am taking off "-" (minus) from the socket name, everything works just perfect! So if I change config to: service auth { unix_listener blabla { mode = 0600 user = postfix group = postfix } } Mar 25 16:55:12 mail-server postfix/smtpd[2872]: connect from unknown[10.254.200.202] Mar 25 16:55:12 mail-server dovecot[2786]: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Mar 25 16:55:12 mail-server dovecot[2786]: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so Mar 25 16:55:12 mail-server dovecot[2786]: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Mar 25 16:55:12 mail-server dovecot[2786]: auth: Debug: Read auth token secret from /var/run/dovecot//auth-token-secret.dat Mar 25 16:55:12 mail-server dovecot[2786]: auth: Debug: auth client connected (pid=0) Mar 25 16:55:13 mail-server dovecot[2786]: auth: Debug: client in: AUTH 1 PLAIN service=smtp nologin lip=192.168.101.24 rip=10.254.200.202 secured resp=<hidden> Mar 25 16:55:13 mail-server dovecot[2786]: auth: Debug: cache(admin(a)asergis.com,10.254.200.202): miss Mar 25 16:55:13 mail-server dovecot[2786]: auth-worker(2878): Debug: Loading modules from directory: /usr/lib64/dovecot/auth Mar 25 16:55:13 mail-server dovecot[2786]: auth-worker(2878): Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so Mar 25 16:55:13 mail-server dovecot[2786]: auth-worker(2878): Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Mar 25 16:55:13 mail-server dovecot[2786]: auth-worker(2878): Debug: sql(admin(a)asergis.com,10.254.200.202): query: SELECT userid AS username, domain, password FROM users WHERE userid = 'admin' AND domain = 'asergis.com' Mar 25 16:55:13 mail-server dovecot[2786]: auth: Debug: client passdb out: OK 1 user=admin(a)asergis.com Mar 25 16:55:13 mail-server postfix/smtpd[2872]: 5C63030208: client=unknown[10.254.200.202], sasl_method=PLAIN, sasl_username=admin(a)asergis.com Mar 25 16:55:13 mail-server postfix/cleanup[2881]: 5C63030208: message-id=<d7706aa7-a2ad-6890-5590-e6f83b5ec3af(a)asergis.com> Mar 25 16:55:13 mail-server postfix/qmgr[2870]: 5C63030208: from=<admin(a)asergis.com>, size=622, nrcpt=1 (queue active) P.s. I don't mind to use socket without minus on its name. But this looks really strange. Thanks. You are awesome Vladimir

4 9

dsync backuping folders only, not emails
by Istvan Prosinger 26 Mar '18

26 Mar '18

Hi guys, I have an issue when I try to backup a remote mailbox, apparently it exits with no errors, it creates the mailbox folders in local, but it doesn't copy any email. doveadm -Dv -o dsync_features=empty-header-workaround -o imapc_host=secure.emailsrvr.com -o imapc_password='passwd' backup -R -u somemail(a)counselorinberlin.de imapc: Any hints? All the best, Istvan

1 0

Re: How to format auth-worker logs ?
by chaouche yacine 26 Mar '18

26 Mar '18

Hello list, Here's how auth-worker logs : Mar 26 10:56:38 auth-worker(1753): Info: sql(someuser(a)mydomain.tld,202.107.34.250): Password mismatch I would like to add the service used, like this : Mar 26 10:56:38 auth-worker(1753): Info: service=smtp sql(someuser(a)mydomain.tld,202.107.34.250): Password mismatch Any hints on how to acheive this ? Yassine.

1 0

Quota set-up problems
by Marcin Norek 26 Mar '18

26 Mar '18

Hi, I've recently started using Dovecot as our main mail storage, and it's performing great. But I have a question/problems with quotas. First of we are using: dovecot --version 2.2.32 (dfbe293d4) Dovecot is a part of a pre set environment (mailcow-dockerized) Aside the inbox namespace we have set-up an additional archive ns (Archiwum) like this namespace Archiwum { type = private separator = / prefix = Archiwum/ location = maildir:/var/vmail/arch/%n:INDEXPVT=~/Maildir/Archiwum subscriptions = yes list = yes mailbox "Wyslane" { auto = subscribe } } It is on an separate disk array, and works well. The problem is that this namespace and all its sub mailboxes should have different quota then the main storage so the config is like this quota = dict:Userquota::proxy::sqlquota quota2 = maildir:ns=Archiwum quota_rule = Trash:storage=+100% quota2_rule = *:ignore It works.. but not as intender. While mail located directly in the name space are ignored everything in sub mailbox of the Archiwum is still accounted to the main quota. I've been fighting this for some time now and can not find the solution. So help would be appreciated. Regards Marcin

1 0

destuser setting useless on LMTP proxy
by Jan-Pieter Cornet 26 Mar '18

26 Mar '18

I tried setting the "destuser" setting on the LMTP director as follows, to preserve the original envelope rcpt: protocol lmtp { auth_socket_path = director-userdb passdb { driver = ... override_fields = destuser=%{orig_user} } } The passdb driver would return the appropriate "user" for each alias. Suppose, for example, user1 has emails user1(a)domain.tld, but also alias1(a)domain.tld. Now, it turns out that setting the destuser *changes* the backend. It seems that when the passdb returns "destuser", that username is completely ignored and the hashing of the destuser determines the backend chosen. This is incorrect, the backend should be chosen based on the returned "user", and the "destuser" should only be used for the remote login (or rcpt, in case of LMTP). I'm using version 2.2.35. The problem seems to be in lmtp/commands.c, in client_proxy_rcpt_parse_fields, line 281-285 says: } else if (strcmp(key, "user") == 0 || strcmp(key, "destuser") == 0) { /* changing the username */ *address = value; } ... So it looks as if "user" and "destuser" are treated equally in the LMTP proxy. -- Jan-Pieter Cornet <johnpc(a)xs4all.net> Systeembeheer XS4ALL Internet bv www.xs4all.nl

2 1

Config problem: Service #0 is missing name
by Chris Ross 25 Mar '18

25 Mar '18

Okay. So following up on the problems I was discussing weeks ago, I have hand-patched dovecot to work around problems that I believe may be in libc and not dovecot. Trying to get the properly built and installed dovecot-2.2.35, however, is giving me an error I haven’t seen before. I presume that something got munged while I was hand-configuring and installing/uninstalling/reinstalling the port in recent weeks. Running on a FreeBSD 11-stable machine, when I run “service dovecot start”, it tells me: % sudo service dovecot start Starting dovecot. Fatal: Error reading configuration: Invalid settings: Service #0 is missing name /usr/local/etc/rc.d/dovecot: WARNING: failed to start dovecot % Surprisingly, googling for “Service #0 is missing name” didn’t yield a suggestion. My config is the same as it had been previously, I believe. Does anyone have an idea what might be wrong here? Thanks. - Chris

2 2

Config problem: Service #0 is missing name
by Chris Ross 25 Mar '18

25 Mar '18

Okay. So following up on the problems I was discussing weeks ago, I have hand-patched dovecot to work around problems that I believe may be in libc and not dovecot. Trying to get the properly built and installed dovecot-2.2.35, however, is giving me an error I haven’t seen before. I presume that something got munged while I was hand-configuring and installing/uninstalling/reinstalling the port in recent weeks. Running on a FreeBSD 11-stable machine, when I run “service dovecot start”, it tells me: % sudo service dovecot start Starting dovecot. Fatal: Error reading configuration: Invalid settings: Service #0 is missing name /usr/local/etc/rc.d/dovecot: WARNING: failed to start dovecot % Surprisingly, googling for “Service #0 is missing name” didn’t yield a suggestion. My config is the same as it had been previously, I believe. Does anyone have an idea what might be wrong here? Thanks. - Chris

1 0

recipient delimiter and sieve filters
by André Rodier 24 Mar '18

24 Mar '18

Dear all, I have found a way to automatically copy sent emails in the "Sent" folder, but I am not sure it is the simplest and more reliable way on the long term. I am open to suggestions if I miss a feature in Dovecot - or Postfix, that allows me to do this. I vaguely remember an SMTP extension that do that, but my memory could be wrong. First, I use "~" as a recipient delimiter. Then, I set up a postfix senders_bcc_map that add the ~Sent part: andre(a)homebox.space → bcc: andre~Sent(a)homebox.space It worked, except that the emails was marked as new. I tried first to add a global sieve filter like this: ---------------------------------------------------------------------- # Sieve script executed before for user require ["fileinto","imap4flags"]; # Move automatically copied emails to the sent folder # And mark them as read if header :contains "Delivered-To" "~Sent" { setflag "\\Seen"; fileinto "Sent"; } ---------------------------------------------------------------------- But it did not work, so maybe there is a trick I am not aware of. If I use the "Received" header and a regex, it works ---------------------------------------------------------------------- require ["fileinto","imap4flags","regex"]; if header :regex "Received" "for <[a-z]+~Sent(a)homebox.space>;" { setflag "\\Seen"; fileinto "Sent"; } ---------------------------------------------------------------------- This is working perfectly, but there is limitations, IMHO. - If the recipient delimiter is not compatible with a regex (e.g. "+"), then the script will probably fail. - Parsing every new email using a regular expression might not be the best option in term of system load. So, I finally use this: ---------------------------------------------------------------------- # Move automatically copied emails to the sent folder # And mark them as read require ["fileinto","imap4flags"]; if header :contains "Received" "~Sent" { setflag "\\Seen"; fileinto "Sent"; } ---------------------------------------------------------------------- My question is why the first one does not work? Does the email has been moved to the Sent folder, and dovecot sieve plugin is not able to find the email any more? Kind regards, André -- https://github.com/progmaticltd/homebox

2 2

lmtp service timeouting even after receiving full message
by Arkadiusz Miśkiewicz 23 Mar '18

23 Mar '18

I have a problem with some messages passed from exim to dovecot lmtp service: From exim debug: using socket /var/run/dovecot/lmtp LMTP<< 220 mbox8 ready LMTP>> LHLO mbox8... LMTP<< 250-mbox8 LMTP<< 250-STARTTLS LMTP<< 250-8BITMIME LMTP<< 250-ENHANCEDSTATUSCODES LMTP<< 250 PIPELINING LMTP>> MAIL FROM:... LMTP<< 250 2.1.0 OK LMTP>> RCPT TO:... LMTP<< 250 2.1.5 OK LMTP>> DATA LMTP<< 354 OK LMTP>> writing message and terminating "." cannot use sendfile for body: terminating dot wanted writing data block fd=6 size=6585 timeout=300 LMTP>> QUIT LMTP<< 421 4.4.2 mbox8 Disconnected client for inactivity now above "writting message and terminating" according to exim strace looks like this: 13413 22:07:24 write(2, " LMTP>> writing message and terminating \".\"\n", 45) = 45 <0.000018> 13413 22:07:24 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2705, ...}) = 0 <0.000025> 13413 22:07:24 write(2, "cannot use sendfile for body: terminating dot wanted\n", 53) = 53 <0.000022> 13413 22:07:24 lseek(3, 19, SEEK_SET) = 19 <0.000015> [...] 13413 22:07:24 write(2, "writing data block fd=6 size=6585 timeout=300\n", 46) = 46 <0.000019> 13413 22:07:24 alarm(300) = 0 <0.000013> 13413 22:07:24 write(6, "Return-path: [...] \nwrap\"><br></span></div>.\n", 6585) = 6585 <0.000023> and then exim waits for dovecot lmtp to say it accepted message but lmtp never does that. Isn't .\n always enough for dovecot to signal end of message? Because exim wrote full message to dovecot lmtp unix socket. Now the interesting this - exim does only one write() with 6585 bytes to write that message to lmtp. If exim needs more than one write() to do that (message is larger by some buffer) then it succeeds, dovecot accepts it. Could dovecot lmtp handling for single write() case be broken? dovecot 2.2.35 -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

2 4