- dovecot - dovecot.org

Is it safe to mix dovecot import/backup/sync between dovecot versions 2.2.30.2 and 2.3.7.1?
by Gerben Wierda 22 Dec '19

22 Dec '19

I am migrating a server. The old one uses dovecot 2.2.30.2 and the new one 2.3.7.1. I don’t want to use any tool that might influence flags on messages. I am using Maildir format on both ends and I have a way to let one server access the data on the other (either using an rsync or a direct access). Could I set up a sync between both to create a smooth migration? Gerben Wierda Chess and the Art of Enterprise Architecture <http://enterprisechess.com/> Mastering ArchiMate <http://masteringarchimate.com/> Architecture for Real Enterprises <https://www.infoworld.com/blog/architecture-for-real-enterprises/> at InfoWorld On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ

2 2

dovecot rejecting connects
by Roy 22 Dec '19

22 Dec '19

I am a newbie to dovecot but not postfix and centos I created a new VM with Centos 8 and installed dovecot and postfix. Postfix is working fine but dovecot rejects connections from anything but the local machine. Locally Trying 10.10.100.157... Connected to 10.10.100.157. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready. Machine on same subnet. Windows, Linux, etc. Doesn't seem to matter telnet 10.10.100.157 143 Connecting To 10.10.100.157... Could not open connection to the host, on port 143: Connect failed I made sure the iptables are empty so it doesn't seem to be a firewall issue I put some LOG statements in the iptables and it showed the connect packet arriving and the response packet was ICMP type 3 code 13. Any ideas? Roy

3 4

unable to edit wiki 2, here's the edit:
by Steve Newcomb 19 Dec '19

19 Dec '19

In https://wiki.dovecot.org/Migration/Courier , mail_location = maildir:~/Maildir namespace { prefix = INBOX. separator = . inbox = yes } ... is wrong. Apparently it should be ... mail_location = maildir:~/INBOX ...which at least seemed to work, although (by that time?) I wound up re-downloading all mail. Steve Newcomb srn(a)coolheads.com (Unable to edit the wiki page... Mysterious question stood in the way, something like, "How do you prevent spam?" Evidently I don't know the correct answer.

1 0

slow logins over login_trusted_network
by Wojciech Puchar 18 Dec '19

18 Dec '19

i've upgraded dovecot on my server to 2.3.9 works properly but saslauthd that uses it for rimap authentication over 127.0.0.1 works SLOW. You need to wait 15-20 seconds before authentication. only imap login over 127.0.0.1 is slowed down, while over any other IP is quick. i had this problem with older version of dovecot but it was about adding login_trusted_networks = 127.0.0.1 but i already have this and logins is slow. how to disable throttling (or better - put other limits) for 127.0.0.1?

3 5

DSync replication error
by 横山航平 18 Dec '19

18 Dec '19

Please tell me about Dsync replicator. The following are set to enable the "replication" plug-in /etc/dovecot/conf.d/10-mail.conf *---mail_plugins = notify replication---* And I made the following file /etc/dovecot/conf.d/30-dsync.conf *---service replicator { process_min_avail = 1} dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%uplugin { mail_replica = remote:root@"ServerIP"} service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail }} service replicator { unix_listener replicator-doveadm { mode = 0600 }} replication_max_conns = 10 plugin { # When saving a new mail via IMAP or delivering a mail via LDA/LMTP, # wait for the mail to be synced to the remote site. If it doesn't finish # in 2 seconds, return success anyway. # replication_sync_timeout = 2s}---* But replication gives an error --- *Error: open(/var/run/dovecot/replication-notify-fifo) failed: Permission denied* --- Why is this? By the way, When 30-dsync.conf is changed as follows, it works only for one user *---service aggregator { fifo_listener replication-notify-fifo { user = "one user name" } unix_listener replication-notify { user = "one user name" }}---* However, I want to work with all mail users. Please help me what to do. My configuration is as follows *---# 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf# OS: Linux 3.10.0-1062.9.1.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) # Hostname: test1.s1.iwate-np.co.jp <http://test1.s1.iwate-np.co.jp>dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%ufirst_valid_uid = 1000mail_location = maildir:~/Maildirmail_plugins = notify replicationmbox_write_locks = fcntlnamespace 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}plugin { mail_replica = remote:root@192.168.4.2 <remote%3Aroot(a)192.168.4.2>}service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail }}service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 }}ssl = requiredssl_cert = </etc/pki/dovecot/certs/dovecot.pemssl_key = # hidden, use -P to show ituserdb { driver = passwd}---*

2 2

Local lmtp proxy on backend server
by Marc Roos 17 Dec '19

17 Dec '19

I receive a local mail when I do a 'mail test' on a backend svr1 with this[0] configuration. However when I just add only one configuration change 'lmtp_proxy = yes' I am getting these errors[1]. I would expect this email to still be delivered locally, should this be working or do I misunderstand the lmtp proxy functionality? [0] passdb { args = auth_verbose = default default_fields = proxy=y host=svr1 deny = no driver = pam [1] Dec 15 23:28:48 svr1 dovecot: lmtp(9270): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= Dec 15 23:28:48 svr1 dovecot: lmtp(9270): Connect from local Dec 15 23:28:48 svr1 dovecot: auth: Debug: master in: PASS#0111#011test#011service=lmtp Dec 15 23:28:48 svr1 dovecot: auth: Debug: pam(test): passdb doesn't support credential lookups Dec 15 23:28:48 svr1 dovecot: auth: Debug: passdb out: FAIL#0111#011reason=Configured passdbs don't support credentials lookups Dec 15 23:28:48 svr1 dovecot: lmtp(9270): Debug: user test: Auth PASS lookup returned temporary failure: reason=Configured passdbs don't support credentials lookups Dec 15 23:28:48 svr1 dovecot: lmtp(9270): Debug: auth PASS input: reason=Configured passdbs don't support credentials lookups dovecot-pigeonhole-2.2.36-3.el7_7.1.x86_64 dovecot-2.2.36-3.el7_7.1.x86_64

2 10

Re: Shared namespace is empty after migration to new Dovecot installation
by Peter Reinhold 17 Dec '19

17 Dec '19

On 2019-12-09 09:42, Aki Tuomi wrote: >> That I can, here (anonymized where relevant) >> > > Config looks fine. Have you tried > > 'A1 SELECT Shared/user(a)sharer.dk'? Yields this, which is the same I got when trying to debug using doveadm acl, it seems like the shared mailboxes aren't placed in the shared namespace at all. A1 SELECT Shared/user(a)sharer.dk A1 NO Mailbox doesn't exist: Shared/user(a)sharer.dk (0.006 + 0.000 + 0.005 secs). -- Peter Reinhold

2 5

Gmail and POP3
by Yannick SIEGLER 17 Dec '19

17 Dec '19

Hi everyone, I'm new to this ML. I have some issue with GMail import settings... I run a dovecot server (2.3.4.1) on Debian10 and I try to connect to my accounts from GMail. It's work fine from thunderbird in pop3,pop3s, imap, imaps... Submission work too... But it won't work on GMail except if I set ssl=yes and disable_plaintext_auth = no... Then GMail connect without SSL or TLS... And in plaintext.... Very unsecure... I can send mail with submission from GMail and ssl=require, that's ok. If I try to connect with SSL activated I've got : pop3-login: Disconnected: Too many bad commands And If I try to connect on port 995 with SSL GMail say that I have some SSL error, and the log says : auth: Debug: auth client connected (pid=21831) pop3-login: Debug: SSL: where=0x10, ret=1: before SSL initialization pop3-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization pop3-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization pop3-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec pop3-login: Debug: SSL: where=0x2001, ret=1: TLSv1.3 write encrypted extensions pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate pop3-login: Debug: SSL: where=0x2001, ret=1: TLSv1.3 write server certificate verify pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished pop3-login: Debug: SSL: where=0x2001, ret=1: TLSv1.3 early data pop3-login: Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data pop3-login: Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data pop3-login: Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data pop3-login: Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data pop3-login: Debug: SSL: where=0x2001, ret=1: TLSv1.3 early data pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished pop3-login: Debug: SSL: where=0x20, ret=1: SSLv3/TLS write session ticket pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket pop3-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully pop3-login: Debug: SSL error: Connection closed But as I say, all is working fine from Thunderbird... For the SSL problem this is maybe because GMail doesn't like this configuration in debian for openssl ? [system_default_sect] MinProtocol = TLSv1.2 CipherString = DEFAULT@SECLEVEL=2 Maybe should I try to set MinProtocol = None CipherString = DEFAULT But this make a lot of security change on my opinion... Do someone have any tips or suggestion about my problem ? Thx Yannick

2 2

CentOS x64 compilation fails.
by Mart Pirita 16 Dec '19

16 Dec '19

Hello. I have problems to compile Dovecot2.2.13 with rpmbuild using options: ./configure \ --prefix=/usr \ --with-ssl=openssl \ --with-ssldir=/etc/ssl \ --sysconfdir=/etc \ --without-vpopmail \ --with-pam \ --without-bsdauth \ --without-sql \ --without-nss \ --without-ldap \ --without-pgsql \ --without-mysql \ --without-sqlite \ --with-rundir=/var/run/dovecot \ --without-deliver \ --without-gssapi make Using CentOS 5.11, option - rpmbuild -ba dovecot2.2.spec fails with error: /bin/mkdir -p '/var/tmp/dovecot-2.2.13-mp-root/usr/lib64/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c libdovecot-storage.la '/var/tmp/dovecot-2.2.13-mp-root/usr/lib64/dovecot' libtool: install: error: cannot install `libdovecot-storage.la' to a directory not ending in /usr/lib/dovecot make[4]: *** [install-pkglibLTLIBRARIES] Error 1 make[4]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.13/src/lib-storage' make[3]: *** [install-am] Error 2 make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.13/src/lib-storage' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.13/src/lib-storage' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.13/src' make: *** [install-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.14076 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.14076 (%install) But using CentOS 5.11with option- rpmbuild --target=i686 -ba dovecot2.2.spec works fine. However, using CentOS 6.5, with option - rpmbuild -ba dovecot2.2.spec fails with error: /bin/mkdir -p '/root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.x86_64/usr/lib64/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c libdovecot-storage.la '/root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.x86_64/usr/lib64/dovecot' libtool: install: error: cannot install `libdovecot-storage.la' to a directory not ending in /usr/lib/dovecot make[4]: *** [install-pkglibLTLIBRARIES] Error 1 make[4]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.13/src/lib-storage' make[3]: *** [install-am] Error 2 make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.13/src/lib-storage' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.13/src/lib-storage' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.13/src' make: *** [install-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.HP3meN (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.HP3meN (%install) But when CentOS 5.11with option rpmbuild --target=i686 -ba dovecot2.2.spec suceeds, CentOS 6.5still fails: cpio: dovecot-2.2.13/src/lib-compression/abspath.c: Cannot stat: No such file or directory cpio: dovecot-2.2.13/src/lib-compression/compat.h: Cannot stat: No such file or directory cpio: dovecot-2.2.13/src/lib-compression/lib.h: Cannot stat: No such file or directory 18096 blocks + /usr/lib/rpm/check-buildroot /root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.i386/usr/lib/dovecot/dovecot-config:LIBDOVECOT='-L/root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.i386/usr/lib/dovecot -ldovecot' /root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.i386/usr/lib/dovecot/dovecot-config:LIBDOVECOT_INCLUDE=-I/root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.i386/usr/include/dovecot Found '/root/rpmbuild/BUILDROOT/dovecot-2.2.13-mp.i386' in installed files; aborting error: Bad exit status from /var/tmp/rpm-tmp.69mGY0 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.69mGY0 (%install) How to fix these errors? -- Mart

5 8

Suddenly sieve no longer working
by Heiko W. Rupp 16 Dec '19

16 Dec '19

Hey, I have a successful setup with dovecot and sieve and since a few days sieve is all of a sudden no longer working. I am on OSX and my mta is an older version of postfix (apple supplied). Has anyone gone through that and has some hints on how to best debug (and fix) that? Thanks a lot Heiko -- hwr(a)pilhuhn.de m:0179/207 4919 b:http://pilhuhn.blogspot.com

2 2