- dovecot - dovecot.org

Panic mbox_sync_handle_header
by Igor Russkih 25 Oct '20

25 Oct '20

Hello all, I'm getting a very often panic on my local dovecot setup when accessing some of the local folders. Error message is always Oct 25 14:34:50 imap(irusskikh): Panic: file mbox-sync.c: line 665 (mbox_sync_handle_header): assertion failed: (mail_ctx->mail.from_offset + move_diff != 1 && mail_ctx->mail.from_offset + move_diff != 2) Oct 25 14:34:50 imap(irusskikh): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa05a2) [0x7f05e40005a2] -> /usr/lib/dovecot/libdovecot.so.0(+0xa069a) [0x7f05e400069a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f05e3f901d8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x8b1d7) [0x7f05e432b1d7] -> /usr/lib/dovecot/libdovecot-storage.so.0(mbox_sync+0x48) [0x7f05e432bbf8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mbox_storage_sync_init+0x3b) [0x7f05e432bd3b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) [0x7f05e42eb704] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7f05e42eb7a7] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7f05e43663c1] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7f05e42ebb51] -> dovecot/imap(imap_status_get+0x77) [0x7f05e4c25017] -> dovecot/imap(cmd_status+0x19e) [0x7f05e4c171de] -> dovecot/imap(command_exec+0x5c) [0x7f05e4c1ce0c] -> dovecot/imap(+0x1b382) [0x7f05e4c1b382] -> dovecot/imap(+0x1b41c) [0x7f05e4c1b41c] -> dovecot/imap(client_handle_input+0x18d) [0x7f05e4c1b7dd] -> dovecot/imap(client_input+0xac) [0x7f05e4c1bd2c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f05e4016642] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e) [0x7f05e4017cee] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x36) [0x7f05e40166d6] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f05e4016888] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f05e3f9aa83] -> dovecot/imap(main+0x329) [0x7f05e4c0e139] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f05e3b81b97] -> dovecot/imap(_start+0x2a) [0x7f05e4c0e2ca] Oct 25 14:34:50 imap(irusskikh): Fatal: master: service(imap): child 12785 killed with signal 6 (core dumped) # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.4.0-17763-Microsoft x86_64 Ubuntu 18.04.4 LTS Running now on WSL, but have the same badness on generic ubuntu setup as well. Could somebody guide me if thats something known, or me doing bad things? I'm not on the list, so please CC me. Igor

1 0

dovecot.lda-dupes
by ＠lbutlr 24 Oct '20

24 Oct '20

What is the purpose and/or use of the dovecot.lda-dupes file that (sometimes) exists in the home folder for each user? I've seen some posts about issues with the file or losing track of the location, etc, but nothing on what the file actually does or how it could be useful. I assume it is just a dovecot file that helps not keep track of … I guess duplicate mails? It looks like it contains the message-ids and email destinations for certain, but not all, duplicate emails, but in a binary format. -- "The good news: Hadron Collider went live and did not destroy ALL reality. Bad: I'm the only one who remembers President Gore's 2 terms." --Andy Ihnatko

2 1

net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied
by mj 24 Oct '20

24 Oct '20

Hi, We are getting very occasional messags from dovecot: > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied Over the last week, the message appeared five times. (on a mail server with over 100 users, to that's basically almost never) doveconf -n below > # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.4 () > # OS: Linux 4.19.0-10-amd64 x86_64 Debian 10.6 xfs snip... > service stats { > unix_listener stats-reader { > group = vmail > mode = 0660 > user = vmail > } > unix_listener stats-writer { > group = vmail > mode = 0660 > user = vmail > } > } and the on-disk permissions are: > root@dovecot:~# ls -l /var/run/dovecot/*stat* > srw------- 1 root root 0 Oct 6 00:25 /var/run/dovecot/old-stats > prw------- 1 root root 0 Oct 6 00:25 /var/run/dovecot/old-stats-mail > prw------- 1 root root 0 Oct 6 00:25 /var/run/dovecot/old-stats-user > srw-rw---- 1 vmail vmail 0 Oct 6 00:25 /var/run/dovecot/stats-reader > srw-rw---- 1 vmail vmail 0 Oct 6 00:25 /var/run/dovecot/stats-writer We're not sure what makes the Permission denied error happen... Anyone with an idea? MJ

3 3

Sieve_before
by ＠lbutlr 24 Oct '20

24 Oct '20

So, this is what I did instead of default_sieve: sieve_before = file:/usr/lib/dovecot/sieve/bcc.sieve sieve_before2 = file:/usr/lib/dovecot/sieve/filespam.sieve # cat /usr/lib/dovecot/sieve/bcc.sieve require ["variables", "copy"]; if address :matches ["To", "Cc"] ["*@*."] { redirect :copy "backup+295.${1}.${2}@. . ."; } # cat /usr/lib/dovecot/sieve/filespam.sieve require ["fileinto", "imap4flags"]; if header :contains "X-spam-flag" "YES" { fileinto :flags "\Seen" "Junk"; } The bcc.sieve file is generated each day with a little script to put in the day of the year, so that for the backup user the folder structure for backups for my list mail is, for example: 295 kremels kreme <messages> otheruser kreme <messages> And tomorrow new folders for 296 will be created. So far, I think it's working. 🤞 -- C code. C code run. Run, code, run.

4 17

antispam plugin again
by Maciej Milaszewski 23 Oct '20

23 Oct '20

Hello I have a problem with migrating dovecot from 2.2.36 to 2.3.8 - everything works fine, but a problem with migrating anti-spam plugins New dovecot 2.3.x has implemented own antispam-plugin like: ---- new from dovecot 2.3.8 ----- # From elsewhere to Spam folder imapsieve_mailbox1_name = Spam imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/usr/lib64/dovecot/sieve/report-spam.sieve # From Spam folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Spam imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/usr/lib64/dovecot/sieve/report-ham.sieve sieve_pipe_bin_dir = /usr/lib64/dovecot/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment #setting_name = value sieve_global_dir = /etc/sieve_global sieve_max_redirects = 20 sieve_vacation_use_original_recipient = yes expire = SPAM #expire_dict = proxy::expire expire_dict = redis:host=127.0.0.1:prefix=expire/ --------------------------------------------------------------------------------------- In older version dovecot I use antispam_plugin + simple script: ---------------- old from 2.2.36.4 + antispam plugin ---------- ... antispam_backend = MAILTRAIN antispam_mail_spam = --spam antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/local/bin/spam-learn.sh antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = spam;inbox.spam;Unwanted antispam_trash_pattern_ignorecase = trash;Deleted *;Junk*;kosz antispam_debug_target = syslog antispam_verbose_debug = 1 ------------------------- How do I change the bash file to make it work like on the old system (I use pyzor) like: cat /usr/local/bin/spam-learn.sh #!/bin/sh date >> /tmp/spam.txt echo $@ >> /tmp/spam.txt if [ "x$1" = "x--spam" ]; then /usr/bin/pyzor report >> /tmp/spam.txt 2>&1 fi if [ "x$1" = "x--ham" ]; then /usr/bin/pyzor whitelist >> /tmp/ham.txt 2>&1 fi

1 0

Error: Mailbox INBOX: Transaction commit failed: FTS transaction commit failed: transaction context
by Graham Leggett 22 Oct '20

22 Oct '20

Hi all, While trying to reindex a large mailbox to take advantage of Apache Tika, dovecot logs the following message: Error: Mailbox INBOX: Transaction commit failed: FTS transaction commit failed: transaction context The message is vague in that a transaction has failed, but nowhere does it say what the transaction boundaries are. Did the transaction affect the indexing of one message, or many messages? Did the indexing of the whole mailbox get aborted and rolled back, or just a single message? A wide question. How do I ensure that my shiny new dovecot index gets completely reindexed? How do I know if dovecot is indexing just the new messages, and ignoring the existing messages? Regards, Graham —

1 0

Best prometheus exporter for Dovecot 2.3 with the new metrics/stats module
by Sidsel Jensen 22 Oct '20

22 Oct '20

Hi ppl. I am trying to locate the best prometheus exporter for use with Dovecot 2.3 in connection with the new metrics/stats module. Any pointers in the right direction will be appreciated - seems like there is a bunch out there which all works with the old stats module. Anybody have something “in the works” for 2.3 ? Kind Regards, Sidsel Jensen

2 1

Testing with imaptest to non existing folder makes imap service crash
by Marc Roos 22 Oct '20

22 Oct '20

FWIIW I had this message still in drafts /usr/bin/imaptest - append=100,0 logout=0 host=xxx port=143 user=xxx pass=xxx seed=100 secs=1 clients=1 mbox=64kb.mbox box=inbox/test msgs=100000 And inbox/test does not exist, results in: Fatal: master: service(imap): child 20282 killed with signal 11 (core dumped)

2 1

Understanding matches in sieve
by ＠lbutlr 22 Oct '20

22 Oct '20

RFC 5229 gives the following example: if address :matches ["To", "Cc"] ["coyote(a)**.com", "wile(a)**.com"] { # ${0} is the matching address # ${1} is always the empty string # ${2} is part of the domain name ("ACME.Example") fileinto "INBOX.business.${2}"; stop; And I do not understand why ${1} is always the empty string. In this example, ${1} is the part before the < so using ${2} makes sense. if header :matches "List-ID" "*<*@*" { fileinto "INBOX.lists.${2}"; stop; } I am laso not sure why the first example used **.com instead of *.com (or is that the reason $1 doesn't contain anything because it is the first * of **?). If so, my familiarity with the bash syntax for ** may have been my undoing. If I had # Given to kremels(a)kreme.com if address :matches ["To", "Cc"] ["*(a)*.*"] # ${1} would contain "kremels" # ${2} would contain "kreme" # ${3} would contain "com" Yes? -- "Are you pondering what I'm pondering?" "Sure, Brain, but how are we going to find chaps our size?"

2 2

Users unable to login
by jesus san miguel 22 Oct '20

22 Oct '20

I have certain power users who can't login through POP3 or IMAP from their computer while being receiving mail on their cell phones (pop3), despite pop3_lock_session = no Am I hitting some other limit? I don't see any error in dovecot.log but a generic failed login: Oct 21 10:31:44 imap-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<someuser(a)somedomain.com>, method=DIGEST-MD5, rip=::1, lip=::1, secured, session=<XSVQLSqy2IYAAAAAAAAAAAAAAAAAAAAB> Running version is 2.3.11.3

4 8

Restrictions on default.sieve
by ＠lbutlr 21 Oct '20

21 Oct '20

Are there actions that default.sieve cannot take? I tried adding redirect :copy "backup+foo(a)local.example.com" and… nothing. No errors I can find, but also no mail being redirected. I also tried # there must be 'from' in the received headers if header :contains "received" "from" { redirect :copy "backup+foo(a)local.example.com" } And if header :index 1 :contains "received" "from" { redirect :copy "backup+foo(a)local.example.com" } But still, no mail in .foo for the backup user (yes, dovecot is setup to autofile +address into mailboxes, and that works). -- You couldn't say, 'I had orders.' You couldn't say, 'It's not fair.' No one was listening. There were no Words. You owned yourself. ... Not Thou Shalt Not. Say I Will Not. --Feet of Clay

2 3

A user's last access time
by Victor Sudakov 21 Oct '20

21 Oct '20

Dear Colleagues, Is there a file or directory within a user's Maildir, whose date of modification or access indicates the last time the user accessed his/her E-mail via IMAP or POP3? I'd like to figure out the time a user last logged in into his/her mail account, not the last time a mail was delivered to the INBOX. This information is probably available in the log, but a file which is touched each time a user accesses his/her mail, is more convenient. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/

7 13

Corrupted dbox file + assertion failure
by tim＠linux-daus.de 21 Oct '20

21 Oct '20

Hi all, a dsync failed due a corrupted mdbox file. Force-resync throws the same error. (Dovecot 2.3.9.2) Is there any change to fix/repair the file? dsync-local(LOCALPART(a)DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning: fscking index file /var/mail/12/DOMAIN.TLD/242/LOCALPART/mdbox/storage/dovecot.map.index dsync-local(LOCALPART(a)DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning: mdbox /var/mail/12/DOMAIN.TLD/242/LOCALPART/mdbox/storage: rebuilding indexes dsync-local(LOCALPART(a)DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Error: Corrupted dbox file /var/mail/12/DOMAIN.TLD/242/LOCALPART/mdbox/storage/m.6 (around offset=5191109): msg header has bad magic value dsync-local(LOCALPART(a)DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Panic: file dbox-file-fix.c: line 219 (dbox_file_find_next_magic): assertion failed: (ret == -1) dsync-local(LOCALPART(a)DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Error: Raw backtrace: #0 t_askpass[0x7fbf4218b5f0] -> #1 backtrace_append[0x7fbf4218b860] -> #2 backtrace_get[0x7fbf4218b9c0] -> #3 i_syslog_error_handler[0x7fbf42196840] -> #4 default_fatal_handler[0x7fbf42196910] -> #5 i_fatal[0x7fbf420ec3b7] -> #6 dbox_attachment_file_get_stream[0x7fbf424c1010] -> #7 dbox_file_fix[0x7fbf424c1540] -> #8 mdbox_get_setting_parser_info[0x7fbf424b9290] -> #9 mdbox_storage_rebuild_in_context[0x7fbf424b99a0] -> #10 mdbox_sync_begin[0x7fbf424bbd00] -> #11 mdbox_sync[0x7fbf424bc730] -> #12 mdbox_storage_sync_init[0x7fbf424bc7f0] -> #13 mailbox_sync_init[0x7fbf4249ee80] -> #14 mailbox_sync[0x7fbf4249ef70] -> #15 dsync_brain_master_send_mailbox[0x55d6521dcaa0] -> #16 dsync_brain_run[0x55d6521daae0] -> #17 dsync_brain_run[0x55d6521db360] -> #18 dsync_ibc_has_pending_data[0x55d6521f0840] -> #19 io_loop_call_io[0x7fbf421b0490] -> #20 io_loop_handler_run_internal[0x7fbf421b1e20] -> #21 io_loop_handler_run[0x7fbf421b05c0] -> #22 io_loop_run[0x7fbf421b0810] -> #23 who_line_filter_match[0x55d6521bfa00] -> #24 doveadm_dsync_main[0x55d6521c2280] -> #25 doveadm_mail_single_user[0x55d6521c3090] -> #26 doveadm_mail_try_run[0x55d6521c3900] -> #27 main[0x55d6521b2030] -> #28 __libc_start_main[0x7fbf417c61f0] -> #29 _start[0x55d6521b2670] -> #30 [no start/end information] Regards, Tim

2 1

doveadm http api hign performance?
by hfh＠cndns.com 21 Oct '20

21 Oct '20

Does doveadm http api have high execution efficiency? I have a program that directly calls doveadm http api. Will there be an efficiency problem if a large number of users call it? hfh(a)cndns.com

1 0

How to move/reorganise existing e-mails to yearly subfolders
by R. Diez 21 Oct '20

21 Oct '20

Hi all: I am new to e-mail servers and I am evaluating Dovecot. Not really the best combination. 8-) I am trying to find a balance between legal data retention requirements and online mailbox size. I do not want huge online mailboxes, as doing offline, rotating data backups could then take forever (among other reasons). I would rather avoid online (cloud) backups (data protection etc.). If I set a mailbox size limit, users will have to delete old mails by themselves. Or I could somehow script the deletion of attachments from old e-mails, as attachments are usually the main cause of huge mailboxes. Incidentally, can anyone point me to an easy way to achieve this? Preferably over with IMAP, otherwise with Dovecot tools. With regards to legal data retention (which I am no expert about either), I thought I could use some Postfix BCC feature I heard about in order to copy all incoming and outgoing e-mails to a single "data retention" mailbox. Or maybe several of them. I could then archive e-mails from that mailbox on a yearly basis. I would like to automatically organise e-mails inside that mailbox into subfolders like this: 2019/alice 2019/bob 2020/alice 2020/bob That is: [year]/[username] With such a folder structure, it is easier to see what is going on. Is there a tool that can reorganise existing e-mails into such a folder structure? I found some tools on the Internet to backup and export mails from IMAP to IMAP or maildir destinations. But I could not find a tool that just reorganises (moves) e-mails in such a manner inside an existing mailbox, maybe with a user-defined pattern for the destination folders. I guess moving e-mails around on the same mailbox would be much faster than exporting and reimporting them in some clever way. I could always write a Perl script, but that takes time. Such a tool may already exist. Or perhaps somebody could mention a similar, good-written script I can use as a starting point. I am sure there are many small gotchas to avoid. At the moment, I am only confident with Perl and Java. Maybe JavaScript. It would be best to reorganise the e-mails over IMAP. This way, I am independent of the e-mail server. But a Dovecot-specific solution would also be helpful. I could use such a reorganisation tool not just for archiving or data retention purposes, but to reorganise other mailboxes too, like my personal mailbox. I would rather have a script. Clicking around in Thunderbird does not scale. I have seen that you can use a "sieve" in Dovecot to achieve this. But I guess that would only apply to new e-mails. And that would probably apply just to incoming mails, and not to outgoing ones. If I migrate from the existing e-mail servers, the e-mails will probably be mass-imported without going through any "sieve", right? Besides, I already have a few huge mailboxes with many years of e-mails, stored in a different e-mail server, and it would be nice to be able to reorganise them as they are. That way, I could archive the existing older e-mails before migrating to Dovecot, which would reduce the disk size and the export/import time for the migration. Many thanks in advance, rdiez

4 5

modify dovecot user/pass_queries to deliver to local aliases via dovecot submission, with postfixadmin/sqlite3 tables?
by PGNet Dev 21 Oct '20

21 Oct '20

I run dovecot + postfix with postfixadmin/sqlite3 I'm set up for all/only virtual users. All outbound mail submits via dovecot submission port. My current dovecot pass/user db queries are password_query = \ SELECT \ username as user, \ password, \ '/data/vmail/%d/%n/Maildir' as userdb_home, \ 5000 as userdb_uid, \ 5000 as userdb_gid \ FROM mailbox WHERE username = '%u' AND active = '1' user_query = \ SELECT \ '/data/vmail/%d/%n/Maildir' as home, \ 5000 AS uid, \ 5000 AS gid, \ ('dirsize:storage=' || quota) AS quota \ FROM mailbox WHERE username = '%u' AND active = '1' It works perfectly for real addresses. I've setup an alias address, e.g. REAL: realuser(a)example.com ALIAS: aliasuser(a)example.com INBOUND email to the ALIAS address -- from the 'net, delivered from postfix via LMTP to dovecot backend -- works fine. BUT any/all mail from local users TO the ALIAS addr fail at userDB lookup 2020-10-20 12:26:54 lmtp(aliasuser(a)example.com)<rI49JP45j19D8QAA+IOfAw>: Debug: auth-master: userdb lookup(aliasuser(a)example.com): auth USER input: 2020-10-20 12:26:54 lmtp(aliasuser(a)example.com)<rI49JP45j19D8QAA+IOfAw>: Debug: auth-master: userdb lookup(aliasuser(a)example.com): Userdb lookup failed What mods are required to the password_query &/or user_query in order to FIX the local->aliasuser mail lookup and delivery ... and ideally not break the rest of delivery?

1 1

lib22_push_notification_lua_plugin.so: undefined symbol: dlua_dovecot_register
by Mrinal Sharma 20 Oct '20

20 Oct '20

I am trying to use Lua Notification plugin for Event push But saw this error. Can anyone help me on this issue. Error In the logs when I receive an Email is given below. ========================================== Oct 15 21:55:41 master: Info: Dovecot v2.3.11.3 (502c39af9) starting up for imap, lmtp Oct 15 21:56:51 lmtp(36): Fatal: Couldn't load required plugin /usr/lib/dovecot/modules/lib22_push_notification_lua_plugin.so: dlopen() failed: /usr/lib/dovecot/modules/lib22_push_notification_lua_plugin.so: undefined symbol: dlua_dovecot_register ====================================================================== # dovecot -n # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # OS: Linux 4.19.128-microsoft-standard x86_64 Debian 10.6 9p # Hostname: 238afcc76ba9 auth_debug = yes auth_mechanisms = plain oauthbearer xoauth2 auth_verbose = yes disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it log_path = /dev/stdout mail_debug = yes mail_location = maildir:/data/imap_store/%n mail_plugins = " quota" namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Greeting { auto = create } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = no special_use = \Trash } prefix = } passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-oauth2.plain.conf.ext driver = oauth2 mechanisms = plain login } plugin { push_lua_url = http://localhost:5678/mailnotify push_notification_driver = lua:file=/notify.lua quota = maildir:User quota quota_rule = *:storage=5MB quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO } protocols = imap lmtp service doveadm { inet_listener http { port = 80 } } service health-check { executable = script -p health-check.sh inet_listener health-check { port = 5001 } } service lmtp { inet_listener lmtp { address = * port = 24 } process_min_avail = 5 } ssl = no userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota quota notify push_notification push_notification_lua" postmaster_address = postmaster@domainname } protocol lda { mail_plugins = " quota notify push_notification" } protocol imap { imap_metadata = yes mail_plugins = " quota imap_quota quota" }

2 4

Problem with LDAP-query (Active Directory) on filter by memberOf
by Luca Bertoncello 20 Oct '20

20 Oct '20

Hi list! We have a Dovecot 2.3.4 (from Debian 10 repository) that should connect to our AD to authenticate the users. It works, but now we would like to restrict using IMAP to all users in the Group "Funktion - E-Mail-Konto". So I changed the query from: (&(sAMAccountName=%n)(objectClass=user)(homeMDB=*)) to (&(sAMAccountName=%n)(objectClass=user)(homeMDB=*)(memberOf=CN=Funktion - E-Mail-Konto,OU=Funktionen,OU=People,DC=ad,DC=company,DC=org)) The baseDN is DC=ad,DC=company,DC=org With ldapsearch I can get all users and their attributes, but Dovecot fail with this error: Oct 20 15:57:10 mailgw02 dovecot: auth: Error: ldap(testuser,80.187.107.28,<eLf0mhqyLwlQu2sc>): ldap_search(base=dc=ad,dc=company,dc=org filter=(&(samAccountName=testuser)(objectClass=user)(homeMDB=*)(memberOf=CN=Funktion - E-Mail-Konto,OU=Funktionen,OU=People,DC=ad,DC=company,DC=org))) failed: Operations error I didn't found any explanation for this error... Can someone help me? The user used for the connection is the same in Dovecot and ldapsearch. Thanks a lot Luca Bertoncello (lucabert(a)lucabert.de)

1 0

Dovecot docker auto-responder - delegate to external SMTP
by Thomas Pronold 19 Oct '20

19 Oct '20

Hi all, I have dockerized my dovecot setup. Everything works fine besides auto-responder using sieve. Issue is that the my dovecot docker image does NOT come with a SMTP which could be used for outgoing mail. My SMTP setup (postfix) is in another image/container. I want to keep it that way, so that dovecot and postfix have separate images. So basically I have 2 containers running in the same internal network: a) dovecot IP 192.168.10.11 b) postfix IP 192.168.10.22 How do I have to configure dovecot so that it delegates all outgoing (autoresponder) mails to the SMTP on IP 192.168.10.22. The postfix image is configured in a way that certain IPs are allowed to send mails without authentication. So on postfix side I am set. Currently I did a quickfix: I added postfix to dovecot image and configured postfix to use the relayhost 192.168.10.22 for mailing. This works, still I would prefer having the dovecot image not containing an postfix SMTP. Thanks Tom

4 3

Unable to access mail via Outlook
by Odhiambo Washington 19 Oct '20

19 Oct '20

Hola, Dovecot- 2.3.11.3 with mdbox. I have a situation where I can access (view) the e-mails when I use a web-based IMAP client, but NOT M$ Outlook (configured for IMAP). Is there an easy way to solve this? When I send an e-mail to the mailbox address, I can see it on the webmail, but not on Outlook. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 13

Using NFS to extend local email storage
by Maciej Kokociński 19 Oct '20

19 Oct '20

We are running our IMAP mail server on a VPS in the cloud (dovecot+exim+horde webmail), and we are using our on-premises NAS for daily backups through custom rsync scripts (which work well with maildir). There is a lot of storage available on the NAS, while not so much on the VPS. Since, we often get downtime on-premises due to power outages we cannot move the mail server on-premises (though the outages do not interfere too much with the backups). Additional storage in the cloud is at a premium as we would like to avoid further increasing costs. Now, my idea is to set up an NFS volume on the NAS, and configure the cloud-based server as the client. I would like to store only the most recent emails on the main server, and keep the whole data set on the NAS. Naturally I have read the dovecot wiki concerning NFS, and I have browsed this mailing list's archive for answers, but I still have many concerns. Ideally, I would like to use as much storage as possible from the main server, so that only really old emails need to be fetched over the network if requested over IMAP. Also I would like the search function to work regardless whether the NAS is available or not. I wonder if anybody tried a similar configuration before. My concerns are: - should I use NFS volume directly and configure FS-Cache, or should I configure a cache volume separately using e.g. bcache or some other tool? - how to configure the cache to keep as many files and metadata locally? - is it possible to fine tune the cache so it always keeps all the newly created/modified files locally? - is it possible to tune the cache so it keeps at least n files for each user (each maildir)? - will it work fine if I put NFS traffic into an ssh tunnel for security? - will dovecot freeze/crash when the NFS volume disconnects or is temporarily unavailable, what will actually happen in such circumstances? - will the search function work when the NFS volume is unavailable? (I also plan to use solr in the future) - what happens when the main server crashes and then recovers from the NFS share? is the share guaranteed to be consistent? I hope that I have not asked too many questions for a single message... ;) I would really appreciate any help, because I am rather a newbie in dovecot administration, and it overwhelms me. Perhaps, what I am trying to achieve is not the way to go. I am open to suggestions. Best regards, Maciej

4 3

Strange permissions error - Failed to stat sieve storage path
by Graham Leggett 18 Oct '20

18 Oct '20

Hi all I have dovecot-lda set up to run as vmail:vmail, with some sieve scripts in /var/lib/dovecot/sieve. The sieve scripts fail to be found with the following (detailed and very helpful) error message: Oct 14 16:13:33 gatekeeper dovecot[8109]: lda(minfrin(a)example.com)<8109><ZJ9nMo0Hh1+tHwAAKdTwig>: Error: sieve: file storage: Failed to stat sieve storage path: stat(/var/lib/dovecot/sieve/vacation.sieve) failed: Permission denied (euid=387(vmail) egid=387(vmail) missing +x perm: /var/lib/dovecot, we're not in group 97(dovecot), dir owned by 97:97 mode=0750) In this case, the user vmail is a member of the dovecot group: [root@gatekeeper dovecot]# cat /etc/group | grep vmail mail:x:12:postfix,vmail,opendmarc,opendkim,openarc dovecot:x:97:vmail vmail:x:387: [root@gatekeeper dovecot]# sudo su - vmail Last login: Wed Oct 14 16:15:48 SAST 2020 on pts/0 [vmail@gatekeeper ~]$ wc -c /var/lib/dovecot/sieve/vacation.svbin 530 /var/lib/dovecot/sieve/vacation.svbin Does dovecot-lda do anything odd with respect to group memberships? Regards, Graham —

2 1

Problem reading SSL key
by Tech Support 18 Oct '20

18 Oct '20

All; I'm trying to setup dovecot to use SSL, but I'm getting an error message in the logs. I'm getting the error imap-login: Fatal: Couldn't parse private ssl_key. I'm using a commercial cert so I know that the .crt and .key files themselves are not the problem. I have them configured like so: ssl_cert = </etc/pki/tls/certs/mail_acmewidgets_net.crt ssl_key = </etc/pki/tls/private/mail_acmewidgets_net.key The crt is mode 444 and the key is mode 400. Since the log is not giving any other information, I don't know what the problem is. Any insight at all would be greatly appreciated. Thanks; Frank

2 1

backup of namespace, is still looking at (touching?) other namespace?
by Marc Roos 17 Oct '20

17 Oct '20

When I am doing this: doveadm backup -f -n inbox -F /root/backup-accounts.txt tcp:mailxx.local:542 I am getting an error on the distributed storage, which I exactly did not wanted to be touched. doveadm(testaccount): Error: remote(mailxx.local:542): User initialization failed: Namespace 'Archive/': stat(/home/mail-archive/testaccount/Archive/mailboxes) failed: Permission denied (euid=xxx(testaccount) egid=xx(xxxxx) missing +x perm: /home/mail-archive, dir owned by 0:0 mode=0700) doveadm(testaccount): Error: remote(mailxx.local:542): dsync-server: User init failed doveadm(testaccount): Error: Failed to start remote dsync-server command: Remote exit_code=75

1 0

how to set smtp-client -> submission_relay_host for IPv4 only?
by PGNet Dev 16 Oct '20

16 Oct '20

In dovecot conf, for submission relay, I've config'd submission_relay_host = lan.example.com submission_relay_port = 465 hostname -- not IP -- must be used, to inform relay for cert verification match. Here, host lan.example.com lan.example.com has address 10.0.1.47 lan.example.com has IPv6 address fd80:25:01::47 The receiving smtp relay listens only on IPv4 -- no IPv6 service, telnet 10.0.1.47 465 Trying 10.0.1.47... Connected to 10.0.1.47. Escape character is '^]'. telnet -6 fd80:25:01::47 465 Trying fd80:25:01::47... telnet: connect to address fd80:25:01::47: Connection refused On the lan, all boxes are set, in "/etc/gai.conf", for IPv6 to take precedence over IPv4. On submission to dovecot submission port, after login/auth, dovecot smtp-client subsequently connects to the relay lan.example.com:465 IPv6 1st, & fails 2020-10-15 12:51:45 submission(mua(a)example.com)<8OJP+rqxuvho7Z95>: Error: smtp-client: conn lan.example.com:465 ([fd80:25:01::47]:465) [1]: connect(lan.example.com:465) failed: Connection refused then falls back to IPv4, and continues OK 2020-10-15 12:51:45 submission(mua(a)example.com)<8OJP+rqxuvho7Z95>: Info: Successfully relayed message: from=<test(a)remote.example.com>, size=84, id=LMe...Aw, nrcpt=1, reply=`247 2.0.0 Ok: queued as 4CC0KY1wXNzWf93' not fatal, but wasted effort, and noise in the logs. how/where do I configure (just) the dovecot smtp-client -> submission_relay_host to only connect IPv4?

3 4

Dovecot won't accept IMAP TLS 1 connections from older devices [SOLVED]
by Brian Martin 16 Oct '20

16 Oct '20

I've spent days scouring the Internet and trying various solutions on a problem with my Dovecot installation, so I thought I'd share what I learned in hopes of saving other people a lot of time. The dedicated Dovecot hands will know all of the following already. This is for those of us that have to cover a lot of bases. I upgraded my mail server from Ubuntu 18.04.1 to Ubuntu 20.04.1, and found that older Mac-books and iPads (and probably other devices) could no longer establish IMAP connections to Dovecot. Dovecot logged: SSL routines:tls_early_post_process_client_hello:unsupported protocol and TCP/IP traces showed that it dropped the connection after the client's initial HELLO. I tested what kinds of connections Dovecot would accept with (for example): openssl s_client -tls1_1 -connect localhost:993 # Test whether TLSv1.1 is accepted - received "unsupported protocol" message. Searching showed that Dovecot has a parameter "ssl_min_protocol", which is documented as defaulting to TLSv1. Nevertheless I explicitly set it to TLSv1 with no effect. This was a red herring. I spent a long time looking to see if Dovecot had a bug in handling this newish parameter, etc. Eventually I came across one posting regarding a web server, that told me the OpenSSL libraries that Dovecot and lots of other packages use has a single configuration file for the entire system. In Ubuntu 20.04 it defaults to requiring TLSv1.2 or above. Changing the configuration for OpenSSL affects everything on the system using the library. I changed the file, restarted Dovecot, and it immediately accepted TLSv1 connections. Obviously I'd prefer to maintain the improved security of TLSv1.2, but in my case it was better to continue providing mail service at a lower security level than to deny service to some users until they upgraded their personal devices. You'll need to make your on decision on that score. The file to change is (on Ubuntu, at least) /usr/lib/ssl/openssl.cnf. The change consists of adding a line of code in the initial section that invokes several new sections later: In the initial section I added: openssl_conf = default_conf Then at the bottom of the file I added: [default_conf] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] MinProtocol = TLSv1 CipherString = DEFAULT@SECLEVEL=1 There is an alternative approach that I have read of but not tested. Basically you can create a new file elsewhere with the customized content, and then set an environmental variable (OPENSSL_CONF) just before launching Dovecot that points to your new file. This way, only Dovecot is using downgraded security. Since my mail server is a dedicated system and I didn't want to muck with the Dovecot start-up environment, I didn't feel the need to go that route. So all my digging into why Dovecot wouldn't accept TLSv1 connections and how to change it were completely on the wrong path. It would be nice if Dovecot could log a message when its ssl_min_protocol is set lower than what OpenSSL will accept, but Dovecot may not be able to tell what OpenSSL is doing. In any case, those are the symptoms, the real problem, and how to fix it. Good luck, and thanks to Matt Caswell for posting the answer that I eventually found. Ref: https://askubuntu.com/questions/1233186/ubuntu-20-04-how-to-set-lower-ssl-s…

3 2

Auro expunge
by ＠lbutlr 15 Oct '20

15 Oct '20

When using autoexpunge = 14 days in, for example. The trash of junk folders, does that physically remove the messages from disk or simply mark them to be removed and some other action needs to be taken? I ask because my mail server crapped out today and I discovered a Junk folder with 490,000 messages in it, and the sa-spamd and mariadb processes died a horrible death. Haven't had time to track down what was going on, but there were definitely messages in that junk folder from 2019 (though, of course, they may have been added within the last 14 days, I can't verify that as my solution was to remove the folder and recreate a new empty maildir). -- I don't believe there's a power in the 'verse can stop Kaylee from bein' cheerful. Sometimes you just wanna duct-tape her mouth and dump her in the hold for a month.

5 5

RE: dovecot Digest, Vol 210, Issue 27
by webadmin＠exalt.com.au 15 Oct '20

15 Oct '20

I am investigating whether dovecot(https://github.com/dovecot/core/) handles case insensitive Message-ID headers as per RFC. I can't raise a support issue with cPanel team (https://tickets.cpanel.net/review/login.cgi) as that needs an paid account with them. There may be an issue with the CPANEL/WHM DKIM module. Is the source code online? Rob

3 2

How do I enable sieve trace debugging?
by Graham Leggett 14 Oct '20

14 Oct '20

Hi all, I want to enable trace debugging for sieve. Most specifically, I want to know what sieve scripts are running, and whether they’re doing anything. I cannot get anything other than dead silence from dovecot with respect to sieve. I have tried the same as asked in this question: https://unix.stackexchange.com/questions/550618/dovecot-sieve-trace-does-no… In my case, the config looks like this: ## TRACE DEBUGGING # Trace debugging provides detailed insight in the operations performed by # the Sieve script. These settings apply to both the LDA Sieve plugin and the # IMAPSIEVE plugin. # # WARNING: On a busy server, this functionality can quickly fill up the trace # directory with a lot of trace files. Enable this only temporarily and as # selective as possible. # The directory where trace files are written. Trace debugging is disabled if # this setting is not configured or if the directory does not exist. If the # path is relative or it starts with "~/" it is interpreted relative to the # current user's home directory. sieve_trace_dir = /tmp/sieve-trace # The verbosity level of the trace messages. Trace debugging is disabled if # this setting is not configured. Possible values are: # # "actions" - Only print executed action commands, like keep, # fileinto, reject and redirect. # "commands" - Print any executed command, excluding test commands. # "tests" - Print all executed commands and performed tests. # "matching" - Print all executed commands, performed tests and the # values matched in those tests. sieve_trace_level = actions,command,tests,matching # Enables highly verbose debugging messages that are usually only useful for # developers. sieve_trace_debug = yes This looks sensible, syslog would be a great place to log, but nothing related to sieve appears. [root@gatekeeper dovecot]# doveadm log find Looking for log files from /var/log Debug: /var/log/maillog Info: /var/log/maillog Warning: /var/log/maillog Error: /var/log/maillog Fatal: /var/log/maillog Regards, Graham —

3 3

Changing IMAP separator - does it break things?
by Victor Sudakov 14 Oct '20

14 Oct '20

Dear Colleagues, I am using Dovecot 2.3.4.1 with maildirs. Just found out that MacOS Mail clients cannot work with nested folders, presumably because the MacOS Mail does not understand "." as the IMAP separator. Other clients (ThunderBird, Sylpheed, mutt) work fine. Do you think I can change the hierarchy separator in the "inbox" namespace without breaking other clients and the mail layout on disk, losing mail etc? I don't want to break mail for 50 people just to please one Mac Mail user. The users are advanced developers actively using mail sorting rules, nested folders etc. My `doveconf -n` is here: https://termbin.com/w1wd -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/

5 20

Re: Fatal: setgid from userdb lookup fails with wrong gid
by J. de Meijer 14 Oct '20

14 Oct '20

Hi, Not sure if this is it, but I used to have the same error when I started with dovecot. Aki's response was the following (and solved my problem). ------------- Hi! You can't set service imap { service_count = 256 } if you are using multiple system UIDs. See https://wiki.dovecot.org/Services#imap.2C_pop3.2C_submission.2C_managesieve *service_count* can be changed from 1 if only a single UID is used for mail users. This is improves performance, but it's less secure, because bugs in code may leak email data from another user's earlier connection. Aki ----------- Regards, Jeroen > Hello all, > > I'm quite new as well to Dovecot, just installed it on a FreeBSD system with Postfix and Rspamd as side apps. Things are running semi-smoothly for all users but I do have quite a few errors in the logs : > > Oct 13 19:43:56 apollo dovecot[24478]: > imap(user1)<34412><zIeI9ZCxXDmsFhZG>: Fatal: setgid(1030(user1) from userdb lookup) failed with euid=1022(user4), gid=1022(user4), > egid=1022(user4): Operation not permitted (This binary should probably be called with process group set to 1030(user1) instead of 1022(user4)) Oct 13 19:43:59 apollo dovecot[24478]: > imap(user1)<37376><pPS79ZCx+kasFhZG>: Fatal: setgid(1030(user1) from userdb lookup) failed with euid=1124(user3), gid=1124(user3), > egid=1124(user3): Operation not permitted (This binary should probably be called with process group set to 1030(user1) instead of 1124(user3)) Oct 13 19:46:45 apollo dovecot[24478]: > imap(user2)<38858><3hOk/5CxVO1dBDTq>: Fatal: setgid(1136(user2) from userdb lookup) failed with euid=1038(user5), gid=1038(user5), > egid=1038(user5): Operation not permitted (This binary should probably be called with process group set to 1136(user2) instead of 1038(user5)) Oct 13 19:48:55 apollo dovecot[24478]: > imap(user3)<40607><jQtWB5GxHuwKAkQ2>: Fatal: setgid(1124(user3) from userdb lookup) failed with euid=1022(user4), gid=1022(user4), > egid=1022(user4): Operation not permitted (This binary should probably be called with process group set to 1124(user3) instead of 1022(user4)) > > There seems to be confusion. The logs are trying to be helpful but I can't quite process it. Could someone point me in the right direction ? > > system is used by about 60 users. > > Thanks, > > j. > > -- > > doveconf -n > # 2.3.11.3 (502c39af9): /usr/local/etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.11 (d71e0372) > # OS: FreeBSD 12.1-RELEASE-p10 amd64 > # Hostname: apollo.domain1.tld > auth_mechanisms = plain login cram-md5 > auth_username_format = %Ln > mail_location = maildir:~/Maildir > 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 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 = > type = private > } > passdb { > args = scheme=cram-md5 /usr/local/etc/dovecot/cram-md5.pwd > driver = passwd-file > } > plugin { > imapsieve_mailbox1_before = > file:/var/vmail/sieve/global/learn-spam.sieve > imapsieve_mailbox1_causes = COPY > imapsieve_mailbox1_name = Spam > imapsieve_mailbox2_before = > file:/var/vmail/sieve/global/learn-ham.sieve > imapsieve_mailbox2_causes = COPY > imapsieve_mailbox2_from = Spam > imapsieve_mailbox2_name = * > quota = maildir:User quota > quota_exceeded_message = Benutzer %u hat das Speichervolumen > Ã¼berschritten. / User %u has exhausted allowed storage space. > sieve = file:~/sieve;active=~/.dovecot.sieve > sieve_before = /var/vmail/sieve/global/spam-global.sieve > sieve_global_extensions = +vnd.dovecot.pipe > sieve_pipe_bin_dir = /usr/local/bin > sieve_plugins = sieve_imapsieve sieve_extprograms > } > postmaster_address = postmaster(a)apollo.domain1.tld > protocols = imap lmtp sieve > service auth { > client_limit = 3000 > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0666 > user = postfix > } > } > service imap-login { > service_count = 0 > } > service imap { > process_min_avail = 4 > service_count = 512 > vsz_limit = 1 G > } > service lmtp { > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0600 > user = postfix > } > vsz_limit = 1 G > } > ssl_cert = > </usr/local/etc/letsencrypt/live/apollo.domain1.tld/fullchain.pem ssl_cipher_list = > EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA ssl_dh = # hidden, use -P to show it > ssl_key = # hidden, use -P to show it > ssl_prefer_server_ciphers = yes > syslog_facility = local5 > userdb { > driver = passwd > } > protocol lda { > mail_plugins = sieve > } > protocol lmtp { > mail_plugins = quota sieve > postmaster_address = postmaster(a)domain1.tld > } > protocol imap { > mail_max_userip_connections = 100 > mail_plugins = " quota imap_quota imap_sieve" > } > local_name imap.domain2.tld { > ssl_cert = > </usr/local/etc/letsencrypt/live/mail.domain2.tld/fullchain.pem > ssl_key = # hidden, use -P to show it > } > local_name mail.domain2.tld { > ssl_cert = > </usr/local/etc/letsencrypt/live/mail.domain2.tld/fullchain.pem > ssl_key = # hidden, use -P to show it > } >

2 1

Re: zlib errors after upgrading to 2.3.11.3
by Robert Nowotny 14 Oct '20

14 Oct '20

On 9. Sep 2020, at 11.14, Robert Nowotny <rnowotny1966(a)gmail.com> wrote: Sep 3 08:33:25 lxc-imap dovecot: imap(mpaul)<48684><2/9E5mKuAezAqKjk>: Error: Mailbox Sent: UID=2171: read(zlib(/home/vmail/virtualmailboxes/mpaul/storage/m.119)) failed: read(/home/vmail/virtualmailboxes/mpaul/storage/m.119) failed: Broken pipe (FETCH BODY[]) Also this way you can see if the broken mail is actually xz or zstd or zlib. It would be nice to know if there are any zstd or zlib compressed mails that have problems. We did a lot of stress testing with zstd and also with xz, but haven't been able to reproduce any problems. It's also strange that it says taht the error is "Broken pipe" - that doesn't indicate that the mail is corrupted but that there is something more strange going on. So perhaps you don't actually have any mails written as corrupted, but Dovecot is just somehow having trouble reading the mails. I managed to reproduce this. The files aren't corrupted, it's just that reading is failing. The attached patch should fix the xz code and should make your files readable again. Yes, it works ! I switched now to "zstd" compression and currently re-compressing all user imap folders (one by one) Actually, with further testing it looks like the mails were written truncated. My patch simply hides the truncation when reading the mail. But it's anyway best that can be done about them. zstd also has a bug in writing compressed output, but it should always crash instead of writing broken output. We'll try to get fixes to these merged to git soon. currently I am re-compressing the mailboxes and so far i can see only one (1) Error, after about 120GB of recomresses emails : Sep 10 11:32:24 lxc-imap dovecot: imap(ebay)<37070><1aDvPvKus+/AqKjk>: Panic: file ostream.c: line 287 (o_stream_sendv_int): assertion failed: (!stream->blocking) Sep 10 11:32:24 lxc-imap dovecot: imap(ebay)<37070><1aDvPvKus+/AqKjk>: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(backtrace_append+0x41) [0x7f5b00de6da1] -> /usr/local/lib/dovecot/libdovecot.so.0(backtrace_get+0x22) [0x7f5b00de6ec2] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xfe5eb) [0x7f5b00df05eb] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xfe687) [0x7f5b00df0687] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x598e1) [0x7f5b00d4b8e1] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x5e2c1) [0x7f5b00d502c1] -> /usr/local/lib/dovecot/libdovecot.so.0(o_stream_sendv+0x32) [0x7f5b00e14a92] -> /usr/local/lib/dovecot/libdovecot.so.0(io_stream_copy+0x5a) [0x7f5b00e1535a] -> /usr/local/lib/dovecot/libdovecot.so.0(o_stream_send_istream+0x50) [0x7f5b00e15060] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_save_continue+0x2d) [0x7f5b00f9659d] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(dbox_save_continue+0x30) [0x7f5b00f3d3b0] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_save_continue+0x3e) [0x7f5b00f1a34e] -> dovecot/imap [ebay 192.168.168.228 APPEND](+0x13801) [0x55d6905bf801] -> dovecot/imap [ebay 192.168.168.228 APPEND](command_exec+0x6c) [0x55d6905ce3ec] -> dovecot/imap [ebay 192.168.168.228 APPEND](+0x12fdb) [0x55d6905befdb] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6d) [0x7f5b00e06ced] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x145) [0x7f5b00e08305] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x54) [0x7f5b00e06d94] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x48) [0x7f5b00e06f08] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x17) [0x7f5b00d7f8d7] -> dovecot/imap [ebay 192.168.168.228 APPEND](main+0x459) [0x55d6905bec99] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f5b00b0e0b3] -> dovecot/imap [ebay 192.168.168.228 APPEND](_start+0x2e) [0x55d6905bed2e] Sep 10 11:32:24 lxc-imap dovecot: imap-login: Panic: epoll_ctl(del, 21) failed: Bad file descriptor Sep 10 11:32:24 lxc-imap dovecot: imap(ebay)<37070><1aDvPvKus+/AqKjk>: Fatal: master: service(imap): child 37070 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) until now I only have one broken mailbox, I need to repair (I will try that later, just finish all the other users before): Sep 10 12:13:13 lxc-imap dovecot: imap(mtrenner)<41872><KVTf0PKu7+7AqKi0>: Error: lzma.read(/home/vmail/virtualmailboxes/mtrenner/storage/m.349): corrupted data at 3763912 Sep 10 12:13:13 lxc-imap dovecot: imap(mtrenner)<41872><KVTf0PKu7+7AqKi0>: Error: Mailbox Sent: UID=1480: read(zlib(/home/vmail/virtualmailboxes/mtrenner/storage/m.349)) failed: read(/home/vmail/virtualmailboxes/mtrenner/storage/m.349) failed: lzma.read(/home/vmail/virtualmailboxes/mtrenner/storage/m.349): corrupted data at 3763912 (FETCH BODY[]) > zstd also has a bug in writing compressed output, but it should always crash instead of writing broken output. > We'll try to get fixes to these merged to git soon. Uh-Oh, that would be good ... pls notify ! how such thing can slip through the tests ? I just can not remember, the last error with compression was like 10 years ago (dont know if it was me who reported that) However, thank You for Your fast response and taking care !!! Robert

3 2

Spam learning for rspamd
by Dan Egli 14 Oct '20

14 Oct '20

I'm quite new to Dovecot, so forgive me if this is a simple question. I've got rspamd running, and it's rewriting the subject of many messages as spam even when they are not. I've moved things out of the spam folder, which I was under the impression would teach rspamd since I've connected a sieve script that is supposed to call rspamd's learning tool, but nothing is happening. I'm really at a loss as to where to even begin searching for an answer, so any help is appreciated! -- Dan Egli On my Test server

4 5

Procmail with Dovecot
by Dan Egli 13 Oct '20

13 Oct '20

Hey folks, here's a question. I want to enable procmail for the users so that they can have their incoming messages sorted info various folders and such regardless of MUA access or web access. I know I can set procmail to deliver to a maildir, but wouldn't that screw up dovecot's indexes? If it would, what can I do to ensure that the indexes stay correct? Thanks! -- Dan Egli On my Test server

5 5

Fatal: setgid from userdb lookup fails with wrong gid
by Julien Beauviala 13 Oct '20

13 Oct '20

Hello all, I'm quite new as well to Dovecot, just installed it on a FreeBSD system with Postfix and Rspamd as side apps. Things are running semi-smoothly for all users but I do have quite a few errors in the logs : Oct 13 19:43:56 apollo dovecot[24478]: imap(user1)<34412><zIeI9ZCxXDmsFhZG>: Fatal: setgid(1030(user1) from userdb lookup) failed with euid=1022(user4), gid=1022(user4), egid=1022(user4): Operation not permitted (This binary should probably be called with process group set to 1030(user1) instead of 1022(user4)) Oct 13 19:43:59 apollo dovecot[24478]: imap(user1)<37376><pPS79ZCx+kasFhZG>: Fatal: setgid(1030(user1) from userdb lookup) failed with euid=1124(user3), gid=1124(user3), egid=1124(user3): Operation not permitted (This binary should probably be called with process group set to 1030(user1) instead of 1124(user3)) Oct 13 19:46:45 apollo dovecot[24478]: imap(user2)<38858><3hOk/5CxVO1dBDTq>: Fatal: setgid(1136(user2) from userdb lookup) failed with euid=1038(user5), gid=1038(user5), egid=1038(user5): Operation not permitted (This binary should probably be called with process group set to 1136(user2) instead of 1038(user5)) Oct 13 19:48:55 apollo dovecot[24478]: imap(user3)<40607><jQtWB5GxHuwKAkQ2>: Fatal: setgid(1124(user3) from userdb lookup) failed with euid=1022(user4), gid=1022(user4), egid=1022(user4): Operation not permitted (This binary should probably be called with process group set to 1124(user3) instead of 1022(user4)) There seems to be confusion. The logs are trying to be helpful but I can't quite process it. Could someone point me in the right direction ? system is used by about 60 users. Thanks, j. -- doveconf -n # 2.3.11.3 (502c39af9): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (d71e0372) # OS: FreeBSD 12.1-RELEASE-p10 amd64 # Hostname: apollo.domain1.tld auth_mechanisms = plain login cram-md5 auth_username_format = %Ln mail_location = maildir:~/Maildir 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 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 = type = private } passdb { args = scheme=cram-md5 /usr/local/etc/dovecot/cram-md5.pwd driver = passwd-file } plugin { imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * quota = maildir:User quota quota_exceeded_message = Benutzer %u hat das Speichervolumen überschritten. / User %u has exhausted allowed storage space. sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /usr/local/bin sieve_plugins = sieve_imapsieve sieve_extprograms } postmaster_address = postmaster(a)apollo.domain1.tld protocols = imap lmtp sieve service auth { client_limit = 3000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { service_count = 0 } service imap { process_min_avail = 4 service_count = 512 vsz_limit = 1 G } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } vsz_limit = 1 G } ssl_cert = </usr/local/etc/letsencrypt/live/apollo.domain1.tld/fullchain.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes syslog_facility = local5 userdb { driver = passwd } protocol lda { mail_plugins = sieve } protocol lmtp { mail_plugins = quota sieve postmaster_address = postmaster(a)domain1.tld } protocol imap { mail_max_userip_connections = 100 mail_plugins = " quota imap_quota imap_sieve" } local_name imap.domain2.tld { ssl_cert = </usr/local/etc/letsencrypt/live/mail.domain2.tld/fullchain.pem ssl_key = # hidden, use -P to show it } local_name mail.domain2.tld { ssl_cert = </usr/local/etc/letsencrypt/live/mail.domain2.tld/fullchain.pem ssl_key = # hidden, use -P to show it }

1 0

Re: LMTP Authentication Error
by David Morsberger 13 Oct '20

13 Oct '20

On 2020-10-07 12:43, Alexander Dalloz wrote: > Am 07.10.2020 um 18:20 schrieb david(a)mmpcrofton.com: >> Any ideas on how to resolve the Userdb connect/lookup problem? My users are pinging me on Sieve support. >> Thanks, >> David > Provide a full output of "doveconf -n"? > Alexander Alexandar, Thanks and here you go. # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-48-generic x86_64 Ubuntu 20.04.1 LTS # Hostname: mmp-mail.mmpcrofton.com base_dir = /var/run/dovecot/ first_valid_uid = 150 login_greeting = Dovecot ready. mail_gid = 150 mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail mail_uid = 150 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 namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = file:/home/mail/rules/%u/;active=/home/mail/rules/%u/.dovecot.sieve sieve_dir = /home/mail/rules/%u } protocols = " imap lmtp sieve pop3 sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/letsencrypt/live/imap.mmpcrofton.com/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " sieve" postmaster_address = david(a)mmpcrofton.com } protocol imap { mail_max_userip_connections = 50 }

2 4

Move older messages to Old folder after a bunch of changes (sql + other stuff)
by Chris Bennett 13 Oct '20

13 Oct '20

I'm starting to get things better done now. Moved to all virtual users over IMAP. Using a SQL database for users/passwords. Setting up folders working properly with neomutt. Right now, that leaves me with just new mail in the INBOX, and other folders. I have a bunch of old mail in each users Maildirs in their real home folders. Right now, I'd like to move all the old mail into a folder (doesn't really matter what it's called). Right now is actually a perfect time to do this by good luck in timing. How should I go about creating a new folder for those messages and then adding the old mail from system user home Maildir folders to the virtual users folders I'm using? Thanks for any help, Chris Bennett

1 0

DKIM fail if WHM adds Message-ID, should be Message-Id
by Robert Martin 13 Oct '20

13 Oct '20

I created a client library to send emails for a webapp. After connecting to the SMTP server with credential setup in CPANEL, and then do NOT add Message-Id header, the DKIM signature 'h' record created by dovecot/WHM is wrong, and a Message-ID (with a capital D) header is added, invalidating the generated DKIM signature value. This causes outlook, yahoo, gmail and other email recipients to add 'dkim:fail' to the message, and thus relegate it to junk or spam. The work around is to add to the message a Message-Id with a little 'd' header. Then the SMTP server processes the email with the correct generated DKIM, correct DKIM 'h' record and does not add a Message-ID header. My SMTP hosting providers that run the WHM/dovecot/CPANEL software are refusing to raise this as a bug and have requested that I do it. Regards Robert

4 3

Preparing for replication: dsync-local(testaccount): Panic: file mbox-lock.c
by Marc Roos 12 Oct '20

12 Oct '20

I am preparing a bit for setting up replication. However when I manually try to dsync an account, the first time I execute this[1] command it seems to be ok. The 2nd time I am getting this error[2]. If I add -1 (one way syncing) the error disappears. Does this mean I will have problems with setting up replication between these two servers? [1] [@ ~]# doveadm sync -n inbox -u testaccount tcp:mail.local:542 [2] [@ ~]# doveadm sync -n inbox -u testaccount tcp:mail.local:542 dsync-local(testaccount): Panic: file mbox-lock.c: line 799 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) dsync-local(testaccount): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xa192e) [0x7fd4f827992e] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fd4f827999a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd4f8209257] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mbox_lock+0xef) [0x7fd4f858feef] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mbox_save_begin+0x658) [0x7fd4f8591958] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_save_begin+0x83) [0x7fd4f855a573] -> doveadm(+0x4a6a3) [0x55e5ae8276a3] -> doveadm(dsync_mailbox_import_mail+0xca) [0x55e5ae82a9fa] -> doveadm(dsync_brain_sync_mails+0xb3) [0x55e5ae824963] -> doveadm(dsync_brain_run+0x551) [0x55e5ae820551] -> doveadm(+0x438e0) [0x55e5ae8208e0] -> doveadm(+0x5899f) [0x55e5ae83599f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7fd4f828f672] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7fd4f8290d5f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7fd4f828f70c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd4f828f8c8] -> doveadm(+0x297c9) [0x55e5ae8067c9] -> doveadm(+0x2bdcc) [0x55e5ae808dcc] -> doveadm(+0x2c9ca) [0x55e5ae8099ca] -> doveadm(doveadm_mail_try_run+0x215) [0x55e5ae80a325] -> doveadm(main+0x46a) [0x55e5ae7f949a] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fd4f7e2c555] -> doveadm(+0x1c605) [0x55e5ae7f9605] Aborted CentOS Linux release 7.8.2003 (Core) dovecot-pigeonhole-2.2.36-6.el7_8.1.x86_64 dovecot-2.2.36-6.el7_8.1.x86_64

2 2

Doveadm-Sync for sieve / control
by Marc Roos 12 Oct '20

12 Oct '20

How to dsync sieve rules and maybe other necessary files like in control?

1 0

DKIM fail if WHM adds Message-ID, should be Message-Id
by webadmin＠exalt.com.au 12 Oct '20

12 Oct '20

I created a client library to send emails for a webapp. When the client library makes a connection to the SMTP server, and then do NOT add Message-Id header, Message-ID (with a capital D) header is added, and the SMTP server adds a incorrect DKIM-Signature record 'h' part, invalidating the generated DKIM signature value. This causes outlook, yahoo, gmail and other email recipients to add 'dkim:fail' to the message which pushes it into junk/spam folder. The work around is to add to the message a Message-Id with a little ‘d’ header. Then the SMTP server processes the email with the correct DKIM-Signature, correct DKIM ‘h’ part and does not add a Message-ID header. Message-ID fails DKIM, Message-Id is better by OzBob · Pull Request #142 · dovecot/core (github.com) https://github.com/dovecot/core/pull/142 Regards Robert

2 1

where to specify dovecot v2.3.11.3 SSL configs for fts solr indexer/backend connection?
by PGNet Dev 12 Oct '20

12 Oct '20

I'm running. dovecot --version 2.3.11.3 (502c39af9) solr -version 8.6.3 solr's configured to use SSL. dovecot correctly uses SSL for transport fts_solr = url=https://solr.example.com:8984/solr/dovecot/ adding solr-side SSL client auth, - SOLR_SSL_NEED_CLIENT_AUTH=false + SOLR_SSL_NEED_CLIENT_AUTH=need I need to specify client cert for dovecot to present -- specific to the fts indexer connection. It apparently does not use dovecot's general/global SSL configs; that^ toggle immediately breaks MUA-originated search, reporting only 2020-10-11 18:23:30 imap(myuser@example)<oKpmJW+xQKCsHgsH>: Error: fts_solr: Lookup failed: 401 Unauthorized All other protocols SSL configs certainly work, and can be individually configured with specific key/crt pairs. Where do I config dovecot specifically for the search backend? I.e., where do I assign the ssl key/cert for dovecot to present as client to the solr server ?

1 0

Providers running dovecot?
by Olivier Cailloux 11 Oct '20

11 Oct '20

Dear list, I am looking for providers of free e-mail addresses known to run Dovecot (or a variant thereof) for IMAP access. I need only a few MB storage space and no particular features beyond SMTP and IMAP. The reason I ask is that Dovecot is known to implement the IMAP spec quite respectfully, and I am writing a software which uses IMAP search (so I would suggest my users to register an e-mail to a provider implementing correctly the IMAP Search specifications, to reduce the probability of bugs). (More details here: https://www.webhostingtalk.com/showthread.php?t=1821627.) Do you know of any such provider? -- Olivier

7 12

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