- dovecot - dovecot.org

Apple mail works but thunderbird unable to connect
by Dshah 23 Jun '20

23 Jun '20

Dear all, I am stuck on this issue for days, I am able to connect on my IMAP server using Apple mail client but thunderbird shows me this error: "improper command pipelining after EHLO" I have tried all the ports in manual config but it just is not working while Apple Mail is able to connect perfectly, here are my configuration details of "postconf -n" , "doveconf -n" and " master.cf" https://pastebin.com/M3XG9DXA Thanks in advance.

6 12

problem with warnings
by Maciej Milaszewski 23 Jun '20

23 Jun '20

Hi I have a problem with warrnings in log Yesterday "big gays" change datastore and After this time i get warrnings in dovecot like: Warning: Created dotlock file's timestamp is different than current time (1592878268 vs 1592871191): /vmail/us/username/Maildir/dovecot-uidlist Before that there was no problem with warnnings I have dovecot director with 5 dovecot-nodes and storage always was mounted via nfs /vmail on /vmail type nfs (rw,noexec,noatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=120,acregmax=120,acdirmin=120,acdirmax=120,hard,nocto,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.100.41,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=xxx.xxx.xxx.xxx) # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.rc1 (debaa297) # OS: Linux 3.16.0-10-amd64 x86_64 Debian 8.11

1 0

from field encoding
by Jan Jurko 23 Jun '20

23 Jun '20

Good day. I have a dovecot 2.3.4.1 on debian 10 as an imap server. I found there are emails where the header field From has no encoding even if there is a name with special characters like Žlutý Kůň. The header looks like: From: "Žlutý Kůň" <zluty.kun(a)domain.tld> In this case the email client - roundcube, outlook etc. will show the From with wrong characters. This behaviour is typical only for dovecot, not for courier-imap - it was installed before dovecot with no problems. If there is corretly encoded From filed, the client shows the From correctly. Is there a way to set up the dovecot to show the field correctly even without encoding stuff? Some default/fallback settings? Thank you very much for your help Jan Jurko

2 3

nodelay passdb extra field does not work?
by Joe Wong 23 Jun '20

23 Jun '20

Hello, I have added 'y' as nodelay in my passdb query and I see the following in log: dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay does it mean this option is no longer supported in 2.3.10 ? - Joe

2 4

AW: replicator: Panic: data stack: Out of memory
by Thomas Tsiakalakis 23 Jun '20

23 Jun '20

I managed to convince the System that I really want a core dump Thomas Tsiakalakis Team Applikationsbetrieb GDV Dienstleistungs-GmbH Tel: +49(40)33449-4318 Fax: E-Mail: Thomas.Tsiakalakis(a)gdv-dl.de<mailto:Thomas.Tsiakalakis@gdv-dl.de> GDV Dienstleistungs-GmbH Glockengießerwall 1 D-20095 Hamburg www.gdv-dl.de<http://www.gdv-dl.de> Niederlassungen: Wilhelmstraße 43 / 43 G 10117 Berlin Frankenstraße 18 20097 Hamburg Sitz und Registergericht: Hamburg HRB 145291 USt.-IdNr : DE 205183123 Geschäftsführer: Dr. Jens Bartenwerfer Fred di Giuseppe Chiachiarella Aufsichtsratsvorsitzender: Werner Schmidt ------------------------------------------------------------------ Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe der E-Mail ist nicht gestattet. This e-mail and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Von: Thomas Tsiakalakis Gesendet: Donnerstag, 18. Juni 2020 16:26 An: 'dovecot(a)dovecot.org' <dovecot(a)dovecot.org> Betreff: replicator: Panic: data stack: Out of memory Hi, I have set up 2 SLES 15 Hosts with dovecot and replication. Everything seems to work fine but every time a message is delivered, I get an out of memory error in the logs. The Replication itself seems to work fine though. I increased default_vsz_limit to 512M but the only thing that changed was that dovecot was trying to allocate 1073741864 bytes instead of 268435496 As I said, I’m running SLES 15 SP1 and Dovecot 2.3.10 (0da0eff44) (both Hosts have the same version) Each Host currently has 8GB of Memory. # free -h total used free shared buff/cache available Mem: 7.8Gi 278Mi 7.3Gi 47Mi 183Mi 7.2Gi Swap: 4.0Gi 0B 4.0Gi # journalctl -f Jun 18 15:55:48 mail1 postfix/pickup[3457]: 18533C009C8: uid=0 from=<root> Jun 18 15:55:48 mail1 postfix/cleanup[3669]: 18533C009C8: message-id=<20200618135548.18533C009C8@mail1> Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: from=<root@mail1>, size=431, nrcpt=1 (queue active) Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Connect from local Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f8346d6d262] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f8346d6d37e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebcee) [0x7f8346d77cee] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebd91) [0x7f8346d77d91] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8346cd1f8b] -> /usr/lib64/dovecot/libdovecot.so.0(t_pop_last_unsafe+0) [0x7f8346d73660] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe7a50) [0x7f8346d73a50] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10eb58) [0x7f8346d9ab58] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe3ac5) [0x7f8346d6fac5] -> /usr/lib64/dovecot/libdovecot.so.0(buffer_write+0xf2) [0x7f8346d6fdb2] -> dovecot/replicator(replicator_queue_push+0xde) [0x5648989a5cde] -> dovecot/replicator(+0x5464) [0x5648989a5464] -> dovecot/replicator(+0x4a0b) [0x5648989a4a0b] -> dovecot/replicator(+0x4c02) [0x5648989a4c02] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f8346d90c99] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x134) [0x7f8346d92574] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f8346d90d9c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f8346d90fc8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f8346d01873] -> dovecot/replicator(main+0x1a0) [0x5648989a3cb0] -> /lib64/libc.so.6(__libc_start_main+0xea) [0x7f83468f534a] -> dovecot/replicator(_start+0x2a) [0x5648989a3d5a] Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Sync failure: Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Remote sent invalid input: - Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: msgid=<20200618135548.18533C009C8@mail1>: saved mail to INBOX Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Disconnect from local: Client has quit the connection (state=READY) Jun 18 15:55:48 mail1 postfix/lmtp[3672]: 18533C009C8: to=<test(a)example.com>, orig_to=<test(a)domain.com>, relay=mail1[private/dovecot-lmtp], delay=0.17, delays=0.02/0.01/0.02/0.13, dsn=2.0.0, status=sent (250 2.0.0 <test(a)example.com> q5sLCGRy615ZDgAATn/NZw Saved) Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: removed Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Fatal: master: service(replicator): child 2948 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2)

1 0

Updating wiki content
by Dan 22 Jun '20

22 Jun '20

Greetings, I'd like to contribute to the Dovecot wiki in regards to clients that lack the ability to support SNI. However the captcha doesn't make sense, I get a question "What do you do to prevent spam?". This is a loaded question which I'm uncertain what the answer should be. Thanks.

2 1

Bug[?]report: duplicate response
by Johannes Schilling 21 Jun '20

21 Jun '20

hi, i'm not sure if i've discovered a bug or if i'm not following the IMAP specs correctly. observations: { echo -en "a1 login foo bar\r\na2 notify set (subscribed (FlagChange SubscriptionChange MessageNew MessageExpunge))\r\n"; cat - } | openssl s_client -connect [my_dovecot_server]:993 produces the following output (aside from the openssl s_client cert-inspection stuff): 2020-06-21 12:26:02 * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot (Debian) ready. 2020-06-21 12:26:02 a1 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY LITERAL+ NOTIFY SPECIAL-USE] Logged in 2020-06-21 12:26:02 a2 OK NOTIFY completed (0.005 + 0.000 + 0.004 secs). 2020-06-21 12:26:02 a2 OK NOTIFY completed (0.002 + 0.000 + 0.001 secs). the first line is the pre-login welcome prompt, the second one the result of the "a1 login .." command and the third and fourth seem to be the answer to the "a2 notify set .." command, twice. from the different timings given, it seems the a2 command is actually executed twice. is this a case of "you're not allowed to pipeline commands like this" or a bug in dovecot (or both)? i attached the output of `dovecot -n`. best, dario

1 0

Mailfiles gets duplicated
by Jacques Schreiber 19 Jun '20

19 Jun '20

Hello, With my configuration Dovecot creates multiple duplicates (sometimes 2, sometimes 3, sometimes a plenty) of mailfiles when moving them into the Sent or the Trash folders. This does not affect the Inbox folder. I observed this while using Thunderbird on Ubuntu as a client as well as K9-Mail on Android, therefore I expect this comes from the Dovecot server and not from the client itself. It also appears that the duplicates does not have the size S= and vsize W= flags. Here is a short example of the last emails from my folder /.Sent/cur: -rw------- 1 pi pi 1,6M mars 24 22:18 1585084691.M834293P16489.raspberry-pi,S=1658182,W=1679758:2,S -rwx------ 1 pi pi 34M mars 24 22:20 1585084841.M415421P17104Q0Rc311b18de2edf536.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:22 1585084954.M254398P17175Q0R6c5a66e22ac3a3d2.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:46 1585086411.M317404P18117Q0R61ba34fb281e8eb5.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:51 1585086659.M435086P18251Q0R7e118d3bd7784c6d.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:53 1585086799.M821376P18319Q0R6b838db7f14a2302.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:54 1585086861.M788796P18398Q0Raaa98233db1f9b6a.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:00 1585087244.M616219P18629Q0R4d5856ac0d1b1337.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:01 1585087278.M581756P18651Q0R6a75f871d9e8f0aa.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:01 1585087296.M954701P18666Q0R0cce469807cb0aa8.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:05 1585087552.M557221P18793Q0R541dece72da12039.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:09 1585087759.M768686P18927Q0Rbc1c813e1b124702.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:10 1585087823.M232119P19026Q0R4086d52491835470.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:10 1585087855.M951407P19035Q0R4edd76369b804f54.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:22 1585088561.M364587P19476Q0Rdc0ac3a664f1a80f.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:24 1585088639.M90555P19512Q0R6214b0e915c88908.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:27 1585088859.M192671P19663Q0Re4562fb440f7a4be.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:28 1585088927.M926251P19699Q0Rbe7523140efc06e2.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:29 1585088962.M120826P19721Q0Rd66b5d585c41123b.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:31 1585089111.M427988P19799Q0R5b8e8a032adc33c8.raspberry-pi:2, -rwx------ 1 pi pi 1,6M mars 24 23:32 1585089138.M910049P19827Q1R1b4d834fadfb0fd6.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:33 1585089180.M811880P19839Q0R8c415b8fbf638018.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:34 1585089252.M333476P19878Q0R3b809c0f458a90e0.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:34 1585089293.M103544P19918Q0Rd9acc8d53f5c8b32.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:35 1585089314.M270143P19948Q0R1202a6fe81862880.raspberry-pi:2, -rw------- 1 pi pi 2,0M mars 29 13:01 1585479708.M437415P11486.raspberry-pi,S=2076767,W=2105374:2,S -rwx------ 1 pi pi 2,0M mars 29 13:02 1585479733.M94224P13150Q0R974361f29d7d9cdb.raspberry-pi:2, -rw------- 1 pi pi 2,5K mars 31 09:10 1585638623.M921769P12803.raspberry-pi,S=2511,W=2585:2,S -rwx------ 1 pi pi 3,0K mars 31 09:11 1585638671.M552885P12861Q0R878fb6aa8485b5c0.raspberry-pi:2, -rw------- 1 pi pi 19M avril 3 09:38 1585899475.M669440P24679.raspberry-pi,S=19757959,W=20028662:2,S -rwx------ 1 pi pi 19M avril 3 09:38 1585899531.M744009P25082Q0R0b61c7e8e7b723b4.raspberry-pi:2, -rw------- 1 pi pi 421 avril 3 14:52 1585918350.M591326P1027.raspberry-pi,S=421,W=434:2,S -rw------- 1 pi pi 421 avril 3 14:52 1585918360.M206900P1027.raspberry-pi,S=421,W=434:2,S -rw------- 1 pi pi 421 avril 3 14:52 1585918372.M255849P1032.raspberry-pi,S=421,W=434:2,S -rwx------ 1 pi pi 1,1K avril 3 14:53 1585918394.M224204P1071Q0R7e9bc28b2d8e7fc4.raspberry-pi:2, -rwx------ 1 pi pi 1,1K avril 3 14:53 1585918395.M884727P1073Q1Ra4a111c1e0f5a399.raspberry-pi:2, -rwx------ 1 pi pi 1,1K avril 3 14:53 1585918398.M36019P1077Q2R10960cdc588b3ede.raspberry-pi:2, Below are details about my configuration pi@raspberry-pi:~$ sudo uname --all Linux raspberry-pi 4.4.38+ #938 Thu Dec 15 15:17:54 GMT 2016 armv6l GNU/Linux pi@raspberry-pi:~$ mount [...] /dev/sda1 on /home/pi type ext4 (rw,noatime,nodiratime,data=ordered) [...] pi@raspberry-pi:/var/log$ sudo dovecot --version 2.2.13 pi@raspberry-pi:/var/log$ sudo dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 4.4.38+ armv6l Debian 8.0 ext4 disable_plaintext_auth = no mail_location = maildir:/home/pi/Mails/%u namespace { inbox = yes location = mailbox { auto = subscribe special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { auto = subscribe special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { auto = subscribe special_use = \Trash name = Trash } prefix = separator = / type = private name = inbox } passdb { driver = pam } passdb { args = /home/pi/Mails/dovecot_passwords driver = passwd-file } protocols = " imap" service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service { inet_listener { address = * port = 4143 name = imap } name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </home/pi/Mails/imap_ssl_certificate.crt ssl_key = </home/pi/Mails/imap_ssl_private.key userdb { driver = passwd } userdb { args = uid=1000 gid=1000 home=/var/mail/%u driver = static } protocol lmtp { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } }

1 1

replicator: Panic: data stack: Out of memory
by Thomas Tsiakalakis 18 Jun '20

18 Jun '20

Hi, I have set up 2 SLES 15 Hosts with dovecot and replication. Everything seems to work fine but every time a message is delivered, I get an out of memory error in the logs. The Replication itself seems to work fine though. I increased default_vsz_limit to 512M but the only thing that changed was that dovecot was trying to allocate 1073741864 bytes instead of 268435496 As I said, I’m running SLES 15 SP1 and Dovecot 2.3.10 (0da0eff44) (both Hosts have the same version) Each Host currently has 8GB of Memory. # free -h total used free shared buff/cache available Mem: 7.8Gi 278Mi 7.3Gi 47Mi 183Mi 7.2Gi Swap: 4.0Gi 0B 4.0Gi # journalctl -f Jun 18 15:55:48 mail1 postfix/pickup[3457]: 18533C009C8: uid=0 from=<root> Jun 18 15:55:48 mail1 postfix/cleanup[3669]: 18533C009C8: message-id=<20200618135548.18533C009C8@mail1> Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: from=<root@mail1>, size=431, nrcpt=1 (queue active) Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Connect from local Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f8346d6d262] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f8346d6d37e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebcee) [0x7f8346d77cee] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebd91) [0x7f8346d77d91] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8346cd1f8b] -> /usr/lib64/dovecot/libdovecot.so.0(t_pop_last_unsafe+0) [0x7f8346d73660] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe7a50) [0x7f8346d73a50] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10eb58) [0x7f8346d9ab58] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe3ac5) [0x7f8346d6fac5] -> /usr/lib64/dovecot/libdovecot.so.0(buffer_write+0xf2) [0x7f8346d6fdb2] -> dovecot/replicator(replicator_queue_push+0xde) [0x5648989a5cde] -> dovecot/replicator(+0x5464) [0x5648989a5464] -> dovecot/replicator(+0x4a0b) [0x5648989a4a0b] -> dovecot/replicator(+0x4c02) [0x5648989a4c02] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f8346d90c99] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x134) [0x7f8346d92574] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f8346d90d9c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f8346d90fc8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f8346d01873] -> dovecot/replicator(main+0x1a0) [0x5648989a3cb0] -> /lib64/libc.so.6(__libc_start_main+0xea) [0x7f83468f534a] -> dovecot/replicator(_start+0x2a) [0x5648989a3d5a] Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Sync failure: Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Remote sent invalid input: - Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: msgid=<20200618135548.18533C009C8@mail1>: saved mail to INBOX Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Disconnect from local: Client has quit the connection (state=READY) Jun 18 15:55:48 mail1 postfix/lmtp[3672]: 18533C009C8: to=<test(a)example.com>, orig_to=<test(a)domain.com>, relay=mail1[private/dovecot-lmtp], delay=0.17, delays=0.02/0.01/0.02/0.13, dsn=2.0.0, status=sent (250 2.0.0 <test(a)example.com> q5sLCGRy615ZDgAATn/NZw Saved) Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: removed Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Fatal: master: service(replicator): child 2948 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2) Thomas Tsiakalakis Team Applikationsbetrieb GDV Dienstleistungs-GmbH Tel: +49(40)33449-4318 Fax: E-Mail: Thomas.Tsiakalakis(a)gdv-dl.de<mailto:Thomas.Tsiakalakis@gdv-dl.de> GDV Dienstleistungs-GmbH Glockengießerwall 1 D-20095 Hamburg www.gdv-dl.de<http://www.gdv-dl.de> Niederlassungen: Wilhelmstraße 43 / 43 G 10117 Berlin Frankenstraße 18 20097 Hamburg Sitz und Registergericht: Hamburg HRB 145291 USt.-IdNr : DE 205183123 Geschäftsführer: Dr. Jens Bartenwerfer Fred di Giuseppe Chiachiarella Aufsichtsratsvorsitzender: Werner Schmidt ------------------------------------------------------------------ Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe der E-Mail ist nicht gestattet. This e-mail and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

1 0

Sieve-scripts won't replicate
by Niels Kobschätzki 18 Jun '20

18 Jun '20

Hi, I am trying to use dovecot replication for a two-way sync. And whatever I do, sieve-scripts won’t replicate. Mails replicate near instantaneous. When I disable the sieve-script in roundcube, the other server will create in the home of the user on the other side a folder sieve/tmp but enabling won’t create the roundcube.sieve and the symlink .dovecot.sieve -> sieve/roundcube.sieve The home of a virtual mail user on server1 looks like this: drwx------ 4 vexim vexim 4096 Jun 18 08:02 . drwx------ 8 vexim vexim 4096 Jun 18 07:59 .. lrwxrwxrwx 1 vexim vexim 21 Jun 18 07:59 .dovecot.sieve -> sieve/roundcube.sieve drwx------ 5 vexim vexim 4096 Jun 18 08:14 Maildir drwx------ 3 vexim vexim 4096 Jun 18 08:02 sieve A ps auxwww|grep dove looks like this (maybe some user is wrong?): ps auxwww |grep dove root 847 0.0 0.0 4200 3044 ? Ss 07:54 0:00 /usr/sbin/dovecot -F root 849 0.0 0.0 4060 2544 ? S 07:54 0:00 dovecot-team1/replicator dovecot 850 0.0 0.0 3912 1092 ? S 07:54 0:00 dovecot-team1/anvil root 851 0.0 0.0 4048 2464 ? S 07:54 0:00 dovecot-team1/log dovecot 852 0.0 0.0 4048 2692 ? S 07:54 0:00 dovecot-team1/stats root 853 0.0 0.0 6072 4368 ? S 07:54 0:00 dovecot-team1/config dovecot 855 0.0 0.0 17412 6620 ? S 07:54 0:00 dovecot-team1/auth dovenull 856 0.0 0.0 8200 6344 ? S 07:54 0:00 dovecot-team1/imap-login vexim 858 0.0 0.0 7092 5300 ? S 07:54 0:00 dovecot-team1/imap dovecot 902 0.0 0.0 3912 1096 ? S 07:55 0:00 dovecot-team1/aggregator dovenull 1929 0.0 0.0 8200 6256 ? S 08:15 0:00 dovecot-team1/imap-login vexim 1930 0.0 0.0 6984 5284 ? S 08:15 0:00 dovecot-team1/imap dovenull 1931 0.0 0.0 8200 6248 ? S 08:15 0:00 dovecot-team1/imap-login vexim 1932 0.0 0.0 6964 5140 ? S 08:15 0:00 dovecot-team1/imap root 2210 0.0 0.0 6048 892 pts/0 S+ 08:21 0:00 grep dove I do not see any errors in the log. Here is the doveconf -n output. The partner looks identical except the replication target. # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 # Hostname: team.snafu.de auth_mechanisms = plain login auth_verbose = yes doveadm_password = # hidden, use -P to show it doveadm_port = 12345 instance_name = team1 mail_location = maildir:~/mail:INBOX=/var/vmail/%d/%u mail_plugins = " notify replication" 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 index ihave duplicate mime foreverypart extracttext spamtest spamtestplus virustest editheader servermetadata imapflags notify imapsieve vnd.dovecot.imapsieve 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 = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * mail_replica = tcps:server2.domain.de:12345 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags +editheader +regex +spamtest +spamtestplus +virustest +servermetadata sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = " imap lmtp sieve sieve" replication_dsync_parameters = -D -d -N -l 30 -U service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vexim } unix_listener replication-notify { mode = 0666 user = vexim } } service auth { unix_listener auth-client { group = vexim mode = 0660 user = Debian-exim } unix_listener auth-userdb { group = vexim mode = 0666 user = vexim } } service config { unix_listener config { user = vexim } } service doveadm { inet_listener { port = 12345 ssl = yes } user = vexim } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </etc/ssl/certs/wildcard.domain.de.pem ssl_cipher_list = HIGH:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " notify replication sieve" } protocol imap { mail_plugins = " notify replication imap_sieve" } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log mail_plugins = " notify replication sieve" } protocol sieve { mail_max_userip_connections = 10 managesieve_max_line_length = 65536 } Any help appreciated. Niels

1 1

Password mismatch after upgrade to Ubuntu Focal
by Jeffrey van Doesburg 16 Jun '20

16 Jun '20

Hi! Today I upgraded one of our Dovecot servers from Ubuntu 18.04 to Ubuntu 20.04. After the upgrade I have login issues because the password didn't match. I also installed Dovecot on a clean Ubuntu 20.04 server with the same configuration files. And here I also got the password match issue. We're using LDAP for managing the login credentials and I'm 100% sure the password is correct. With the debug options on, you will see something like this: CRYPT(<PLAIN_TEXT_PASSWORD>) != '$6$<SECRET_PASSWORD_HASH>' Does somebody know if there are know issues with Dovecot 2.3.7.2- 1ubuntu3.1 on Ubuntu 20.04 and with the LDAP driver? dovecot -n ------------------------- # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-33-generic x86_64 Ubuntu 20.04 LTS ceph # Hostname: server.example.tld auth_verbose = yes disable_plaintext_auth = no listen = *, [::] log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = POP/IMAP Service ready. mail_fsync = always mail_location = maildir:/mail/%u mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { acl = vfile:/etc/dovecot/acls/:cache_secs=30 autosubscribe = Trash autosubscribe2 = Sent autosubscribe3 = Drafts } protocols = imap pop3 service auth { user = root } service imap-create-folder { executable = script-login /usr/local/sbin/dovecot-create-dirs.sh } service imap-login { process_min_avail = 15 service_count = 0 } service imap { executable = imap imap-create-folder } service pop3-login { process_min_avail = 15 service_count = 0 } service pop3 { drop_priv_before_exec = yes } ssl = no userdb { driver = prefetch } protocol imap { mail_max_userip_connections = 25 mail_plugins = acl } protocol pop3 { pop3_uidl_format = %f } ------------------------------ /etc/dovecot/dovecot-ldap.conf ------------------------------ hosts = ldap.server.example.tld dn = <XXXXX> dnpass = <XXXXX> auth_bind = no ldap_version = 3 base = <XXXXX> pass_attrs = <XXXXX> pass_filter = <XXXXX> ----------------- Thanks! Jeffrey

2 5

Send SPF SoftFails to Junk
by Scott A. Wozny 14 Jun '20

14 Jun '20

Hello Dovecot gurus, I've set up SPF checking on my postfix gateway and have confirmed that messages from domains set with hard fails that don't come from a good sender are rejected outright. Messages from domains set with a softfail that come from bad sources are tagged in the message header with "Softfail (domain owner discourages use of this host)", but end up in the user's Inbox, anyway. I suppose I kind of figured DoceCot would see the SPF softfail in the message header and automagically route that message to Junk, but it didn't. I've looked around Google and the Dovecot documentation to see if there are any instructions on how to do this, but I can't find anything. Is there an easy way to do this or do I need something more advanced in the way of a spam filtering system? OR is doing this my mail client's responsibility and I need to look around my Thunderbird settings? I suppose it's also possible that Postfix needed to do something beyond adding the Received-SPF line in the message header, but I didn't see anything about that in the Policy-SPF config. This is my first foray into SPF so I'm open to any suggestions. Thanks, Scott

2 2

Login auth strip domain from username
by David Pottage 14 Jun '20

14 Jun '20

Hi, I have just discovered that the IMAP account setup wizard in outlook 2019 assumes that the email address for a user is the same as their username, and there is no easy way to separately enter different user. (It can be done via hidden dialog boxes, command line switches and registry hacking, but it is far from easy [1]) Like many small setups, the dovecot accounts on my mail server map directly to unix accounts on the machine, and the IMAP password for each account is the same as the unix login password. I have now got outlook sorted and talking to my IMAP server, but seeing as this issue will almost certainly arise again, with out over-simplified MUA software, is there a setting in dovecot that if it is given an email address as a login username it strips off the domain part, and tests the user part against the password supplied? If you know how to do that for postfix for sending email, then even better! [1] https://superuser.com/questions/1391960/how-to-enter-username-of-imap-accou… -- David Pottage

4 3

handling spam from gmail.
by Marc Roos 12 Jun '20

12 Jun '20

I am sick of this gmail spam. Does anyone know a solution where I can do something like this: 1. received email from adcpni444(a)gmail.com 2. system recognizes this email address has been 'whitelisted', continue with 7. 3. system recognizes as this email never been seen before 4. auto reply with something like (maybe with a wait time of x hours): Your message did not receive the final recipient. You are sending from a known spam provider network that is why we blocked your message. Please confirm that: - you are not a spammer and - you have permission to use the mail adress you send your message to - you and your provider agree to uphold GDPR legislation - you and your provider are liable for damages when breaching any of the above. Click link to confirm and you agree with the above https://www.domainwithoutletsencryptcertificate.com/asdfasdfadsfaf 5. sender clicks confirm url 6. email address is added to some white list. 7. email is delivered to recipient.

16 27

Read-flag of mails don't update
by Marius Rasch 12 Jun '20

12 Jun '20

Hi, since one or two month I have a problem with Dovecot not updating the read-flag on mails using IMAP. I receive new mails, but when reading, they still unread on other devices (but shown as read on the first device). When I remember correct, this problem doesn't come with an update of dovecot, but just occured at some time. But I've updated dovecot since then a few times. Whenever a client connects to dovecot I get an panic in the log. I therefore added a log file and my dovecot configuration (is this fine or does it need to be in the mail body?). There are system information in the output of dovecot -n; the filesystem dovecot is running on is ext4. I hope I provided all information needed and seeing forward to get a hint what the problem might be. Marius

3 7

executing script on mail arrival from sieve
by Voytek Eymont 12 Jun '20

12 Jun '20

I currently have a basic script to process some mails, it runs from cron every 10 minutes, basically, sieve copies some mails to subfolder on mail arrival, script fetches mails if any from this subfolder then processes these mail, get maybe 1 or 2 or often none but cron runs the script every 10 minutes, most times not needed as nothing is retrieved it's pretty crude - but works getmail fetches mails to local folder, deletes in subfolder munpack mailfile to unMIME links dumps HTML to txt looking at wiki2, 'Pigeonhole Sieve Extprograms Plugin', is this what would allow to execute my script on new mail arrival? I can't quite figure out how to.. if anyone has any sample, I might try to adapt to my need.. thanks (probably I should just leave like it is till I understand the docs...) thanks, V

2 2

Doveadm Backup (other) issues
by Gingko 11 Jun '20

11 Jun '20

Hello, I also have issues using Dovecot Backup. I am trying to Backup (or possibly Sync - one way) a single user IMAP account from a remote server, unknown type, to my own server. For that purpose, I defined the following parameters : imapc_host = <host name> imapc_user = <user name> imapc_password = <password> imapc_features = rfc822.size (<user name> has format: name(a)example.com, and <host name> is the name of the imap remote server that I use for getting mails) … and then I issued the following command: doveadm backup -R -u <user name, format name(a)example.com> imapc: ... but doing this, I get the following answer: dsync(<user name>): Info: imapc(<host name>:143): Connected to <host IP address>:143 (local 192.168.1.2:52940) dsync(<user name>): Error: Failed to initialize user: namespace configuration error: Namespace mail/ can't have alias_for= to a different storage (different root dirs) How can I solve this? If there is something not matching between servers, I may eventually change configuration on my side, but I think I would first have to know which feature(s) I have to know from the remote server in order to create the matching one on my server. Is there a way to list all relevant data coming from the remote server? Also: Doing this, is it necessary that the source user name be the same as the destination user name? Is it possible to backup an IMAP account to a user account having a completely different name? Regards, Gingko

5 7

Dovecot /VMWare Boxer
by Djule Djukic 11 Jun '20

11 Jun '20

Hello all, My name is Djule Djukic and I am working for Hipotekarna Banka from Montenegro. We are using IMAP email server Dovecot version 2.1.17. As a email clients on our corporate workstations we are using Thunderbird or WebMail and everything is working fine. We decided to introduce MDM solution in our environment and we installed VMWare WorkspaceOne (former Airwatch) which use Boxer as a mail client in App per VPN scenario. When we syncronise email with Boxer we have found that the time and date displayed for some messages have been changed to the time at which the file was synchronized. This is not hapening with all messages. It is happening only with messages in subfolders, never with Inbox. It seems when messages is moved by some rule from WebMail or Thunderbird from Inbox to some subfolder, Boxer is not able to read dates correctly, By seraching on Internet we found couple of explanation what might be possibel cause of this behaviour. https://imapsync.lamiral.info/FAQ.d/FAQ.Dates.txt https://serverfault.com/questions/588618/maintain-email-timestamp-when-tran… https://dovecot.org/pipermail/dovecot/2008-July/032165.html Problem with some email clients is that they not look always for "Date:" from email message header. The "Date:" header is usually the date the message was written or sent the first time, at the writer side. This "Date:" header line is never changed by any transfer or copy. If an email client uses the "Date:" header for displaying the date of a message then no problem in synchronization with wrong date should arise. Obviously this is not a case with a Boxer email application. We tried GMail and everything is working fine. We are wondering if someone can explain what APPEND command could have done in our case? Is it relevant at all for our case? Is it used somehow by thunderbird or webmail clients? Also we would like to hear from someone if there are some improvemnents in further release of dovecot or some configuration that we can implement in order to fix this? Thank you in advanced for your suggestions and contribution, Đule Đukić Specijalista za informacionu bezbjednost / ISO ĐuleĐukić Specijalistaza informacionu bezbjednost / ISO http://www.hipotekarnabanka.com/hb-content/uploads/2014/06/slika1.jpg

3 3

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

Yes tell that to the people that create rhel6, rhel7 and rhel8 and give lts support. Unless google pays you to train your software to mark their messages as spam, you might want to consider yourself not to smart as well ;) My solution would solve the problem others create (see the other mail). Your solution wastes your time and will always be carrying water to the sea. I think if 50% of providers in the world would do this, it would quickly be end of story for the spam originating from the networks like google and amazon. If there is a McDonalds build next to your home, and their clients throw waste into your garden. You hold McDonalds liable for cleaning this up not? Or are you also going to cleanup their mess indefinitely. -----Original Message----- From: Reindl Harald [mailto:h.reindl@thelounge.net] Sent: donderdag 11 juni 2020 11:09 To: Marc Roos; dominic; dovecot; lists; users Subject: Re: handling spam from gmail. Am 11.06.20 um 11:04 schrieb Marc Roos: > I have got lots of shit coming from *.google.com like these: > > X-Spam-Status: No, score=2.1 required=3.0 tests=BAYES_00 because you are too dumb to train your bayes give me one such message and i am pretty sure it will fire BAYES_80 or BAYES_99 which will burn it with fire and lead to a milter reject here SpamAssassin 3.3.1 is also not very smart in 2020 so instead ask for dumb solutions which making you part of a bigger problem better do your homework

2 1

Pigeonhole-sieve auto-reply
by ＠lbutlr 11 Jun '20

11 Jun '20

Is it possible to have a sieve script reply with a press message to certain emails (and only certain emails) based on sieve matches? I see a lot on vacation replies, but I want something more specific. Something along the lines of procmails formail command? Everything I’ve searched for is about vacation r filing replies into the same folder as the original message.

2 2

Special use folders in mailbox hierarchy
by Scott A. Wozny 11 Jun '20

11 Jun '20

Dear Dovecot Gurus, Setting up my first IMAP server and looking at the folder structure, I had a mailbox I built on a Dovecot server and a mailbox configured by a hosting provider next to each other in Thunderbird and I noticed that the special use folders (Drafts, Trash and Sent) in my default-ish (I did set them to auto = subscribe) Dovecot install make these folders appear parallel to my Inbox folder where my hosting provider’s default configuration has them under the Inbox hierarchically, along with all the folders I built for mail storage over the use of the account. I did some googling, but I cannot find any guidance on which of these is preferred, why, or how they could be controlled in Dovecot. The default Dovecot config is ambiguous (IMHO) in that the mailbox config elements are children to the inbox namespace (implying they go under Inbox in the hierarchy) but their special_use parameter names are \Name which (if you use a UNIX filesystem paradigm) implies they should be at the root of the hierarchy and, therefore, parallel with Inbox, which is how Thunderbird shows them, but I’m not sure if that’s a mail client decision and not anything to do with the server configuration. Since I can’t access the config of my hosting provider, I can’t make any comparisons, so I thought I’d ask on the list if there is any standard guidance on server side configuration of special use folders in Dovecot or if there’s no guidance available because I’m overthinking this. :) Thanks, Scott

3 3

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

>> Yes tell that to the people that create rhel6, rhel7 and rhel8 and give >> lts support. > >as said that has nothing to do with your wrong training and RHEL has >always the same problem: you can't package the latest and greatest shit >over 10 years because it requrires newer versions of dependencies > >so what you get with your lazyness by using a LTS distribution is a >"never change a running system, just fix the worst bugs and don't touch >anything else" > >upstream developers don't hold development for 10 years > >written from a Fedora workstation with kernel 5.6.18-200.fc31.x86_64 >from last night realyed over a datacenter firewall and a mailserver >using the same kernel > >> Unless google pays you to train your software to mark their messages as >> spam, you might want to consider yourself not to smart as well ;) > >unless i make good money from customers paying for a nearly 100% >hitrate of spam combine with a zero-false-positive policy i am likely >smarter than you I would argue it is quite difficult to identify intelligence. I am pretty sure I would not start with your reasoning. I have a favourite German saying I like to quote in matters like these "gegen Dummheit kämpfen Götter selbst vergebens" >> My solution would solve the problem others create (see the other mail). >> Your solution wastes your time and will always be carrying water to the >> sea. I think if 50% of providers in the world would do this, it would >> quickly be end of story for the spam originating from the networks like >> google and amazon. > >they won't give a shit and when i get such idiotic mails as you propose >i take the phone, call the sender and suggest to fire his mailadmin >better sooner than later > >> If there is a McDonalds build next to your home, and their clients throw >> waste into your garden. You hold McDonalds liable for cleaning this up >> not? Or are you also going to cleanup their mess indefinitely. > >what a nonsense

1 0

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

Your logics sucks. There is a difference between how email works and how spamassassin works. You are assuming that everyone in the world is using spamassassin by including it in 'how email works'. Maybe you like to post a link to your bayes files???? Am 11.06.20 um 11:13 schrieb Marc Roos: > You do not understand how mail works. Google mail is only getting > through when spf checks and the likes are being passed. unless you don't manage to get rid of BAYES_00 in case of clear spam messages don't tell me you understand how email works

1 0

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

You do not understand how mail works. Google mail is only getting through when spf checks and the likes are being passed. I am not creating any problems with this, I am just bouncing them back. Google has enough billions to handle these issues. If everyone would apply this procedures, people with legitimate email accounts would move from a spam network to some other provider. People joining these providers are the problem, because it allows these networks to mix spam with legitimate email. When clients start moving out, spam networks are becoming easier to hard block and these providers start thinking about their infrastructure and their bussines model. If everyone would be doing this, it is solving the spam problem. My below procedure should be applicable for any network generating a lot of spam. -----Original Message----- From: Reindl Harald [mailto:h.reindl@thelounge.net] Sent: donderdag 11 juni 2020 10:25 To: Marc Roos; dovecot; users Subject: Re: handling spam from gmail. Am 11.06.20 um 10:19 schrieb Marc Roos: > I am sick of this gmail spam. Does anyone know a solution where I can > do something like this: > > 1. received email from adcpni444(a)gmail.com 2. system recognizes this > email address has been 'whitelisted', continue with 7. > 3. system recognizes as this email never been seen before 4. auto > reply with something like (maybe with a wait time of x hours): > Your message did not receive the final recipient. You are sending > from a known spam provider > network that is why we blocked your message. Please confirm that: > - you are not a spammer and > - you have permission to use the mail adress you send your message to > - you and your provider agree to uphold GDPR legislation > - you and your provider are liable for damages when breaching any > of the above. > > > Click link to confirm and you agree with the above > https://www.domainwithoutletsencryptcertificate.com/asdfasdfadsfaf > > 5. sender clicks confirm url > 6. email address is added to some white list. > 7. email is delivered to recipient. and i am sick of people not understanding how email works! you don't send unasked mail to a in the most cases forged sender unless you want to be part of the problem backscatters and brainless autoreplies have to be burnt with fire

1 0

Dovecot fs quota reports quota as byte
by Kazim Koybasi 11 Jun '20

11 Jun '20

Hello, My dovecot configuration is like below. My filesystem quota is reported as kb and dovecot quota reported as bytes so dovecot quota becomes wrongly greater than filesystem quota. How can I solve this issue? Any help apretiated. Quota name Type Value Limit % user STORAGE 10428416 3242880 321 # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 4.18.0-147.8.1.el8_1.x86_64 x86_64 CentOS Linux release 8.1.1911 (Core) # Hostname: suretired auth_mechanisms = plain login auth_username_format = %Ln debug_log_path = /var/log/dovecot.log first_valid_uid = 1000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = * mail_debug = yes mail_location = maildir:~/Maildir:INDEX=/var/no-quotas/index/%u:CONTROL=/var/no-quotas/control/%u mail_plugins = quota 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 index ihave duplicate mime foreverypart extracttext spamtest spamtestplus mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { quota = fs:user sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/default.sieve sieve_extensions = +spamtest +spamtestplus sieve_spamtest_max_value = 15 sieve_spamtest_status_header = X-Spam-Score: (-?[[:digit:]]+\.[[:digit:]]).* sieve_spamtest_status_type = score } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = dovecot } } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 2424 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 1024 } service quota-warning { executable = script /usr/bin/quota-warning.sh unix_listener quota-warning { group = dovecot mode = 0600 user = dovecot } user = dovecot } ssl_cert = </etc/pki/dovecot/certs/letsencrypt/fullchain1.pem ssl_cipher_list = ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 !TLSv1 userdb { driver = passwd } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log log_path = /var/log/dovecot-lmtp-errors.log mail_plugins = quota sieve quota } protocol lda { mail_plugins = quota sieve quota } protocol imap { mail_plugins = quota quota imap_quota } protocol sieve { info_log_path = /var/log/dovecot-sieve.log log_path = /var/log/dovecot-sieve-errors.log managesieve_max_line_length = 65536 } protocol pop3 { mail_plugins = quota pop3_quota quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv }

1 0

How to unset namespace configuration from dovecot.conf in conf.d/99-cutom.conf?
by Py Retta 09 Jun '20

09 Jun '20

Dear all, my /etc/dovecot/dovecot.conf [0] that is shipped with the Linux distro (Ubuntu 18.04, dovecot 2.3.10) has a namespace section: namespace inbox { ... mailbox Sent { ... } ... } I need to remove this whole section from the configuration, but I need to do this in a file such as /etc/dovecot/conf.d/99-custom.conf because I want this modification to be stable against automatic updates of dovecot.conf shipped by the distro. This raises the question, how do I "unset" an earlier namespace configuration at a later point in the stack of config files? Speaking in terms of `doveconf -n`, snippet [1] below lists the original configuration (including namespace setup) and [2] lists the desired configuration that results from deleting the namespace passage from dovecot.conf. However, I would like to achieve it without deleting it from dovecot.conf but by adding sth to conf.d/99-custom.conf. Thanks a lot, Py [0] original dovecot.conf (only relevant namespace section): # Default private namespace setup compatible with Courier-IMAP. namespace inbox { separator = . prefix = INBOX. inbox = yes mailbox Sent { auto = subscribe # autocreate and autosubscribe the Sent mailbox special_use = \Sent } mailbox Spam { auto = create # autocreate Spam, but don't autosubscribe special_use = \Junk } mailbox Drafts { auto = create special_use = \Drafts } mailbox Trash { auto = create special_use = \Trash } } [1] `doveconf -n` for the original configuration: # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2248) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (2251) # OS: Linux 4.15.0 x86_64 Ubuntu 18.04.4 LTS ext4 # Hostname: ############ auth_mechanisms = ####################### auth_username_chars = ################ disable_plaintext_auth = #### first_valid_uid = #### imap_client_workarounds = delay-newmail imap_logout_format = rcvd=%i, sent=%o mail_home = ################## mail_location = ##################### mail_log_prefix = "service=%s, user=%u, ip=[%r]. " mail_plugins = " quota" managesieve_logout_format = rcvd=%i, sent=%o 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 index ihave duplicate mime foreverypart extracttext imapflags notify namespace inbox { inbox = yes location = mailbox Drafts { auto = create special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = create special_use = \Trash } prefix = INBOX. separator = . } passdb { driver = plesk } plugin { quota = maildir:User quota quota_grace = 0 quota_warning = storage=95%% quota-warning %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = rcvd=%i, sent=%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s protocols = imap pop3 sieve service auth-worker { group = user = } service auth { group = unix_listener auth-userdb { group = popuser mode = 0600 user = popuser } user = } service imap-login { process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 service_count = 1 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 service_count = 1 } service quota-warning { executable = ################ unix_listener quota-warning { user = popuser } user = popuser } service stats { unix_listener stats-writer { user = popuser } } ssl_cert = ################ ssl_cipher_list = ############# ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" } [2] `doveconf -n` for the desired configuration (with the namespace section in dovecot.conf removed): # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2248) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (2251) # OS: Linux 4.15.0 x86_64 Ubuntu 18.04.4 LTS ext4 # Hostname: ############ auth_mechanisms = ####################### auth_username_chars = ################ disable_plaintext_auth = #### first_valid_uid = #### imap_client_workarounds = delay-newmail imap_logout_format = rcvd=%i, sent=%o mail_home = ################## mail_location = ##################### mail_log_prefix = "service=%s, user=%u, ip=[%r]. " mail_plugins = " quota" managesieve_logout_format = rcvd=%i, sent=%o 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 index ihave duplicate mime foreverypart extracttext imapflags notify passdb { driver = plesk } plugin { quota = maildir:User quota quota_grace = 0 quota_warning = storage=95%% quota-warning %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = rcvd=%i, sent=%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s protocols = imap pop3 sieve service auth-worker { group = user = } service auth { group = unix_listener auth-userdb { group = popuser mode = 0600 user = popuser } user = } service imap-login { process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 service_count = 1 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 service_count = 1 } service quota-warning { executable = ################ unix_listener quota-warning { user = popuser } user = popuser } service stats { unix_listener stats-writer { user = popuser } } ssl_cert = ################ ssl_cipher_list = ############# ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" }

1 0

doveadm protocol bug
by Felipe Gasper 08 Jun '20

08 Jun '20

Hi everyone, On 26th May I emailed this list a few times about an apparent protocol bug in Dovecot’s server-side doveadm implementation. Later that day I sent in a pull request to fix the issue. Thread reference: https://dovecot.org/pipermail/dovecot/2020-May/119066.html Pull request: https://github.com/dovecot/core/pull/129 Thus far neither the mailing list emails nor the PR have garnered any responses. Can someone please weigh in on these? It’s totally understandable if Dovecot’s behavior here is going to say as-is; I’d just like some confirmation so we can note it in our client implementation. (Switching our client to the HTTP API would be out-of-scope for our current project.) Thank you again! cheers, -Felipe Gasper

1 0

Can't share a mailbox
by Maxime DERCHE 08 Jun '20

08 Jun '20

Hello, I have a "notifs@" generic mail account, intended to receive technical monitoring messages. I need to share it with the people of the analyst team. I created a shared namespace, and enabled the modules. doveadm acl creates the dovecot-acl file but not the acl_shared_dict file. I guess something prevents it from doing it, but I fail to see what. It is a LDAP setup, and there is only one vmail (uid/gid 500) UNIX account to read and write the files on the file system. $ > doveadm acl add -u notifs(a)test.example.tld "shared/notifs(a)test.example.tld/INBOX" user=maxime.derche(a)test.example.tld :lrw $ > doveadm acl debug -u maxime.derche(a)test.example.tld "shared/notifs(a)test.example.tld/INBOX" doveadm(maxime.derche(a)test.example.tld): Info: Mailbox 'INBOX' is in namespace 'shared/notifs(a)test.example.tld/' doveadm(maxime.derche(a)test.example.tld): Info: Mailbox path: /var/vmail/test.example.tld/notifs/mail doveadm(maxime.derche(a)test.example.tld): Info: Per-user private flags in mailbox: \Seen doveadm(maxime.derche(a)test.example.tld): Info: User maxime.derche(a)test.example.tld has rights: lrw doveadm(maxime.derche(a)test.example.tld): Error: User maxime.derche(a)test.example.tld is missing 'lookup' right doveadm(maxime.derche(a)test.example.tld): Info: Mailbox shared/notifs(a)test.example.tld/INBOX is NOT visible in LIST /var/vmail/test.example.tld/notifs/mail/dovecot-acl: ---------------------------------------- user=maxime.derche(a)test.example.tld :lrw ---------------------------------------- dovecot -n ---------------------------------------- # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 # Hostname: server.example.tld auth_debug = yes auth_mechanisms = plain login auth_verbose = yes lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_access_groups = vmail mail_debug = yes mail_gid = 5000 mail_location = maildir:~/Maildir mail_plugins = quota acl mail_privileged_group = mail mail_server_admin = mailto:postmaster@test.example.tld mail_shared_explicit_inbox = yes mail_uid = 5000 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 index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace { list = children location = maildir:%%h/mail:INDEXPVT=~/mail/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/vmail/shared-mailboxes imapsieve_mailbox1_before = file:/etc/dovecot/sieve/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/etc/dovecot/sieve/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * recipient_delimiter = + sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after sieve_before = /etc/dovecot/sieve-before sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /etc/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = " imap lmtp sieve" service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/ssl/certs/cert.pem ssl_cipher_list = HIGH:!ADH:!AECDH:!PSK:!KRB5:!RC4:!DES:!3DES:!MD5 ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap override_fields = home=/var/vmail/%d/%n } protocol lmtp { mail_plugins = quota acl sieve userdb { args = allow_all_users=yes uid=vmail gid=vmail home=/var/vmail/%d/%n mail=maildir:~/mail driver = static name = } } protocol imap { mail_plugins = quota acl imap_sieve imap_acl } ---------------------------------------- Does anyone see what I'm doing wrong here? Kind regards, -- Maxime DERCHE Information System Consulting France | NVMQVAM SOLVS https://www.mdisc.fr/ OpenPGP Key ID: 0x814E02A25697FD13 OpenPGP Key Fingerprint: 8B7B 60C9 1095 A198 C883 5205 814E 02A2 5697 FD13

1 0

Doveadm Backup issues
by Francis Augusto Medeiros-Logeay 07 Jun '20

07 Jun '20

Hi, I'm trying to use doveadm backup but I'm having a few issues. When trying locally: `doveadm backup -D -A maildir:/usr/local/backup` It results that no mailbox is separated by user - all seems to sync on the same folder, messing up with the folder structure of the original maildir. When trying remotely: `doveadm backup -D -A -N ssh -i mykey root@myremotebackup.com:/backup doveadmin dsync-server -A` I get this error line for each user: dsync-local(theuser(a)thedomain.com)<5DNrEXdG1l5tAgAAqsACHw>: Error: read(remote) failed: EOF (version not received) doveadm(theuser(a)thedomain.com): Fatal: execvp(ssh) failed: No such file or directory I'd be very thankful if someone could help me with this. Best, Francis -- Francis Augusto Medeiros-Logeay Oslo, Norway

3 5

Deliver administrative message ignoring user quota
by Peter Folta 07 Jun '20

07 Jun '20

Hi everyone, I have a separate internal system running on a different host that needs to put an administrative email into a user’s inbox. I’ve been playing around with the “doveadm mailbox save” command via Doveadm’s HTTP API (https://doc.dovecot.org/admin_manual/doveadm_http_api/#doveadm-mailbox-save <https://doc.dovecot.org/admin_manual/doveadm_http_api/#doveadm-mailbox-save>). This works quite well provided the user is within quota limit, however, I would like to be able to deliver these messages even if the email account is over quota. I noticed that it’s possible to override the quota configuration using dovecot-lda by overriding plugin/quota with the “noenforcing” directive as explained in https://wiki.dovecot.org/Quota/Configuration <https://wiki.dovecot.org/Quota/Configuration>. I don’t currently use LDA, SMTP servers based on Postfix deliver mail via LMTP and I need to be able to deliver this message from a different host in the network. The HTTP API doesn’t seem to support overriding the quota config. What would be the best way to go about this? Thanks Peter

2 2

(no subject)
by Stephen Blackwell 07 Jun '20

07 Jun '20

I want to disable the time penalty for dovecot imap authentication. When receiving a valid user-password combo the server responds in .04 seconds. When I send in an invalid comination it will either respond in 1.544 or 2.044 seconds += .002 I am using dovecot to test a program that sends a login request to a server and processes the response. I want to be able to send a series of valid and invalid login attempts. The issue is that with the 2 seconds delay for a bad login attempt, the tests are too slow to run in production I can see that the delay is defined in auth-penalty.h Is there a way, in the config file, to set AUTH_PENALTY_INIT_SECS = 0, or any other way to remove the time delay for an invalid login. I am running dovecot version 2.2.33.2 I am running without root permissions I do not want to make changes outside of the dovecot config file, password file, or run folder. -- Stephen

3 2

Cannot log in to IMAP server and logs are unclear as to why
by Scott A. Wozny 07 Jun '20

07 Jun '20

I’m trying a super basic config based upon https://wiki.dovecot.org/HowTo/PostfixDovecotLMTP but before I work on shipping mail through Postfix to DoveCot, I wanted to make sure IMAP is working first, but I can’t even get a basic login to so I thought I’d see if the gurus on the list might be able to point out I’m doing wrong. The documentation is pretty good, but there were some gaps I had to guess at and I’m presuming that’s where I went wrong. I’ve turned SELinux to permissive mode, for now. Here’s the doveconf -n: # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1062.12.1.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) # Hostname: imap first_valid_uid = 1000 listen = 192.168.1.207 mail_gid = vmail mail_home = /var/vmail/%d/%n mail_location = sdbox:~/mail mail_uid = vmail mbox_write_locks = fcntl 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 = separator = / } passdb { args = scheme=PLAIN username_format=%u /etc/dovecot/users driver = passwd-file } protocols = imap lmtp service lmtp { group = vmail unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } I wasn’t sure how to set rights on the users file: [sawozny@imap var]$ cat /etc/dovecot/users test@test.com:{plain}test [sawozny@imap var]$ ls -la /etc/dovecot/users -rw-r--r--. 1 root root 26 Jun 3 23:31 /etc/dovecot/users Also, didn’t know what rights to set on the /var/vmail directoy so I did this: drwxrwx---. 3 vmail vmail 4096 Jun 3 20:52 vmail This directory is also empty except for the lost+fond directory that comes with a disk mount point. My understanding is that the mail home and maildir will manifest automagically on first login, but if I need to prime the pump, please let me know what I need to do. For my test, I did: [sawozny@imap var]$ telnet 192.168.1.207 143 Trying 192.168.1.207... Connected to 192.168.1.207. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. 01 LOGIN test(a)test.com test 01 NO [UNAVAILABLE] Internal error occurred. Refer to server log for more information. Connection closed by foreign host. And the results in the /var/log/maillog file are: Jun 3 23:35:34 imap dovecot: auth: Error: passwd-file /etc/dovecot/users: User test(a)test.com is missing userdb info Jun 3 23:35:44 imap dovecot: auth: Error: passwd-file(test(a)test.com,192.168.1.207,<DBqafDan7ODAqAHP>): user not found from userdb Jun 3 23:35:44 imap dovecot: imap: Error: Authenticated user not found from userdb, auth lookup id=843055105 (auth connected 0 msecs ago, handshake 0 msecs ago, request took 0 msecs, client-pid=12047 client-id=1) Jun 3 23:35:44 imap dovecot: imap-login: Internal login failure (pid=12047 id=1) (internal failure, 1 successful auths): user=<test(a)test.com>, method=PLAIN, rip=192.168.1.207, lip=192.168.1.207, mpid=12049, secured, session=<DBqafDan7ODAqAHP> I’m not sure where I’ve gone wrong. From my understanding of the documentation, all I need in the userdb is name and password. UID, GID and HOME are also indicated as required, but I set them at the system level, so why is the system telling me the user was not found? This definitely isn’t my first rodeo with Linux, but I know almost nothing about messaging so in that regard I’m a totally n00b and would really appreciate some guidance. Thanks, Scott

3 5

Only show mails within 30 days or 60 days?
by hfh＠cndns.com 05 Jun '20

05 Jun '20

How to display emails within 30 days or 60 days in inbox, sent box, etc. For example, in the mail client tool, the user clicks the inbox button and only sees the mail within 30 days. The virtual mailbox plugin will only generate a new mailbox. Thank you！！！

4 3

manual mdbox lock
by rudolf＠padaru.de 05 Jun '20

05 Jun '20

Good Morning, i have a question about the mdbox dotlock technique. We create a new backup strategy for our mailservers because we want to switch the mailformat from mbox to mdbox. Our recent backup plan works mainly with rsync and the inbuild tar function. We want to hande the backups with mdbox similar. Is there a way, how i can write-lock a mail user via the doveadm command or with dotlock files? I have searched the doveadm-sync code but i cant make out the point where the command lock the mailbox for write access. We work with Ubuntu 18, dovecot 2.33.2 Mit freundlichen Grüßen Yours sincerely <https://padaru.de/> Pascal Rudolf | Geschäftsführer PADARU-IT | Bielebohstraße 10 | 02736 Beiersdorf @: rudolf(a)padaru.de | www: <http://padaru.de/> padaru.de mobil: +49 (0) 17 772 595 32

1 0

Mailbox & Server Down
by Andrea Miconi 04 Jun '20

04 Jun '20

My mailboxes are on a Dovecot (IMAP) server.On DNS there is an MX record pointing to the server.To read the mail I use Roundcube.If the server is down, I lose the new mail. I would like to do two things, alternatively. First option.1) I keeep the mail on the provider's server, restoring the original MX record.2) Dovecot does not receive the mail, but should go to download it.3) I can access the server with Roundcube to read the downloaded mail, but if the server is down I can always go to read the mail on the provider's server with its webmail Second optionI install a second mail server and the two have to replicate the mail.But I don't know how to do it, so I need a guide with instructions.Furthermore Roundcube would always access only one server and if this is down, how can I connect to the second one?This is a typical situation for webmail like Yahoo, Outlook or GMail, but I'm not Yahoo, Microsoft and Google ;) Thanks in advance for any advice.

5 7

Error deleting INBOX when doing an imap sync
by Des Magner 04 Jun '20

04 Jun '20

Hi I am trying to set up a new mail server with dovecot. I got it all installed and set up successfully but am running into problems trying to migrate from my current email server. I tried the following command: doveadm -Dv -o imapc_host=[current-imap-host] -o imapc_user=[current-user] -o imapc_password=[password] -o imapc_features=rfc822.size -o mail_fsync=never backup -R -u [user] imapc: It connects fine but eventually fails with the following errors: dsync([user]): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. dsync([user]): Debug: brain S: Remote mailbox tree: INBOX guid=[xxx] uid_validity=1591096439 uid_next=1 subs=no last_change=0 last_subs=0 dsync([user] Debug: imapc([current-imap-host]:143): Disconnected I am guessing the new INBOX is not compatible with the Inbox on my current mail server so it is trying to delete it. If so is there a way I can change my configuration to allow it to be deleted?

3 2

I can no longer use TLS for Windows7 and Outlook
by Mark Constable 03 Jun '20

03 Jun '20

I currently use Ubuntu 20.04 with Dovecot 2.3.7.2 and OpenSSL 1.1.1f. A few months ago there was an update to all these systems and since then I've had to talk W7 and old Mac clients through disabling ports 993/995 with TLS enabled back to ports 143/110 without SSL or they could not pick up email. Thunderbird users (ie; me) were unaffected. Could anyone share a set of port 993/995 SSL settings known to work with Windows7 and Outlook16 using "dovecot -n|grep ^ssl_" please ? Mine is currently... ssl_ca = </etc/ssl/certs/ca-certificates.crt ssl_cert = </etc/ssl/example.com/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_options = no_compression no_ticket ssl_prefer_server_ciphers = yes I have commented out ssl_cipher_list, ssl_min_protocol and others to get back to whatever the defaults are so I am not simply guessing what the optimal settings would be to cover Win7 and up. Yes I know Win7 is no longer supported but that does not help the 100s of older users I have that can't/won't upgrade their computers.

7 6

Packages for CentOS 8
by Peter 01 Jun '20

01 Jun '20

I've now successfully built Dovecot packages for CentOS 8 that do not have the quota support stripped out. I was able to do this because CentOS has now finally shipped the quota-devel package as well as the other -devel packages that were previously missing from CentOS 8. For those of you who are interested they are in the GhettoForge Testing repo for el8 at: http://mirror.ghettoforge.org/distributions/gf/el/8/testing/x86_64/ These are untested so let me know if anyone experiences any issues with them. Peter

3 6

locking question
by Tom Lieuallen 01 Jun '20

01 Jun '20

We're running dovecot 2.3.10 on two different servers (two different environments). Both very similarly configured (sendmail and procmail for mail delivery); same OS and patch levels. One environment has nearly 10,000 users and hasn't seen problems. The other environment has just a handful of users, but one user is very active with email and has a fairly complicated procmail configuration. I'm having ongoing mail file locking problems with that one user... Procmail says it's using dotlocking and fcntl: procmail v3.22 2001/09/10 Locking strategies: dotlocking, fcntl() I'm using defaults for dovecot: #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl I have seen this a number of times in dovecot's logs. This signifies a start of locking problems with a mailbox. Mailbox aa_checkme_second: fcntl() failed with mbox: No locks available Procmail's logs show this: procmail: Locking "mail/aa_checkme_second.lock" procmail: Assigning "LASTFOLDER=mail/aa_checkme_second" procmail: Opening "mail/aa_checkme_second" procmail: Acquiring kernel-lock procmail: Kernel-lock failed procmail: Unlocking "mail/aa_checkme_second.lock" These errors were not concurrent; dovecot's errors happened first. I've been suspicious that there was a locking conflict of some kind. My only remaining question on that front is about the read locks. Is it worth trying dotlock for it instead of fcntl? If that's not the problem, then could we be running into some system limitations or a bug in the kernel or mailbox storage? The server running dovecot is Centos 6.10. The mailbox storage is on Isilon OneFS 8.1.2.0. I should probably increase dovecot's logging to see if anything else jumps out at me. thank you for any suggestions. Tom Lieuallen Oregon State Univesity

1 0

Problems with userdb and mail deliveribility
by Chris Bennett 01 Jun '20

01 Jun '20

I briefly got some mails delivered, but not anymore. Attached are dovecot-info.log, dovecot-debug.log, dovecot.log, maillog, /etc/mail/passwd smtpd.conf, vaddr, vusers, vdomains Thanks for any help. Chris Bennett

3 4

auth_policy_server vs client_id and x-originating-ip
by Zdeněk Zámečník 01 Jun '20

01 Jun '20

I run into troubles when trying to set up auth_policy_server in Dovecot 2.3.10.1. It works almost as expected but I cannot get client ID in this process. By setting up "imap_id_log=*" I see in log that Dovecot gets details about mail client like name and version: May 31 14:20:58 mail dovecot: imap(xxx(a)example.xxx)<24796><ft7ytfCmjdZWMSZQ>: ID sent: name=Thunderbird, version=68.8.1 But the auth_policy_server is getting all details except this ID, it's empty: May 31 14:20:58 mail auth-policy[10357]: { May 31 14:20:58 mail auth-policy[10357]: device_id: '', May 31 14:20:58 mail auth-policy[10357]: login: 'xxx(a)example.xxx', May 31 14:20:58 mail auth-policy[10357]: protocol: 'imap', May 31 14:20:58 mail auth-policy[10357]: pwhash: '097a', May 31 14:20:58 mail auth-policy[10357]: remote: '1.2.3.4', May 31 14:20:58 mail auth-policy[10357]: tls: true May 31 14:20:58 mail auth-policy[10357]: } However in some cases I see that client_id is passed to auth_policy_server: May 31 14:27:41 mail auth-policy[10357]: { May 31 14:27:41 mail auth-policy[10357]: device_id: '"name" "Outlook-iOS-Android" "version" "2.0"', May 31 14:27:41 mail auth-policy[10357]: login: 'yyy(a)example.xxx', May 31 14:27:41 mail auth-policy[10357]: protocol: 'imap', May 31 14:27:41 mail auth-policy[10357]: pwhash: '0b63', May 31 14:27:41 mail auth-policy[10357]: remote: '3.4.5.6', May 31 14:27:41 mail auth-policy[10357]: tls: true May 31 14:27:41 mail auth-policy[10357]: } I think I am missing some important point. Maybe IMAP command ID and client_id are totally different. Can you please advise? Is it possible to pass details about mail client to auth_policy_server? Second question is: how I can get "x-originating-ip" from ID command to auth_policy_server? Below is my config file: # 2.3.10.1 (a3d0e1171): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (67bf5bd7) # OS: Linux 5.3.18-2-pve x86_64 Debian 10.4 # Hostname: mail.z-technics.com auth_cache_size = 2 M auth_cache_ttl = 5 mins auth_master_user_separator = * auth_mechanisms = plain login auth_policy_check_before_auth = no auth_policy_hash_nonce = # hidden, use -P to show it auth_policy_report_after_auth = no auth_policy_server_timeout_msecs = 1500 auth_policy_server_url = http://127.0.0.1:8090/ dict { acl = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no imap_client_workarounds = delay-newmail imap_hibernate_timeout = 5 secs imap_id_log = * imap_id_retain = yes login_trusted_networks = 127.0.0.1 mail_gid = 2000 mail_home = /var/vmail/%d/%n mail_location = mdbox:~/mdbox:ALT=/var/vmail-archive/%d/%n/mdbox mail_max_userip_connections = 60 mail_plugins = acl zlib fts quota mail_uid = 2000 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 index ihave duplicate mime foreverypart extracttext vacation-seconds editheader imapsieve vnd.dovecot.imapsieve mdbox_rotate_interval = 1 days mdbox_rotate_size = 16 M passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /etc/dovecot/masters.db driver = passwd-file master = yes pass = yes } plugin { acl = vfile acl_shared_dict = proxy::acl imapsieve_mailbox1_before = file:/var/vmail/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/var/vmail/sieve/report-spam.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = Junk imapsieve_mailbox4_before = file:/var/vmail/sieve/report-ham.sieve imapsieve_mailbox4_causes = COPY imapsieve_mailbox4_from = Junk imapsieve_mailbox4_name = * mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_new3 = Deleted Items mailbox_alias_old = Sent mailbox_alias_old2 = Sent mailbox_alias_old3 = Trash quota = dict:User quota::proxy::quota quota_grace = 10%% quota_rule2 = Trash:ignore quota_rule3 = Junk:ignore quota_warning = storage=80%% quota-warning 90 %u quota_warning2 = storage=85%% quota-warning 95 %u quota_warning3 = storage=95%% quota-warning 105 %u sieve = /var/vmail/%d/%n/sieve/.sieve sieve_after = /var/vmail/%d/%n/sieve/autoreply.sieve sieve_before = /var/vmail/sieve/global.sieve sieve_dir = /var/vmail/%d/%n/sieve sieve_extensions = +editheader +vacation-seconds sieve_global_dir = /var/vmail/sieve/ sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_max_redirects = 20 sieve_pipe_bin_dir = /usr/lib/dovecot sieve_plugins = sieve_imapsieve sieve_extprograms sieve_vacation_send_from_recipient = yes } protocols = imap sieve lmtp pop3 service auth-worker { unix_listener auth-worker { user = vmail } user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = vmail } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-hibernate { unix_listener imap-hibernate { group = $default_internal_group mode = 0660 } } service imap-login { process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service imap { executable = imap process_limit = 3500 unix_listener imap-master { user = $default_internal_user } vsz_limit = 2 G } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 400 } service pop3-login { process_min_avail = 3 service_count = 0 vsz_limit = 320 M } service pop3 { process_limit = 200 vsz_limit = 320 M } service quota-warning { executable = script /etc/dovecot/quota_warning.sh unix_listener quota-warning { mode = 0666 user = vmail } user = vmail } ssl_cert = </etc/ssl/private/multi.z-technics.cz.dovecot.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it stats_writer_socket_path = userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } protocol sieve { managesieve_implementation_string = Dovecot Pigeonhole managesieve_max_compile_errors = 5 } protocol imap { mail_plugins = quota imap_quota fts mailbox_alias imap_acl acl imap_zlib imap_sieve } protocol lda { mail_fsync = optimized } protocol lmtp { mail_fsync = optimized mail_plugins = quota sieve acl }

2 1

2.3.10 + lazy expunge
by Matt Bryant 01 Jun '20

01 Jun '20

Hi, so currently run dovecot 2.2.x on CentOS 7 box and was looking to upgrade to 2.3.10. I use lazy expunge atm into a different namespace but saw on the new doco pages that is is depracted in 2.3.0. Have tested and still seems to work so question is more around why ? Why would this be deprecated given using a different namespace allows 2 things a) the folder where message is located is taken accross so if I want to restore and know where it went b) namespace allows me to specify an alternate location for storing the messages. Also given it does still work is there any indication as to what version the deprecation basically equates to it not working. rgds Matt ------ 8< --------- namespace Deprecated since version v2.3.0.

1 0

identify 143 vs 993 clients
by mj 01 Jun '20

01 Jun '20

Hi, I am trying to find a nice way to identify dovecot clients that are still configured to use port 143 to connect to our mailserver, from the dovecot logs. I would then ask them to move over to 993, and finally disable port 143 altogether. When looking at the dovecot logs, it seems this is not logged in any obvious way. Of course I could use netflow etc, but that would not give us usernames, but IP's, etc. So, is there a nice way to somehow indicate in the dovecot logs, if a client connected on 143 or on 993? Thanks!

13 25

Running doveadm without config file?
by Joseph Tam 01 Jun '20

01 Jun '20

It would be useful to run the "doveadm" utility on a non-dovecot server e.g. generating password hashes: # echo plaintextpass | doveadm pw -s BLF-CRYPT doveadm(user): Fatal: Error reading configuration: stat(/etc/dovecot/dovecot.conf) failed: No such file or directory Is there a way to circumvent the need for a configuration file? Joseph Tam <jtam.home(a)gmail.com>

2 4

Current thinking on backups ?
by Laura Smith 30 May '20

30 May '20

Hi, What are people doing for backups ? My current process is LVM snapshot and backup from that to NFS share. But there seems to be hints around the internet that people use/abuse "doveadm backup" for backup purposes even though it seems its original intention was for transferring mailboxes between dovecot instances. Assuming its ok to "doveadm backup" to an NFS share, is it ok to use "doveadm backup" when dovecot has replication setup (replication-notify etc.) ? Or will it interfere ? Thanks! Laura

4 4

Operation not permitted - fchown() failed for /run/dovecot/login
by Dshah 30 May '20

30 May '20

# dovecot --version 2.3.10.1 (a3d0e1171) Dovecot is unable to start, I see error " Fatal: fchown() failed for /run/dovecot/login: Operation not permitted" what could be the problem? any help please $ls -la /var/mail/ drwxr-xr-x 1 root root 4096 May 29 17:32 . drwxr-xr-x 1 root root 4096 May 28 17:08 .. drw------- 2 root root 4096 May 29 17:32 domains ====# cat /etc/dovecot/dovecot.conf===== auth_mechanisms = plain login auth_username_format = %Lu auth_verbose = yes auth_debug = yes auth_debug_passwords = no log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = IMAP server ready disable_plaintext_auth = no protocols = imap pop3 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/mail/domains/%d/%n first_valid_gid = 105 first_valid_uid = 102 last_valid_gid = 105 last_valid_uid = 102 service anvil { client_limit = 2100 } ssl_cert = </secret/tls.crt ssl_key = </secret/tls.key ssl_ca = </secret/ca.crt namespace inbox { inbox = yes mailbox Trash { auto = create special_use = \Trash } mailbox Spam { auto = no special_use = \Junk } mailbox Ham { auto = no } mailbox Sent { auto = subscribe special_use = \Sent } } # service auth { # unix_listener auth-master { # mode = 0600 # user = vmail # } # unix_listener /var/spool/postfix/private/auth { # mode = 0666 # user = postfix # group = postfix # } # user = root # } # service auth-worker { # user = root # } # protocol lda { # log_path = /home/vmail/dovecot-deliver.log # auth_socket_path = /var/run/dovecot/auth-master # postmaster_address = postmaster(a)razalabs.com # } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } userdb { driver = static args = uid=102 gid=105 home=/var/mail/domains/%d/%n allow_all_users=yes } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } =================/etc/dovecot/dovecot-sql.conf.ext=============== driver = mysql connect = host=localhost dbname=mail user=root password=pass default_pass_scheme = CRYPT password_query = SELECT email as user, password FROM users WHERE email='%u'; =================dovecot-sql.conf.ext=============== =================/etc/dovecot/dovecot-sql.conf.ext=============== driver = mysql connect = host=localhost dbname=mail user=root password=pass default_pass_scheme = CRYPT password_query = SELECT email as user, password FROM users WHERE email='%u'; =================dovecot-sql.conf.ext=============== and postfix =================/etc/postfix/main.cf=============== inet_protocols = all meta_directory = /etc/postfix shlib_directory = /usr/lib/postfix myhostname = mail.my-domain.com mynetworks = 127.0.0.0/8 message_size_limit = 30720000 virtual_alias_domains = virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_mailbox_base = /var/mail/domains virtual_uid_maps = static:102 virtual_gid_maps = static:105 smtpd_sasl_type = dovecot smtpd_sasl_path = /var/spool/postfix/private/auth smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_authenticated_header = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_use_tls = yes smtpd_tls_cert_file = /secret/tls.crt smtpd_tls_key_file = /secret/tls.key #virtual_create_maildirsize = yes #virtual_maildir_extended = yes proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks virtual_transport = dovecot dovecot_destination_recipient_limit = 1 smtpd_milters = inet:127.0.0.1:8891 milter_default_action = accept =================/etc/postfix/main.cf===============

1 1

migrating dovecot to new server
by David Mehler 30 May '20

30 May '20

Hello, I'm needing to migrate my dovecot installation it's 2.3 on FreeBSD 12.1 to a new server. I'd ideally like to back up all the mails in the maildir location, copy that over, load in my configuration files, and bring the system back up. I doubt it's that easy, any pitfalls I should watch out for? Thanks. Dave.

4 4

director -> POP3s/IMAPs -> mailbox host
by patosec 28 May '20

28 May '20

Hello again, I did a lot of trial and error already, but I can't seem to find a way to encrypt my dovecot director to dovceot mailbox traffic. Is there a way to configure dovecot director to only use ssl/tls encrypted connections for specific tagged mailbox clusters? (or all clusters, in fact does not matter if it could be restricted to tags) Looks like there is also no documentation available for this sort of configuration. I tried setting my mailbox nodes to "ssl = require" butt after doing so I can't login through director proxy anymore. It always looks like ssl/tls termination is finally done on director side. Anyone tried this already or has a running setup doing encryption from lets say frontend to backend? Thanks, greetings Patrick

2 2

service doveadm - how to debug proxying with director
by patosec 28 May '20

28 May '20

Hello everyone, I'm on a small dovecot director -> dovecot mailbox setup and I try to get doveadm command proxying to work. Though I don't get the expected output. My directors do not forward the doveadm commands to the expected backend host. Doveadm is working as expected on the backend hosts, the director hosts just dont log anything about the proxying that should happen or anything else about the doveadm commands at all. Can someone guide me in a direction on what to try next or maybe got a working config regarding doveadm proxying? Thanks in advance! Some technical data regarding my problem: Dovecot Version: 2.3.10 (0da0eff44) Output of a 'doveadm director status' command: mail server ip tag vhosts state state changed users 10.0.0.81 tag1 100 up - 0 10.0.0.82 tag1 100 up - 1 Output of a 'doveadm director ring status' command: director ip port type last failed status ping ms input output buffered buffered peak last read last write 10.0.0.193 9090 self never ring synced 5 - - - - - - 10.0.0.194 9090 right never synced 0 2051 6400 0 757 2020-05-28 09:56:37 2020-05-28 09:56:37 10.0.0.195 9090 left never synced 0 4929 1804 0 37 2020-05-28 09:56:37 2020-05-28 09:56:37 This is my dovecot-director hosts configuration (doveadm related part): service doveadm { inet_listener { # any port you want to use for this: port = 24245 } } local 0.0.0.0 { # password to use for client authentication doveadm_password = secret # allow client to only use specified list of commands (default is all): #doveadm_allowed_commands = } # same port as doveadm's inet_listener doveadm_port = 24245 protocol doveadm { # NOTE: director-userdb socket is actually used only for passdb lookups, not userdb lookups auth_socket_path = director-userdb } And here the dovecot-backend hosts configuration (doveadm related part): ### director conf service doveadm { inet_listener { # any port you want to use for this: port = 24245 } } local 0.0.0.0 { # password to use for client authentication doveadm_password = secret # allow client to only use specified list of commands (default is all): #doveadm_allowed_commands = } A 'doveadm user -u test(a)test.com' command on the backend host: userdb: test(a)test.com user : test(a)test.com home : /var/spool/imap/test(a)test.com quota : maildir:User quota quota_rule: *:storage=1048576:messages=153000 A 'doveadm user -u test(a)test.com' command on the director host: userdb: test(a)test.com user : test(a)test.com

2 3

Determinant of umask for sieve_pipe_bin_dir scripts?
by Laura Smith 27 May '20

27 May '20

Hi, What determines the umask of sieve_pipe_bin_dir scripts ? The results from my script are always being set to 0600. My script is simple and shown below, even if I adjust the right line to add " && chmod 644", the actual resulting file still remains at 0600 ?!? #!/bin/bash # Usage: imapsieve_copy <email> <spam|ham> MSG_USER="$1" MSG_TYPE="$2" RUN_UUID=$(cat /proc/sys/kernel/random/uuid) BASE_DIR="/foo/bar" TARGET_DIR="${BASE_DIR}/${MSG_TYPE}" TARGET_FILE="${TARGET_DIR}/${RUN_UUID}" cat > "${TARGET_FILE}" < /dev/stdin && pigz -9 "${TARGET_FILE}"

2 2