Greetings,

As promised: I'm back.

After processing about 740 mails, it is again.

Via SSH based replication it isn't so dramatic, but exists.

See:

  mx1# doveadm fetch -u kir...@korins.ky 'uid' mailbox virtual.All | grep 
'^uid:' | tail -n 5
  uid: 145485
  uid: 145486
  uid: 145487
  uid: 145488
  uid: 145489
  mx1# doveadm fetch -u kir...@korins.ky hdr.Message-ID mailbox virtual.All uid 
145489
  hdr.message-id: 
<cadguc0gtckctzwpdwf4xyu63ozzjzycqmiuzgsuoeoz6gop...@mail.gmail.com>
  mx1#

vs

  mx2# doveadm fetch -u kir...@korins.ky 'uid' mailbox virtual.All | grep 
'^uid:' | tail -n 5
  uid: 145487
  uid: 145488
  uid: 145489
  uid: 145490
  uid: 145491
  mx2# doveadm fetch -u kir...@korins.ky hdr.Message-ID mailbox virtual.All uid 
145491
  hdr.message-id: 
<cadguc0gtckctzwpdwf4xyu63ozzjzycqmiuzgsuoeoz6gop...@mail.gmail.com>
  mx2# doveadm fetch -u kir...@korins.ky hdr.Message-ID mailbox virtual.All uid 
145489
  hdr.message-id: <87edd58shf.wl-kir...@korins.ky>
  mx2#

So, by some digging I discovered the mails which triggers an issue:

  mx1# doveadm fetch -u kir...@korins.ky 'uid' mailbox virtual.All | grep 
'^uid: 14484'
  uid: 14484
  uid: 144840
  uid: 144841
  uid: 144845
  uid: 144848
  uid: 144849
  mx1# doveadm fetch -u kir...@korins.ky hdr mailbox virtual.All uid 144841 | 
md5
  d65a22e12bd0c72d321a78d2efd3383b
  mx1# doveadm fetch -u kir...@korins.ky hdr mailbox virtual.All uid 144840 | 
md5
  25a8b53ecfd513cf9031dae0e9000d92
  mx1#

vs

  mx2# doveadm fetch -u kir...@korins.ky 'uid' mailbox virtual.All | grep 
'^uid: 14484'
  uid: 14484
  uid: 144840
  uid: 144842
  uid: 144846
  uid: 144849
  mx2# doveadm fetch -u kir...@korins.ky hdr mailbox virtual.All uid 144842 | 
md5
  d65a22e12bd0c72d321a78d2efd3383b
  mx2# doveadm fetch -u kir...@korins.ky hdr mailbox virtual.All uid 144840 | 
md5
  25a8b53ecfd513cf9031dae0e9000d92
  mx2#

this email 144841 / 144842 were delivered to mx1 at 17 Feb 2024 17:52:18
which allows me do check logs:

  mx1# zgrep '17:52:[123]' /var/log/maillog.3.gz
  Feb 17 17:52:15 mx1 smtpd[52094]: d7da603e4213f8ff smtp connected 
address=199.185.178.25 host=mail.openbsd.org
  Feb 17 17:52:15 mx1 smtpd[39991]: dnsbl: d7da603e4213f8ff DNS error 2 on 
cbl.abuseat.org
  Feb 17 17:52:17 mx1 smtpd[52094]: d7da603e4213f8ff smtp tls 
ciphers=TLSv1.3:TLS_AES_256_GCM_SHA384:256
  Feb 17 17:52:18 mx1 smtpd[52094]: d7da603e4213f8ff smtp message 
msgid=d8e3748c size=4552 nrcpt=1 proto=ESMTP
  Feb 17 17:52:18 mx1 smtpd[52094]: d7da603e4213f8ff smtp envelope 
evpid=d8e3748cc73371ec from=<owner-ports+m141...@openbsd.org> 
to=<kir...@korins.ky>
  Feb 17 17:52:19 mx1 dovecot: lmtp(15471): Connect from local
  Feb 17 17:52:19 mx1 dovecot: 
lmtp(kir...@korins.ky)<15471><h2dQAEPk0GVvPAAAeeMcAQ>: sieve: 
msgid=<4bc76d19-00f2-b60b-a87f-315adfd08...@grey.my.domain>: stored mail into 
mailbox 'INBOX'
  Feb 17 17:52:19 mx1 dovecot: lmtp(15471): Disconnect from local: Logged out 
(state=READY)
  Feb 17 17:52:19 mx1 smtpd[52094]: d7da603f60cff302 mda delivery 
evpid=d8e3748cc73371ec from=<owner-ports+m141...@openbsd.org> 
to=<kir...@korins.ky> rcpt=<kir...@korins.ky> user=vmail delay=1s result=Ok 
stat=Delivered
  Feb 17 17:52:19 mx1 smtpd[52094]: d7da603e4213f8ff smtp disconnected 
reason=quit
  mx1#

nothing, let check mx2:

  mx2# zgrep '17:52:[123]' /var/log/maillog.3.gz
  Feb 17 17:52:17 mx2 smtpd[3556]: 99938cb221b4cb0b smtp connected 
address=199.185.178.25 host=mail.openbsd.org
  Feb 17 17:52:20 mx2 smtpd[3556]: 99938cb221b4cb0b smtp tls 
ciphers=TLSv1.3:TLS_AES_256_GCM_SHA384:256
  Feb 17 17:52:30 mx2 smtpd[3556]: 99938cb221b4cb0b smtp disconnected 
reason=quit
  mx2#

nothing as well.

I do have full sync each 15 minutes, let check any dsync logs on bigger
interval (an hour):

  mx1# zgrep '17 1[78]:' /var/log/maillog.3.gz | grep dsync
  mx1#

and

  mx2# zgrep '17 1[78]:' /var/log/maillog.3.gz | grep dsync
  mx2#

Also hasn't got anything.

It seems that SSH based replication is better than TCP, and both of at
least works that I can't say about TCPS.

But it may introduce a kind of collision inside virtual boxes.

So, to future investigate an issue I've started to run dsync-server as:
doveadm -Dv dsync-server, I hoep that it allows to catch this.

And as usual re-created vurtial boxes.

--
wbr, Kirill
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Reply via email to