- dovecot - dovecot.org

Re: Disallow acces via imap, but keep lmtp running
by Julian Kippels 16 Dec '20

16 Dec '20

I thought about that, but that would also kill their access to wifi and other services, because it all comes from the same LDAP. Julian Am Tue, 15 Dec 2020 23:37:58 +0100 schrieb Jos <jos(a)cloudzeeland.nl>: > You could change their password temporily and do the migration? > > — Verstuurd via een mobiele telefoon > > > Op 15 dec. 2020 om 23:22 heeft Julian Kippels <kippels(a)hhu.de> het > > volgende geschreven: > > > > Hi all, > > > > what is the best way to temporarily disable access to a mailbox via > > imap, but keep it possible to deliver to the mailbox via lmtp? > > I want to migrate some mailboxes around and would like to ensure > > that the users cannot access their mail while doing so. > > I would like to keep the users from logging in entirely rather than > > setting ACLs. > > > > Thanks in advance > > Julian

3 2

Dovecot Director scaling / performance
by tim＠linux-daus.de 15 Dec '20

15 Dec '20

Hi, currently i'm going to evaluate the Dovecot Director. Are there someone with experience how the Dovecot Director does scale? The last current information i could find was a post on this mailing list from 2012: 4 Directors are well known, >75 are too much. Are there any more up to date experience regarding how many user (current and new/s) a single Dovecot Director/proxy node could handle and how many director nodes in a ring are known to work (well)? Best regards, Tim

2 1

Putting UIDL value into X-UIDL: header
by Süleyman Düzdaban 15 Dec '20

15 Dec '20

Hi, Is there any way to put UIDL value into X-UIDL: header with Dovecot or Sieve? As stated in https://wiki2.dovecot.org/Migration page QPopper can do that. I'm asking this for preventing clients who are using POP to re-download messages and making future migrations easy. I can really benefit from inserting UIDL values even only for the new messages from now on, but if there is any way to put it into all messages in all mailboxes (Maildir) I would be grateful for that too. Dovecot version: 2.3.8 (9df20d2db) Thanks in advance.

3 4

How to reset / remove all replicator users
by Ralf Becker 14 Dec '20

14 Dec '20

After creating a new replication pair, it was started with an old sqlite userdb, we use for iteration / replication. The situation was quickly resolved by generating a new sqlite userdb, as it is done hourly anyway. Unfortunately I can not get ride of all access users from the replication: / # doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 14 Waiting 'failed' requests 1 Total number of known users 724 / # doveadm user '*'|wc -l 507 The replication process creates again and again a lot (empty) mailboxes on both sides of the replication. I tried the obvious with no avail: / # doveadm replicator remove '*' Error: Replicator failed: User not found I also tried restarting the pair one after the other, but it seems the users to replicate are somewhere persisted. I'm also trying to delete the users from the newly created (empty) mailboxes, but the number of known users in "doveadm replicator status" is unchanged: root:/var/dovecot/imap# for domain in $(ls -1 |grep -v bb-trunk.egroupware.de|grep -v outdoor-training.de|grep -v rbz-); do for user in $domain/*; do echo "$(basename $user)@$domain"; doveadm replicator remove "$(basename $user)@$domain"; done; rm -rf $domain; done Any idea what else I can do, or where the replication stores it's users? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

2 1

How to setup Dovecot director in a NAT-like environment?
by Richard Mader 14 Dec '20

14 Dec '20

How can I setup Dovecot director in a NAT like environment? My mailservers are running within docker and one of them behind a router, so the IP that dovecot binds to does not match the IP that other mailservers have to use to connect to them. Since when running director the servers connect to each other, I'd guess I'd have to set the external IP of the servers in the "director_servers". If I do that I'm unable to start the director nodes since they cannnot find out which of the addresses is their own. I had a quick peek at the sourcecode and director detects its own address by trying to bind to all of the addresses. Since we're behind a NAT, that will of course fail for its external IP. When I set the local address or localhost in the "director_servers" directive, then the director nodes are able to start but they are denied when connecting to other nodes. When using the NAT-internal IP I've got the following error: > Error: Remote director thinks it's someone else (connected to > <other-directors-external-ip>:9090, remote says it's > <other-directors-internal-ip>:9090) When using localhost/127.0.0.1 then I get: > Info: Connecting to <other-directors-external-ip>:9090 (as 127.0.0.1): > Alone in director ring - trying to connect to others > Error: connect(<other-directors-external-ip>:9090) failed: Invalid > argument Is it somehow possible to tell director which of the addresses within "director_servers" is its own address, that it then advertises to other servers, instead of trying figuring that out itself by trying to bind to all ip-addresses on startup? Kafka e.g. has the "advertised.listeners" property to set a custom host to announce to clients and to other Kafka nodes. If there is not such a property or any other workaround, I might consider implementing this into director myself. Although I might need some help getting started since this is my first time contributing to a non Scala/Java or Typescript/NodeJS Project. So far I've discovered that Github seems to be the official repo and is not just a mirror and I was able to compile it on my machine. Now I've got questions such as, where can I find the binaries that I've just compiled and whats the best way to get them running locally and to test my changes, where are unit tests located, ...? Best Regards, Richard

2 1

Migrate mailbox from NFS folder to new NFS folder
by Claudio Corvino 14 Dec '20

14 Dec '20

Hi everyone, I need to migrate many user mailboxes from an NFS folder to a new NFS folder, both mounted on the same Dovecot server (2.2.27). Once migrated, users will connect to a new Dovecot server (2.3.4.1). I would like to know how to use /doveadm backup/ (or sync?) instead of /rsync/ as I noted that after migration with rsync I have duplicates and some e-mails marked as unread. What is the correct way to achieve this? Thanks Cheers

2 1

Unexpected behavior of doveadm mailbox delete -e -s
by Mar Alegre 13 Dec '20

13 Dec '20

Hello, I have encountered what I believe to be a bug, or at least inaccurate documentation. I am running version 2.3.4.1 of Dovecot (installed via the default repo for Debian 10), so my apologies if this has been fixed in a more recent version. I tried to look for changelogs but was not able to find any. The `doveadm mailbox delete` command accepts flags `-e` and `-s` (among others). The flags are described by both the man pages and the wiki as follows: - `-e`: Require mailboxes to be empty before deleting. - `-s`: Unsubscribe deleted mailboxes. Based on these descriptions, I would expect that when both of these flags are combined, a directory that is not empty would be neither deleted nor unsubscribed. However, I have discovered that when I run the command `doveadm mailbox delete -u $myusername -e -s $non_empty_dir`, the result is that the directory is not deleted, but it *is* unsubscribed. I assume this is a bug, but if it is intended, the documentation should probably be updated to more clearly communicate that the `-s` flag will cause a directory to be unsubscribed even if it is not deleted. Best, Mar Alegre

2 1

fyi: please change /var/run to /run in debian buster repository
by Michael 12 Dec '20

12 Dec '20

hey, just one minor thing: if there's any time left, please change in the repository debian/buster in the package dovecot-core in the file /lib/systemd/system/dovecot.service the line PIDFile=/var/run/dovecot/master.pid to PIDFile=/run/dovecot/master.pid because systemd always shows the following warning: Dec 12 15:46:30 mail systemd[1]: /lib/systemd/system/dovecot.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/dovecot/master.pid → /run/dovecot/master.pid; please update the unit file accordingly. creating a drop-in in /etc/systemd/system/dovecot.service.d/ doesn't do anything. greetings...

2 1

important message
by jk00100033＠gmail.com 12 Dec '20

12 Dec '20

I've invited you to fill out the following form: Untitled form To fill it out, visit: https://docs.google.com/forms/d/e/1FAIpQLSeqI7QUpet4levWQvhvUuqn1Au-fqPDo0W… Greetings! To You Mr. Joe is my name; I work in a Bank here in Benin. And I personally handle transactions of Mr. Martin Quick who eventually died on the 5th of February 2017 from injuries sustained in a road accident that happened 3 years ago. Prior to his death, Mr. Martin Quick lived and worked in Benin Republic and was doing Contracting with Benin Energy dept. He has (Four million, three hundred thousand Euros) in a fixed account with the bank with no other beneficiary. Now I write to seek your consent to present you as an oversea based partner to stand in as next of kin to the late Mr. Martin Quick. Let me know if it is ok to work with you. please email me in my private email for more details ( kukuaj001(a)gmail.com ) please email me in my private email for more details ( kukuaj001(a)gmail.com ) My best Regards Mr. Joe. Google Forms: Create and analyze surveys.

4 3

Potential issue with lmtp_rawlog_dir when using TLS
by John Fawcett 11 Dec '20

11 Dec '20

Hi not sure why this happens, but looks like lmtp_rawlog_dir blocks the successful negotiation of an lmtp starttls connection. Reproducible with openssl s_client. Two runs with only difference the presence of lmtp_rawlog_dir setting in dovecot config. Failed connection with lmtp_rawlog_dir Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Connect from ::1 Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x10, ret=1: before SSL initialization Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x2001, ret=1: before SSL initialization Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL: where=0x2002, ret=-1: error Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL error: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Error: lmtp-server: conn [::1]:53876 [2]: SSL handshake failed: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Debug: SSL error: SSL_accept() syscall failed: Invalid argument Dec 10 21:01:31 server03 dovecot[41002]: lmtp(41021): Disconnect from ::1: SSL Initialization failed (state=READY) Successful connection without lmtp_rawlog_dir Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Connect from ::1 Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x10, ret=1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: before SSL initialization Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL_get_servername() failed Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 write encrypted extensions Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 write server certificate verify Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=-1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: TLSv1.3 early data Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x20, ret=1: SSLv3/TLS write session ticket Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket Dec 10 20:59:07 server03 dovecot[40970]: lmtp(40988): Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully John

1 0