October 2020 - dovecot

Expiry in kmail
by mh＠mike.franken.de 11 Oct '20

11 Oct '20

Hi *, is there any setting/plugin/... for dovecot, that would enable the "expiry" feature in kmail, i.e. let the client decide, what mails in what folder will expire and should be deleted by the server? TIA. Bye. Michael.

1 0

Replication process Out of memory error
by Joelly Alexander 11 Oct '20

11 Oct '20

Running replication between two nodes and every time a out of memory error is logged when a replication triggered: 2020.10.11 01:43:39 replicator: Panic: data stack: Out of memory when allocating 268435496 bytes 2020.10.11 01:43:39 replicator: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7fcb4403662b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb6c1) [0x7fcb440366c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a149) [0x7fcb43fa5149] -> /usr/lib/dovecot/libdovecot.so.0(+0x49d9d) [0x7fcb43fa4d9d] -> /usr/lib/dovecot/libdovecot.so.0(+0xd7c7d) [0x7fcb44032c7d] -> /usr/lib/dovecot/libdovecot.so.0(+0xfa9b8) [0x7fcb440559b8] -> /usr/lib/dovecot/libdovecot.so.0(+0xd52dc) [0x7fcb440302dc] -> /usr/lib/dovecot/libdovecot.so.0(buffer_write+0x66) [0x7fcb440304d6] -> dovecot/replicator(replicator_queue_push+0xd9) [0x55933ecc4ad9] -> dovecot/replicator(+0x5266) [0x55933ecc4266] -> dovecot/replicator(+0x4952) [0x55933ecc3952] -> dovecot/replicator(+0x4af0) [0x55933ecc3af0] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6f) [0x7fcb4404cadf] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x136) [0x7fcb4404e0d6] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7fcb4404cb7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7fcb4404cce0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fcb43fcd0d3] -> dovecot/replicator(main+0x196) [0x55933ecc2c56] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7fcb43db509b] -> dovecot/replicator(_start+0x2a) [0x55933ecc2d1a] 2020.10.11 01:43:39 replicator: Fatal: master: service(replicator): child 7834 killed with signal 6 (core dumped) Setting vsz_limit doesn't change behavior, the OOM error indicates that it seems trying to allocate even more memory: vsz_limit = 64M says says OOM Error when trying to allocate 67108904 bytes which is 40 bytes more than what is set vsz_limit = 128M says says OOM Error when trying to allocate 268435496 bytes which is 40 bytes more than twice what is set vsz_limit = 256M says says OOM Error when trying to allocate 268435496 bytes which is 40 bytes more than what is set vsz_limit = 512M says says OOM Error when trying to allocate 1073741864 bytes which is 40 bytes more than twice what is set vsz_limit = 1024M says says OOM Error when trying to allocate 1073741864 bytes which is 40 bytes more than what is set vsz_limit = 2048M says says OOM Error when trying to allocate 4294967336 bytes which is 40 bytes more than twice what is set vsz_limit = 4096M says says OOM Error when trying to allocate 4294967336 bytes which is 40 bytes more than what is set vsz_limit = 8192M says says OOM Error when trying to allocate 17179869224 bytes which is 40 bytes more than twice what is set vsz_limit = 16384M says says OOM Error when trying to allocate 17179869224 bytes which is 40 bytes more than what is set everything set larger than 16384M stays at OOM Error when trying to allocate 17179869224... Replication itself seems to work but the error is always logged. # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 5.8.0-0.bpo.2-amd64 x86_64 Debian 10.6 ext4 Thanks, Alex -- ======================================================== Alexander Joelly Bachweg 2 A-8501 Lieboch, AUSTRIA

1 0

Feature request.
by Rogier Wolff 10 Oct '20

10 Oct '20

Hi, I get my Email from my own SMTP server on the internet using "fetchmail". Some time ago I did the smart thing and configured dovecot to use SSL and the letsencrypt certificate that automatically renews. Welllll..... a few days ago my certificate expired and the fetchmail deamon running in the background had nowhere to complain. So I didn't notice. It turns out that dovecot had been running uninterrupted since august 13th, the certificate was renewed on september 7th and I suspect it expired on october 7th. So.... Feature request: check the expiry date on the SSL certificate as it is being loaded and check for a new certificate if it HAS expired. If you worry about performance, this could be done where: TLS handshaking: SSL_accept() failed: error:14094415:SSL routines:ssl3_read_bytes:sslv3 alert certificate expired: SSL alert number 45 is reported. That would mean that ONE client will once get the error before dovecot fixes it. My personal fix is to restart dovecot once a week from now on. I might be running an older version: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-34-generic x86_64 Ubuntu 18.04.5 LTS if it has already been fixed, please accept my apologies. Roger. -- ** R.E.Wolff(a)BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 ** ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** f equals m times a. When your f is steady, and your m is going down your a is going up. -- Chris Hadfield about flying up the space shuttle.

13 17

Core dump with search in a virtual folder with FTS enabled
by Jonathan Moesli 09 Oct '20

09 Oct '20

Hi all, when I try to search in a virtual mailbox with FTS enabled, imap cores dump. Sample IMAP session in a virtual mailbox: 1 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 PREVIEW=FUZZY STATUS=SIZE SAVEDATE LITERAL+ NOTIFY] Logged in2 SELECT Search/All* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.* 1 EXISTS* 0 RECENT* OK [UNSEEN 1] First unseen.* OK [UIDVALIDITY 1602234810] UIDs valid* OK [UIDNEXT 2] Predicted next UID2 OK [READ-WRITE] Select completed (0.002 + 0.000 + 0.001 secs).2 UID SEARCH HEADER From userConnection closed by foreign host. When I search in INBOX all OK: 1 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 PREVIEW=FUZZY STATUS=SIZE SAVEDATE LITERAL+ NOTIFY] Logged in 2 SELECT INBOX* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.* 1 EXISTS* 0 RECENT* OK [UNSEEN 1] First unseen.* OK [UIDVALIDITY 1602234520] UIDs valid* OK [UIDNEXT 2] Predicted next UID* OK [NOMODSEQ] No permanent modsequences2 OK [READ-WRITE] Select completed (0.003 + 0.000 + 0.002 secs).2 UID SEARCH HEADER From user* SEARCH 12 OK Search completed (0.002 + 0.000 + 0.001 secs). Error log: Oct 09 12:58:22 Panic: imap(user)<31554><Y3pl0zqx3s9/AAAB>: Module context fts_mailbox_list_module missingOct 09 12:58:22 Error: imap(user)<31554><Y3pl0zqx3s9/AAAB>: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fbe88afddf2] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fbe88afdefe] -> /usr/lib64/dovecot/libdovecot.so.0(+0xec42e) [0x7fbe88b0842e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xec4d1) [0x7fbe88b084d1] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbe88a5f4ea] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x123f7) [0x7fbe8821f3f7] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0xe2f4) [0x7fbe8821b2f4] -> /usr/lib64/dovecot/lib20_fts_plugin.so(fts_search_lookup+0xd4) [0x7fbe8821b7b4] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x11a98) [0x7fbe8821ea98] -> dovecot/imap(imap_search_start+0x70) [0x55e251f4e620] -> dovecot/imap(cmd_search+0xd6) [0x55e251f3ea86] -> dovecot/imap(command_exec+0x64) [0x55e251f46cc4] -> dovecot/imap(+0x1ce4f) [0x55e251f44e4f] -> dovecot/imap(+0x1ced7) [0x55e251f44ed7] -> dovecot/imap(client_handle_input+0x205) [0x55e251f45365] -> dovecot/imap(client_input+0x75) [0x55e251f45925] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7fbe88b20b45] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12b) [0x7fbe88b2249b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7fbe88b20c49] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fbe88b20e88] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fbe88a90393] -> dovecot/imap(main+0x332) [0x55e251f36f12] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fbe88670555] -> dovecot/imap(+0xf115) [0x55e251f37115]Oct 09 12:58:22 Fatal: imap(user)<31554><Y3pl0zqx3s9/AAAB>: master: service(imap): child 31554 killed with signal 6 (core dumped) Dovecot configuration (doveconf -n):# 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1127.19.1.el7.x86_64 x86_64 CentOS Linux release 7.8.2003 (Core)first_valid_uid = 1000 mail_debug = yesmail_location = maildir:~/Maildir:INDEX=MEMORYmail_plugins = virtual fts fts_lucenembox_write_locks = fcntlnamespace inbox { inbox = yes location = prefix = separator = /}namespace virtual { hidden = yes list = no location = virtual:/etc/dovecot/virtual:INDEX=~/virtual prefix = Search/ separator = / subscriptions = no type = private}passdb { args = scheme=PLAIN username_format=%u /etc/dovecot/users driver = passwd-file}plugin { fts = lucene fts_lucene = whitespace_chars=@.}userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file} Backtrace:#0 0x00007fbe88684387 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55 #1 0x00007fbe88685a78 in __GI_abort () at abort.c:90#2 0x00007fbe88b083e7 in default_fatal_finish (status=0, type=<optimized out>) at failures.c:459#3 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:471#4 0x00007fbe88b084d1 in i_internal_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:848#5 0x00007fbe88a5f4ea in i_panic (format=format@entry=0x7fbe88225058 "Module context fts_mailbox_list_module missing") at failures.c:523#6 0x00007fbe8821f3f7 in fts_mailbox_backend (box=<optimized out>) at fts-storage.c:957#7 0x00007fbe8821b2f4 in fts_search_lookup_level_multi (and_args=<optimized out>, args=0x55e253347698, fctx=0x55e2533be330) at fts-search.c:182#8 fts_search_lookup_level (fctx=fctx@entry=0x55e2533be330, args=0x55e253347698, and_args=and_args@entry=true) at fts-search.c:210#9 0x00007fbe8821b7b4 in fts_search_lookup (fctx=fctx@entry=0x55e2533be330) at fts-search.c:360#10 0x00007fbe8821ea98 in fts_mailbox_search_init (t=0x55e253342e60, args=0x55e2533475c8, sort_program=<optimized out>, wanted_fields=0, wanted_headers=0x0) at fts-storage.c:260#11 0x000055e251f4e620 in imap_search_start (ctx=ctx@entry=0x55e2533353f0, sargs=0x55e2533475c8, sort_program=sort_program@entry=0x0) at imap-search.c:540#12 0x000055e251f3ea86 in cmd_search (cmd=0x55e253335238) at cmd-search.c:48#13 0x000055e251f46cc4 in command_exec (cmd=cmd@entry=0x55e253335238) at imap-commands.c:201#14 0x000055e251f44e4f in client_command_input (cmd=cmd@entry=0x55e253335238) at imap-client.c:1178#15 0x000055e251f44ed7 in client_command_input (cmd=0x55e253335238) at imap-client.c:1243#16 0x000055e251f45365 in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x55e2533349c8) at imap-client.c:1285#17 client_handle_input (client=client@entry=0x55e2533349c8) at imap-client.c:1299#18 0x000055e251f45925 in client_input (client=0x55e2533349c8) at imap-client.c:1343#19 0x00007fbe88b20b45 in io_loop_call_io (io=0x55e25332dfe0) at ioloop.c:713#20 0x00007fbe88b2249b in io_loop_handler_run_internal (ioloop=ioloop@entry=0x55e253311de0) at ioloop-epoll.c:222#21 0x00007fbe88b20c49 in io_loop_handler_run (ioloop=ioloop@entry=0x55e253311de0) at ioloop.c:765#22 0x00007fbe88b20e88 in io_loop_run (ioloop=0x55e253311de0) at ioloop.c:738#23 0x00007fbe88a90393 in master_service_run (service=0x55e253311c40, callback=callback@entry=0x55e251f53340 <client_connected>) at master-service.c:851#24 0x000055e251f36f12 in main (argc=1, argv=0x55e253311960) at main.c:534 I tried with both solr and lucene engines, always core dump. Packages installed: - dovecot-2.3.11.3-4.x86_64 - dovecot-debuginfo-2.3.11.3-4.x86_64 Maybe I missed a configuration parameter? Thank you.

1 0

Dovecot 2.3.10-2.3.11.3 pop3/imap login problem after upgrade
by Michał Smyczyński 09 Oct '20

09 Oct '20

Hi, I came across a following issue. After upgrading dovecot from 2.3.10 to 2.3.11.3 pop/imap logins fail. Auth method is plain/login ,with ssl required and shadow passdb driver, runnning on Slackware Linux 14.1. The configuration in both cases is the same, and in the past, after each uprgade i had no problems. I did not come across also of any information if upgrading from 2.3.10 to 2.3.11.3 require any significant change to auth configuration. Dovecot v2.3.10 (0da0eff44) starting up for pop3, imap (core dumps disabled) pop3-login: Login: user=<test>, method=PLAIN, rip=89.78.12.2, lip=192.168.100.30, mpid=8109, TLS, session=<7aCIhC6xzehZTgwC> Dovecot v2.3.11.3 (502c39af9) starting up for pop3, imap (core dumps disabled) pop3-login: Disconnected (tried to use unsupported auth mechanism): user=<test>, method=USER, rip=89.78.12.2, lip=192.168.100.30, TLS, session=<CYwFfS6xouhZTgwC> I appreciate help if someone knows the cause and solution. Regards

1 0

Sieve not exists
by ＠lbutlr 08 Oct '20

08 Oct '20

I thought this was working as intended, but I have recently been getting some random messages put into this mailbox that definitely have list-ip headers (including some messages from this list) and that do not have multiple addresses. I believe this started happening on 20200922, which would hav been when I applied the most recent update to dovecot, as that is when the listCC box seemed to explode, but I do not have traces over 7 days old. if allof (address :count "ge" :comparator "i;ascii-numeric" ["to", "cc"] ["2"], not exists ["list-id","mailing-list", "x-loop"] ) { fileinto :create "listCC"; stop;} Headers of a message that triggered this (minus Received and signature headers, just removed for length) This is the trace: 23: address test 23: starting `:count-ge' match with `i;ascii-numeric' comparator: 23: extracting `to' headers from message 23: parsing address header value `Kurt Jaeger <dovecot(a)opsec.eu>, dovecot(a)dovecot.org' 23: address value `dovecot(a)opsec.eu' 23: address value `dovecot(a)dovecot.org' 23: extracting `cc' headers from message 23: matching count value `2' 23: with key `2' => 1 23: finishing match with result: matched So, it looks like it is matching Reply-To and/or X-Original-To as well as To? Or is something else happening here? 23: jump if result is false 23: not jumping 24: exists test 24: header `list-id' exists 24: header `mailing-list' is missing 24: headers are missing 24: jump if result is true 24: not jumping Or the logic of "not exists" has changed from AND (meaning none of those headers exist)? 26: fileinto action 26: store message in mailbox `listCC' 27: stop command; end all script execution ## Finished executing script '.active_sieve' Headers of that message (minute received and signature headers, elided just for length) Reply-To: dovecot(a)dovecot.org Return-Path: <dovecot-bounces(a)dovecot.org> X-Original-To: dovecot(a)dovecot.org Delivered-To: dovecot(a)dovecot.org Date: Wed, 30 Sep 2020 17:06:54 +0200 From: Kurt Jaeger <dovecot(a)opsec.eu> To: dovecot(a)dovecot.org Subject: debugging TLS with wireshark and a custom application ? Message-ID: <20200930150654.GT53210(a)home.opsec.eu> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: dovecot(a)dovecot.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Dovecot Mailing List <dovecot.dovecot.org> List-Unsubscribe: <https://dovecot.org/mailman/options/dovecot>, <mailto:dovecot-request@dovecot.org?subject=unsubscribe> List-Archive: <https://dovecot.org/pipermail/dovecot/> List-Post: <mailto:dovecot@dovecot.org> List-Help: <mailto:dovecot-request@dovecot.org?subject=help> List-Subscribe: <https://dovecot.org/mailman/listinfo/dovecot>, <mailto:dovecot-request@dovecot.org?subject=subscribe> Errors-To: dovecot-bounces(a)dovecot.org Sender: "dovecot" <dovecot-bounces(a)dovecot.org> There is one address in the To and no CC header at all, so why was this filed into listCC? (This is the only incidence of listCC in the sieve file for the list user) -- "I used to hate the sun, because it'd shone on everything I'd done. Made me feel that all that I had done was overfill the ashtray of my life."

2 1

How do I make "vnd.dovecot.environment" available?
by Graham Leggett 08 Oct '20

08 Oct '20

Hi all, According to the docs at https://wiki.dovecot.org/Pigeonhole/Sieve, some extensions are not available by default. The docs tell me the sieve_plugins, sieve_extensions and/or sieve_global_extensions configs are involved, but I can find no authoritative documentation as to what the values should be. What values must I use to make “vnd.dovecot.environment” available? Adding "sieve_global_extensions = +vnd.dovecot.environment” to 90-sieve.conf seems to not be enough. [root@gatekeeper ~]# sievec -D /var/lib/dovecot-sieve/default.sieve sievec(root): Debug: sieve: Pigeonhole version 0.5.8 (b7b03ba2) initializing sievec(root): Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. sievec(root): Debug: sieve: file storage: Using Sieve script path: /var/lib/dovecot-sieve/default.sieve sievec(root): Debug: sieve: file script: Opened script `default' from `/var/lib/dovecot-sieve/default.sieve' default: line 5: error: require command: unknown Sieve capability `vnd.dovecot.environment'. default: line 19: error: referring to variable in unknown namespace 'vnd'. default: error: validation failed. sievec(root): Fatal: failed to compile sieve script '/var/lib/dovecot-sieve/default.sieve' Regards, Graham —

3 5

dovecot: lmtp: Error: fatal error: failed to reserve page summary memory
by Roman Vasilyev 08 Oct '20

08 Oct '20

Sorry for offtopic, don't know where to ask it after updating from `ubuntu` 18 to 20 started getting this on running golang binary from sieve rules file ``` Sep 17 08:54:00 lonjemail spamd[3231]: spamd: connection from ::1 [::1]:57844 to port 783, fd 5 Sep 17 08:54:00 lonjemail spamd[3231]: spamd: setuid to Debian-exim succeeded Sep 17 08:54:00 lonjemail spamd[3231]: spamd: processing message <CANcP0tbws-r=L8KrTug_NKLk0EuPwo1vKotdpV=Pf95Pxusbww(a)mail.gmail.com> for Debian-exim:114 Sep 17 08:54:00 lonjemail systemd-resolved[527]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 17 08:54:00 lonjemail systemd-resolved[527]: message repeated 8 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Sep 17 08:54:00 lonjemail spamd[3231]: spamd: clean message (1.1/5.0) for Debian-exim:114 in 0.3 seconds, 2760 bytes. Sep 17 08:54:00 lonjemail spamd[3231]: spamd: result: . 1 - DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,RDNS_NONE,SPF_HELO_NONE,SPF_PASS scantime=0.3,size=2760,user=Debian-exim,uid=114,required_score=5.0,rhost=::1,raddr=::1,rport=57844,mid=<CANcP0tbws-r=L8KrTug_NKLk0EuPwo1vKotdpV= Pf95Pxusbww(a)mail.gmail.com>,autolearn=no autolearn_force=no Sep 17 08:54:00 lonjemail dovecot: lmtp(4254): Connect from local Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: fatal error: failed to reserve page summary memory Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime stack: Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.throw(0x1a48db5, 0x25) Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/panic.go:1116 +0x72 fp=0x7ffe160d5860 sp=0x7ffe160d5830 pc=0x4ce5d2 Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.(*pageAlloc).sysInit(0x232c268) Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/mpagealloc_64bit.go:80 +0x185 fp=0x7ffe160d58f0 sp=0x7ffe160d5860 pc=0x4c4e25 Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.(*pageAlloc).init(0x232c268, 0x232c260, 0x25cb8d8) Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/mpagealloc.go:317 +0x75 fp=0x7ffe160d5918 sp=0x7ffe160d58f0 pc=0x4c2815 Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.(*mheap).init(0x232c260) Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/mheap.go:743 +0x24b fp=0x7ffe160d5940 sp=0x7ffe160d5918 pc=0x4bf84b Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.mallocinit() Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/malloc.go:480 +0x109 fp=0x7ffe160d5968 sp=0x7ffe160d5940 pc=0x4a4c49 Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.schedinit() Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/proc.go:563 +0x65 fp=0x7ffe160d59c0 sp=0x7ffe160d5968 pc=0x4d1f25 Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.rt0_go(0x7ffe160d5ad8, 0x2, 0x7ffe160d5ad8, 0x1813580, 0x7fd3cc8a80b3, 0x7fd3cca6cb80, 0x7ffe160d5ad8, 0x200011c00, 0x501080, 0x1813580, ...) Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/asm_amd64.s:214 +0x125 fp=0x7ffe160d59c8 sp=0x7ffe160d59c0 pc=0x5011c5 Sep 17 08:54:00 lonjemail dovecot: lmtp(roman)<4254></X0wOCgkY1+eEAAAgcArzw>: program exec:/usr/lib/dovecot/sieve-execute/smtp (4255): Terminated with non-zero exit code 2 Sep 17 08:54:00 lonjemail dovecot: lmtp(roman)<4254></X0wOCgkY1+eEAAAgcArzw>: sieve: msgid=<CANcP0tbws-r=L8KrTug_NKLk0EuPwo1vKotdpV=Pf95Pxusbww(a)mail.gmail.com>: stored mail into mailbox 'Unsubscribe.Neighbors' Sep 17 08:54:00 lonjemail dovecot: lmtp(4254): Disconnect from local: Client has quit the connection (state=READY) Sep 17 08:55:01 lonjemail CRON[4257]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) ``` here is sieve rules: ``` require ["variables", "fileinto", "mailbox", "vnd.dovecot.execute"]; if address :matches "from" "*" { set "from" "${1}"; } if anyof ( header :contains "subject" "unsubscribe neighbours", header :contains "subject" "unsubscribe neighbors") { execute "smtp" "-neighbors=${from}"; fileinto :create "Unsubscribe.Neighbors"; } elsif address :contains "from" ["mailer-daemon", "postmaster", "internet mail delivery"] { if header :matches "X-Failed-Recipients" "*" { execute "smtp" "-email=${1}"; fileinto :create "Mail Delivery System"; } else { fileinto :create "Mail Delivery System.Warning"; } } else { # The rest goes into INBOX # default is "implicit keep", we do it explicitly here keep; } ``` Attempted in `/etc/dovecot/conf.d/90-sieve.conf` vsz_limit = 256M with no luck Can somebody help me in fixing it?

2 2

custom userdb server, Exim, and proxying
by Felipe Gasper 08 Oct '20

08 Oct '20

Hi all, We have Exim using Dovecot for authentication. Dovecot, in turn, consults a custom internal server that answers Dovecot’s userdb queries. When IMAP connections arrive, for some users we want to forward those connections--without authentication--to an external IMAP server. For these users, we return “proxy_maybe” and “nopassword” in the authn response from our userdb server. This tells Dovecot to proxy the connection to a new server without trying to authenticate. Exim, though, doesn’t grok “proxy_maybe”, so it just sees “nopassword”. In response, it just skips SMTP authentication entirely. We could address this if our custom service could know whether the authn is for Exim or not. Exim does send a “service=smtp” in its request to /var/run/dovecot/auth-client, but thus far I don’t see that that’s being passed on to the userdb server. Is there any way I can configure Dovecot so that our userdb server can detect when it’s Exim doing the authentication? Alternatively we could just authenticate on the proxy (i.e., stop sending “nopassword”), but that will entail a new requirements for passwords to be in sync; ideally we’d like to avoid that. Any insight from this group would be much appreciated. Thank you! cheers, -Felipe Gasper

2 1

replication flag default setting?
by Norman King 08 Oct '20

08 Oct '20

Hello. I'm playing with dovecot replication. I have a working replication config on a test server and would like to copy that to production but i don't know what's going to happen with existing accounts. Will they automatically start replicating without any further input from me? Is there a flag on the account somewhere that can tell me what the replication status is? Any thoughts on this would be appreciated. dovecot version 2.3.7.2 -- regards Norman King Compass Foundation sysadmin/tech support Phone, 856-974-5335 ext 221 support(a)compassfoundation.io <mailto:support@compassfoundation.io> Website <https://compassfoundation.io>

2 1