- dovecot - dovecot.org

dovecot: doveconf: Fatal: block_alloc(134217728): Out of memory
by Brent Clark 30 Jun '20

30 Jun '20

Good day Guys Currently on Debian Stretch (2.2.27). This morning we enabled SNI for our clients (file per domain). On going live with the new server configuration, we started getting the following on our shared hosting servers. Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: doveconf: Fatal: block_alloc(134217728): Out of memory Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: config: Fatal: block_alloc(134217728): Out of memory Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: config: Fatal: master: service(config): child 64008 returned error 83 (Out of memory (service config { vsz_limit=512 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) Jun 30 07:25:34 REMOVED_HOSTNAME dovecot: doveconf: Panic: data stack: Out of memory when allocating 2147483688 bytes Jun 30 07:25:37 REMOVED_HOSTNAME dovecot: config: Panic: data stack: Out of memory when allocating 2147483688 bytes This is a server with 2414 domains. On a few of our servers, to buy time, we had to set: default_vsz_limit =10096M A question I would like to ask is. Based on the following change notice, could the following be the problem. https://dovecot.org/pipermail/dovecot-news/2019-July/000412.html - config: Memory leak in config process when ssl_dh setting wasn't set and there was no ssl-parameters.dat file. This caused config process to die once in a while with "out of memory". If anyone could provide any assistance or share a tip on where we can look it would be appreciated. This one has my team and I stumped. Kind regards Brent Clark

1 0

POP3Deleted flag issues
by Justina Colmena ~biz 29 Jun '20

29 Jun '20

Hello, I have been running my own mail server with Dovecot, Postfix, and Cyrus-SASL for authentication. = dovecot22u.x86_64 1:2.2.36.4-1.el7.ius @ius I am basically trying to tune the system for better performance. The flat files "/var/mail/justina" etc exhibit locking issues and conflicts when fetching mail at the same time new mail is being delivered by Postfix. Other mail is stored in "Maildir" type folders accessible via IMAP. These exhibit better performance with finer grained locking. There's an "idea" that was posted to the list 7 years ago, shows up top rank on Google. https://dovecot.org/pipermail/dovecot/2013-May/090114.html I fear either an incomplete implementation of the feature or "here-be-dragons" code that may or may not be completely documented. I would like all the "$POP3Deleted" mail to be moved to an "Archive" Maildir folder accessible via IMAP. How do I accomplish this? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0

layout:fs info
by Stefano Gatto - Fly2Net sas 29 Jun '20

29 Jun '20

Hi all, my dovecot version is 2.2.13, quite standard configuration. Can I add directive LAYOUT=fs in dovecot configuration without losing all my archived messages? This should modify the separator of email folders from dots to slashes, correct? BR Stefano

2 2

Plugin ABI compat between v2.3.8 and v2.3.9
by Alexander Strasser 24 Jun '20

24 Jun '20

Hi all! This is my first post on this list. Please pardon me if I overlooked or misunderstood some things. I had some imap crashes (sig11) starting at the end of 2019 after an upgrade of dovecot. I found out, that I didn't have any problems using version v2.3.8, but any version v2.3.9 and higher would trigger the crashes. After investigating more deeply and creating a core dump, I saw that the crash happened in an external plugin fetchmail_wakeup[1]. After recompiling that plugin with up to date dovecot headers, I didn't get crashes anymore. So I suspect there were ABI incompatible changes and it was forgotten to bump the minimum Plugin-ABI version supported. I could try to follow up some more details, but it would be quite a burden because of rebuilding the plugin with debug symbols against version 2.3.8 of dovecot and triggering the crash etc. Despite that I think it should be possible to detect changes that are ABI incompatible, as otherwise plugin users would always have to find out first hand with unknown consequences. That said there could be a possibility of the plugin using the API/ABI in an invalid way. If that was the cause, then the plugin should be changed. Hope this report turns out to help improve the situation. I don't have problems currently and will in future be sensitive to this specific possible cause of problems, but not having such crashes in the first place, would be worth it and maybe could still help others. Best regards, Alexander 1: slightly reduced version of: https://github.com/marschap/fetchmail_wakeup

2 4

Converting dot-namespaced Maildir to /-namespaced
by Guido Goluke, MajorLabel 24 Jun '20

24 Jun '20

I have a couple of domains on my server, all of them namespaced with a dot. It's 10-15 mailboxes at the most. Is there good way to convert them to / (slash) namespaced folders? Maybe some bash script lying around somewhere?

1 0

dovecot fts configuration without solr
by Danilo Tomasoni 24 Jun '20

24 Jun '20

Hello All, I always used dovecot and I'm pretty happy with it, but recently I changed OS (to ubuntu 18) and to get dovecot LTS with lucene (the default I was using on my previous arch installation) I needed to build from source the version 2.3.10 (the one that came with the repos was older and clucene was not actually supported) The problem is that the Clucene is not behaving well, It indexes only some mails but definitely not all according to my tests (there are also strange assertion errors in the logs) I also tried xapian fts index but is very slow indexing and definitely doesn't seem to work. The problem with solr fts is that solr doesn't even start on my tiny system (odroid C2 with 2GB RAM) and anyway I don't want to bloat all the system for the indexing if possible.. Anyone can suggest me a proper minimal and working configuration? Thank you Danilo

2 2

JMAP support
by Martynas Bendorius 23 Jun '20

23 Jun '20

Hello, Is there any ETA set for JMAP support? Thank you! >> On 11/27/2016 5:28 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> Hi! >> We are working on including JMAP support to Dovecot. At this moment I cannot give any promise for exact version, but hopefully it will be part of v2.3 >> >> Aki Tuomi >> Dovecot Oy -- Best regards, Martynas Bendorius

3 2

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