- dovecot - dovecot.org

logging verbosity
by Fourhundred Thecat 05 Feb '21

05 Feb '21

Hello, I get lots of these messages in the log: dovecot: imap-login: Login: user(a)1.2.3.4, TLSv1.3 with .. dovecot: imap(user)<10889><glzsCIi6AMbUGQtL>: Disconnected for inactivity ... dovecot: imap(user)<10887><vzjQB4i6/MXUGQtL>: Logged out ... when user clicks on folder in Thunderbird, or sometimes even when the Thunderbird window is in focus (without clicking anything). Anyway, how can I suppress these info messages, while keeping the important ones, such as auth problems? I am using Dovecot v2.3.4.1 with 10-logging.conf with default values. I see there is this line: # Log unsuccessful authentication attempts and the reasons why they failed. auth_verbose = yes I definitely want to keep logging unsuccessful auth, but how can I suppress the verbose rest? and lastly, can these settings be set per-user? Can I suppress verbose for user 'bob' but keep for others? thanks,

5 5

Feb 03 13:27:19 aggregator: Fatal: chroot(/var/lib/dovecot/run/dovecot/.) failed: Operation not permitted
by Jörg Faudin Schulz 05 Feb '21

05 Feb '21

I'm trying to set up dsync replication. This seems to work partial - complete replica does work (delete the mailboxes on target, and they'll get filled again). But, changes don't seem to get populated on the replica server; I get the msg Feb 03 13:27:19 aggregator: Fatal: chroot(/var/lib/dovecot/run/dovecot/.) failed: Operation not permitted dovecot conf: # Pigeonhole version 0.5.13 (cdd19fe) # OS: Linux 4.4.0-193-generic x86_64 # Hostname: imap.faudin.de auth_mechanisms = plain login default_internal_group = root default_internal_user = vmail default_login_user = vmail doveadm_password = # hidden, use -P to show it doveadm_port = 2443 first_valid_gid = 0 imapc_features = rfc822.size fetch-headers imapc_port = 1143 imapc_ssl = starttls imapc_ssl_verify = no imapc_user = %u lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /dev/stderr mail_plugins = " notify replication" mail_prefetch_count = 20 mail_privileged_group = root 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 = create special_use = \Drafts } mailbox Junk { auto = create special_use = \Junk } mailbox Sent { auto = create special_use = \Sent } mailbox "Sent Messages" { auto = create special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { mail_replica = tcp:m.datilo.de:2443 postmaster = isomne valid address replication_sync_timeout = 2 sieve = file:/var/vmail/sieve/scripts/%u/sieve;active=/var/vmail/sieve/scripts/%u/.dovecot.sieve sieve_after = /etc/dovecot/sieve/sieve-after sieve_before = /etc/dovecot/sieve/sieve-before sieve_default = /etc/dovecot/sieve/default.sieve sieve_dir = /var/vmail/sieve/scripts/%u sieve_global_dir = /var/vmail/sieve } protocols = imap lmtp sieve service aggregator { unix_listener replication-notify { group = root mode = 0666 user = vmail } } service anvil { chroot = } service auth { chroot = unix_listener auth-client { mode = 0660 user = vmail } } service config { unix_listener config { group = root user = vmail } } service doveadm { group = root inet_listener { port = 2443 } user = vmail } service imap-login { chroot = inet_listener imap { port = 1143 } inet_listener imaps { port = 1993 ssl = yes } } service lmtp { chroot = inet_listener lmtp { port = 2525 } } service managesieve-login { chroot = inet_listener sieve { port = 4190 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = root mode = 0600 user = vmail } } ssl = required ssl_cert = </run/secrets/letsencrypt-fullchain ssl_cipher_list = ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH:!SSLv2:!TLS1.0 ssl_client_ca_file = /var/run/secrets/letsencrypt-fullchain ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes submission_host = exim-int-mailout:1587 userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = " notify replication sieve" } protocol lda { mail_plugins = " notify replication sieve" }

4 3

Several users, same mailbox
by Adrian 04 Feb '21

04 Feb '21

Hello, I have had Dovecot set up to use PAM authentication, as my current users all have system accounts on Debian. I've just moved over to passwdfile authentication, because I want to add new users who won't have logins on the system. This is working fine with my existing users. Now, the problem is that I want the new users to share the SAME (Maildir) 'mailbox'. Currently 10-mail.conf contains mail_location = maildir:/var/mail/%u:LAYOUT=fs so this needs to be overridden, or I need some new way of mapping users to mail locations. I could probably do it with symlinks from /var/mail/newuser to /var/mail/mail-location but there may be a better way to do it than that. I'd like it to be in a file, not needing mySQL or other database. Lastly, are there any implications for locking? These will be used rarely but if a second user logs in for the same mailbox they should get a lock error. dovecot -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-11-amd64 x86_64 Debian 10.7 ext4 # Hostname: example.com disable_plaintext_auth = no mail_location = maildir:/var/mail/%u:LAYOUT=fs Thanks in advance

2 1

Restarting indexing?
by Philip Warner 04 Feb '21

04 Feb '21

Hi, I have about 80GB of mail to index using Dovecot 2.3.4.1 and xapian 1.4.11 FTS. After about 18 hours I had to reboot the server for an unrelated reason (it was perhaps a quarter of the way through indexing). After reboot, the indexing did not restart, and I could find no way to restart it other than via the ‘doveadm index’ command, which I have now done, with the result that the indexing has restarted from scratch. Is there a way to coax it to restart from where it left off, in case I need another reboot? Sent from Mail for Windows 10

1 0

lmtp warning flooding logfile
by Michael Ruiz 03 Feb '21

03 Feb '21

Hi all, Checking my dovecot log files, I am seeing a huge flood of the following kind of message over and over. I'm not sure how I can get this to stop. Is there something wrong with my configuration? Regards, Michael dovecot[106888]: lmtp(572901): Warning: Event 0x55ee2285bd30 leaked (parent=(nil)): lmtp-client.c:173: 1 Time(s) dovecot[106888]: lmtp(572901): Warning: Event 0x55ee228774e0 leaked (parent=0x55ee228772d0): mail-storage-service.c:1336: 1 Time(s) dovecot[106888]: lmtp(572901): Warning: Event 0x55ee22877ef0 leaked (parent=0x55ee228711c0): mail-storage-service.c:1336: 1 Time(s) dovecot[106888]: lmtp(572901): Warning: Event 0x55ee2287b3b0 leaked (parent=0x55ee22856e00): smtp-server-transaction.c:58: 1 Time(s) dovecot[106888]: lmtp(572901): Warning: Event 0x55ee2287d5f0 leaked (parent=0x55ee2287db10): smtp-server-recipient.c:38: 1 Time(s) dovecot[106888]: lmtp(572901): Warning: Event 0x55ee2287db10 leaked (parent=0x55ee22856e00): smtp-server-transaction.c:58: 1 Time(s) dovecot[106888]: lmtp(572901): Warning: Event 0x55ee22883700 leaked (parent=0x55ee228877e0): smtp-server-recipient.c:38: 1 Time(s) dovecot[106888]: lmtp(572901): Warning: Event 0x55ee22883910 leaked

1 0

Custom quota exeed message
by rudolf＠padaru.de 03 Feb '21

03 Feb '21

Hey there, i need some help with custom quota messages with dovecot and postfix. The quota setup is clear and easy, now i want to manipulate the exceed message, which is generated, if the mailbox is full. Now i got something like that Your message to <user(a)my.server.com> was automatically discarded: Quota exceeded (mailbox for user is full) The first line so i think is generated from postfix and cant be edit or? The second line is generatet from dovecot and i can manipulate there with the quota_exceeded_message variable. My problem is, that the sender cant see the mail-adress where he originally send the mail. Because the user is an local user on my server. I need somethin like that: Your message to <peter.schmidt(a)schmidt.com> was automatically discarded: Quota exceeded (mailbox for user is full) Is there an way to manipulate the first line of answer? Ori s there an way, that i can run a custom script in the quota_exceeded_message var? With the latter variant i would be able to create something like: Your message to <user(a)my.server.com> was automatically discarded: Quota exceeded (mailbox for user <peter.schmidt(a)schmidt.com> is full) But configurations like quota_exceeded_message = script /my/script.sh wont execute the script. Does anybody have an idea? Mit freundlichen Grüßen Yours sincerely Pascal Rudolf

2 6

error getting messages from mdbox_deleted
by Marc Roos 03 Feb '21

03 Feb '21

I was trying to list messages deleted with doveadm -f flow -o mail_location=mdbox_deleted:/home/mail/xxxxxxx /mdbox fetch -u xxxxxxx "mailbox date.saved guid" ALL And getting this error. What is this about? doveadm(xxxxxxx): Panic: file mdbox-map.c: line 1494 (mdbox_map_get_uid_validity): assertion failed: (map->view != NULL) doveadm(xxxxxxx): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xa192e) [0x7f854625592e] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f854625599a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f85461e5257] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x61830) [0x7f854654c830] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_update_header+0xa0) [0x7f8546551110] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x5d698) [0x7f8546548698] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x5d7e0) [0x7f85465487e0] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) [0x7f85465372d4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7f8546537377] -> doveadm(doveadm_mail_iter_init+0x98) [0x55b4cd34c118] -> doveadm(+0x305b1) [0x55b4cd34a5b1] -> doveadm(+0x2bdcc) [0x55b4cd345dcc] -> doveadm(+0x2c9ca) [0x55b4cd3469ca] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x233) [0x55b4cd347823] -> doveadm(doveadm_cmd_run_ver2+0x50c) [0x55b4cd357fac] -> doveadm(doveadm_cmd_try_run_ver2+0x37) [0x55b4cd358047] -> doveadm(main+0x1e4) [0x55b4cd336214] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f8545e08555] -> doveadm(+0x1c605) [0x55b4cd336605] Aborted

3 3

how to dovecot import to folder/, not folder/INBOX
by didar 02 Feb '21

02 Feb '21

Hi, I am trying to import old Gmail mails from a maildir source into dovecot folder. chowm -R vmail:vmail /tmp/batch-1234 doveadm import -u gmail maildir:/tmp/batch-1234 2011 all This works, but it imports the emails into "2011/INBOX" rather just into "2011". Since, the "gmail" user account has maildir storage itself, I rename the "%h/.2011.INBOX" to "%h/.2011" manually and it seems to be working. I am wondering if there is another cleaner way to do it? Maybe import into default INBOX and use "doveadm move" instead? Here is my passdb file: (this is a testing setup inside a VM in my laptop) didar:{plain}e5d903c1615cdcd9c3d088ec2cb71b11927f7650:::: jamir:{plain}9ffeba7706846ed6be4e6e52bcc7afd792330874:::: chaitali:{plain}09ce7f54c7fee999a27967b741dc2e5f3950e7e8:::: rajesh:{plain}308059d2078ba123c435ebf7d0f20d8f137330cf:::: samim:{plain}23b82f0b10a802d25f308960c6071b151e3c37b6:::: monibul:{plain}8da4d1ae5e520ff8fadd415cfbfbafc8fcebb367:::: owasim:{plain}7ef9cf46165c4729e09fc142432cd892e3365c44:::: office:{PBKDF2}$1$9b5a900650285343$5000$1d041a5a6caea807e26b8ff4b41e5389bb4b4427::::/opt/mailstore/common/.Office::userdb_mail=maildir:~/ banking:{PBKDF2}$1$429b69dc44c46b33$5000$25a4b4c106c3fa69a6890253aa9163b66f013d48::::/opt/mailstore/common/.Banking::userdb_mail=maildir:~/ gmail:{PBKDF2}$1$4fadc2241bf79ee5$5000$6b6db95f72fbe2d9dcd311fdad6f614302e98da7::::/opt/mailstore/common/.Gmail::userdb_mail=maildir:~/ automail:{PBKDF2}$1$549cf6f14ab5ceb0$5000$a18fe676ca716148ab1ba75f225044a960420bbf::::/opt/mailstore/common/.Automail::userdb_mail=maildir:~/ Here is my dovecot.conf: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-13-amd64 x86_64 Debian 10.7 ext4 # Hostname: dovecot.vbox.lan auth_mechanisms = plain login info_log_path = /var/log/dovecot-info.log listen = 10.0.2.90 log_path = /var/log/dovecot.log mail_attachment_dir = /opt/mailstore/attachments mail_location = mdbox:/opt/mailstore/mdboxes/%u mail_plugins = acl namespace { list = children location = maildir:/opt/mailstore/common:INDEXPVT=~/.common prefix = Common/ separator = / subscriptions = no type = public } 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 Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/dai/passwd-imapauth driver = passwd-file } plugin { acl = vfile:/etc/dovecot/dai/global-acl } protocols = imap lmtp service imap-login { inet_listener imap { address = 127.0.0.1 } } service imap { process_limit = 50 } service lmtp { inet_listener lmtp { address = 10.0.2.90 port = 24 } user = vmail } ssl_cert = </etc/dovecot/dai/dai-dovecot.cert ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dai/passwd-imapauth default_fields = uid=vmail gid=vmail home=/opt/mailstore/mdboxes/%u driver = passwd-file } protocol imap { mail_max_userip_connections = 2 mail_plugins = acl imap_acl } protocol lmtp { auth_username_format = %n } -- It's all in the mind, ya know.

2 1

Obtaining the IMAP GUID from a sieve script
by Ron Garret 02 Feb '21

02 Feb '21

Is there any way to obtain the IMAP GUiD of a message that is being processed by a sieve script? I’m writing a filter that needs to to keep track of message identities as they are moved around between folders. I could add my own id header, but I’d rather not have to reinvent that wheel. Thanks, rg

6 11

Dovecot and mutt
by ＠lbutlr 02 Feb '21

02 Feb '21

I have a user who is unable to use mutt to login. I tested and sent a muttrc that worked for me and all he needed to do was put in his username and password. Which failed. After some back and forth, I figured out that his password contains a '$' and a '[' in it, and it seems like one of, or both, of these characters may be the issue. Is that expected? The account and password work properly via iOS and macOS mail, so the issue does't appear to be dovecot, but I find it very odd that mutt would have a glaring issue like this, so I am wondering if there is something else that I need to do. Mutt 2.0.4 (2020-12-30) The configuration looks like this: # Imap settings set imap_user = "user(a)example.com" set imap_pass = "lasH-hds[er$asd" # Not a real password # Smtp settings set smtp_url = "smtps://mail.covisp.net:587" set smtp_pass = "lasHhds[er$asd" # Remote mail folders set folder = "imaps://mail.covisp.net:993" set spoolfile = "+INBOX" set postponed = "+/Drafts" set record = "+/Sent Mail" set trash = "+/Trash" --

10 14

Master user password mismatch
by Gregory Sloop 01 Feb '21

01 Feb '21

Trying to get master users working. I'm not sure what info would be best, but here's the detail I have now, in trying to get it working. Setup the master user file, and enabled master users in the conf files. Created the master user file and user/password hash. Turned on authentication debug. When I try something like: telnet localhost 143 and then supply the master user login - kind of like this: 1 login joeb*jb-master somepassword I get this in the logs. (Some obfuscation done.) --- dovecot: auth: Debug: auth client connected (pid=24985) dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=MM6QC9a5SIYAAAAAAAAAAAAAAAAAAAAB#011lip=::1#011rip=::1#011lport=143#011rport=34376#011resp=<hidden> dovecot: auth: Debug: passwd-file(jb-master,::1,master,<MM6QC9a5SIYAAAAAAAAAAAAAAAAAAAAB>): Master user lookup for login: joeb dovecot: auth: Debug: passwd-file(jb-master,::1,master,<MM6QC9a5SIYAAAAAAAAAAAAAAAAAAAAB>): lookup: user=jb-master file=/etc/dovecot/masterusers-test dovecot: auth: passwd-file(jb-master,::1,master,<MM6QC9a5SIYAAAAAAAAAAAAAAAAAAAAB>): Password mismatch dovecot: auth: Debug: client passdb out: FAIL#0111#011user=jb-master --- Yet I can use htpasswd -b -c -s /etc/dovecot/masterusers-test jb-master somepassword And this succeeds. (I created the masterusers-test file with httpasswd) So, I must have the password right, but dovecot is till failing the auth, claiming a bad password. How do I go about getting more detail so I can determine what's wrong? TIA -Greg

3 4

Unknown euid and egid, wrong mail directory
by Michael Agbaglo 01 Feb '21

01 Feb '21

Hi! Trying to set up dovecot for local accounts and virtual users, sending test mail fails: dovecot sees a permission problem in /home but the mail should go to /srv/mail/example.net/alice. "euid=1001(<unknown>) egid=1001(<unknown>)" 1001 doesn't not exist in /etc/passwd - Where does it come from? M. root@broccoli:~# doveconf -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-65-generic x86_64 Ubuntu 20.04.2 LTS # Hostname: broccoli.example.net mail_home = /srv/mail/%d/%n mail_location = maildir:~/Maildir mail_privileged_group = mail namespace { list = children location = maildir:%%h/Maildir:INDEXPVT=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = " imap lmtp" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/ssl/certs/ssl-cert-snakeoil.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = uid=vmail gid=vmail home=/srv/mail/%d/%n driver = static } root@broccoli:~# id postfix uid=116(postfix) gid=124(postfix) groups=124(postfix) root@broccoli:~# id dovecot uid=114(dovecot) gid=122(dovecot) groups=122(dovecot) root@broccoli:~# sendmail alice(a)example.net < /etc/issue.net root@broccoli:~# tail /var/log/mail.log Jan 30 21:31:47 broccoli postfix/pickup[4067]: 22AE117AA82: uid=0 from=<root> Jan 30 21:31:47 broccoli postfix/cleanup[35091]: 22AE117AA82: message-id=<20210130203147.22AE117AA82(a)broccoli.example.net> Jan 30 21:31:47 broccoli postfix/qmgr[854]: 22AE117AA82: from=<root(a)broccoli.example.net>, size=335, nrcpt=1 (queue active) Jan 30 21:31:47 broccoli dovecot: lmtp(35094): Connect from local Jan 30 21:31:47 broccoli dovecot: lmtp(alice(a)example.net)<35094><xGMOCjPCFWAWiQAAfCPMuA>: Error: mkdir(/home/alice/Maildir) failed: Permission denied (euid=1001(<unknown>) egid=1001(<unknown>) missing +w perm: /home, dir owned by 0:0 mode=0755) Jan 30 21:31:47 broccoli dovecot: lmtp(alice(a)example.net)<35094><xGMOCjPCFWAWiQAAfCPMuA>: Error: mkdir(/home/alice/Maildir) failed: Permission denied (euid=1001(<unknown>) egid=1001(<unknown>) missing +w perm: /home, dir owned by 0:0 mode=0755) Jan 30 21:31:47 broccoli dovecot: lmtp(alice(a)example.net)<35094><xGMOCjPCFWAWiQAAfCPMuA>: Error: lmtp-server: conn unix:pid=35093,uid=116 [1]: rcpt alice(a)example.net: Mailbox INBOX: Failed to autocreate mailbox: Internal error occurred. Refer to server log for more information. [2021-01-30 21:31:47] Jan 30 21:31:47 broccoli dovecot: lmtp(alice(a)example.net)<35094><xGMOCjPCFWAWiQAAfCPMuA>: msgid=<20210130203147.22AE117AA82(a)broccoli.example.net>: save failed to open mailbox INBOX: Mailbox INBOX: Failed to autocreate mailbox: Internal error occurred. Refer to server log for more information. [2021-01-30 21:31:47] Jan 30 21:31:47 broccoli dovecot: lmtp(35094): Disconnect from local: Client has quit the connection (state=READY) Jan 30 21:31:47 broccoli postfix/lmtp[35093]: 22AE117AA82: to=<alice(a)example.net>, relay=broccoli.example.net[private/dovecot-lmtp], delay=0.07, delays=0.04/0.01/0/0.02, dsn=4.2.0, status=deferred (host broccoli.example.net[private/dovecot-lmtp] said: 451 4.2.0 <alice(a)example.net> Internal error occurred. Refer to server log for more information. [2021-01-30 21:31:47] (in reply to end of DATA command))

3 3

Dovecot Gmail OAuth2.0 Setting Question
by 福田泰葵 01 Feb '21

01 Feb '21

Dear Sir or Madam Unable to build OAuth2.0 authentication to Gmail using dovecot as proxy. I have a question about how to use dovecot as a proxy to perform OAuth 2.0 authentication to Gmail using a mail client. 1. Is the following all I need to do to authenticate to Gmail using dovecot as a proxy? - passdb passdb { driver = oauth2 mechanisms = oauthbearer xoauth2 args = /etc/dovecot/dovecot-oauth2.token.conf.ext } passdb { driver = oauth2 mechanisms = plain login args = /etc/dovecot/dovecot-oauth2.plain.conf.ext } - create dovecot-oauth2.token.conf.ext and dovecot-oauth2.plain.conf.ext - create gmail service account api 2. grant_url in dovecot-oauth2.token.conf.ext and dovecot-oauth2.plain.conf.ext is URL for obtaining a Google access token for a web server that I have built myself? 3. I use a Gmail service account, so I don’t need a client ID and secret ID, right? 4. Do I set introspection_url to the URL of my own web server with the access token used for authentication to Google as the response? 5. The documentation says “pass_attrs = host=127.0.0.1”, but if you are authenticating to Gmail, I should use “pass_attrs = proxy=y host=%{if;%s;eq;imap;imap.gmail.com;%{if;%s;eq;pop3;smtp .gmail.com;pop.gmail.com}} port=%{if;%s;eq;imap;993;%{if;%s;eq;pop3;587;465}} proxy_mech=xoauth2 pass=%{oauth2:access_token} user=%{oauth2:email oauth2:email}”? 6. What is the difference between dovecot-oauth2.token.conf.ext and dovecot-oauth2.plain.conf.ext ? Do I need to configure both? I used https://doc.dovecot.org/configuration_manual/authentication/oauth2/#proxy as a reference. I would appreciate your reply. Yours faithfully, ------------------------------ e-mail: taiki.fukuda(a)justsystems.com TEL: 03-5324-7900 mobile: 080-6198-7328 ------------------------------

3 21

Undefined SSL object
by Frank Elsner 31 Jan '21

31 Jan '21

Hi community, when doing imapsync to my dovecot server (Host2) I get the following Host2 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH DEBUG: .../IO/Socket/SSL.pm:1117: global error: Undefined SSL object Host2: Socket successfuly converted to SSL Beside this message all works fine. What is it? SSL setting? How to overcome the message? Greetings, Frank

2 1

Processing incoming mail efficiently
by Ron Garret 30 Jan '21

30 Jan '21

I’ve asked a related question on this list before but I now have a much better handle on what I’m doing and I realize that I still don’t know the answer, so I’m going to ask this again in a slightly different form. I’m writing a spam filter, so obviously I need to feed incoming mail to it somehow. The “obvious” way to do this is with a sieve script using the pipe extension. There are two problems with this: 1. This will always pipe the entire file no matter how big it is. The filter will often not need to process the body of the message, only the headers, or only the first part of a multipart MIME message. Is there any way to allow my filter to open the file in which the message is stored rather than piping it a copy of the message? 2. Once the filter has processed the message and decided if it’s spam it still needs to move the message to the appropriate folder (INBOX or Junk). To do this it needs to somehow correlate the *content* of the message that was piped to it with the UID of the message that needs to be moved. One way to do this is to pull out the message-id header and then use doveadm to find the file containing the message with that message-id, but there are two problems with this. First, not all messages have message-ids. I can work around this by adding my own message-id to messages that don’t already have them, but this just feel wrong. And second, unless dovecot keeps an index of message-ids (does it?) then this will be horribly inefficient because it will have to essentially grep for the message id every time I want to move a message. So it seems like there has to be a better way, but I can’t think of what that would be. I figure this has to be a solved problem because I am obviously not the first person to write a spam filter for dovecot. What is the Right Way to do this? Thanks, rg

3 6

What is the right way to move messages between mailboxes?
by Ron Garret 30 Jan '21

30 Jan '21

I’m working on a spam filter. Incoming messages are sent to an “incoming” folder (via a sieve script) where they are processed by the filter and moved either to INBOX or Junk. My question is: what is the right way to effect this move? Can I just mv the file? With Dovecot automatically notice this and update any connected IMAP clients? Or is there some other procedure and/or utility (doveadm?) that I should be using for this? Thanks, rg

1 0

dovecot and broken uidlist
by Maciej Milaszewski 29 Jan '21

29 Jan '21

Hi I have been trying resolve my problem with dovecot for a few days and I dont have idea.... My environment is: dovecot director+5 dovecot guest dovecot-2.2.36.4 from source Linux 3.16.0-11-amd64 storage via nfs (NetApp) all works fine but when I update OS from debian 8 (kernel 3.16.x) to debian 9 (kernel 4.9.x ) sometimes I get random in logs: Broken dovecot-uidlist examle: Error: Broken file /vmail2/po/pollygraf.xxx_pg_pollygraf/Maildir/dovecot-uidlist line 88: Invalid data: (for random users - sometimes 10 error in day per node, some times more) File looks ok But if I change kernel to 3.16.x problem with "Broken file dovecot-uidlist" - not exists if turn to 4.9 or 5.x - problem exists I have storage via nfs with opions: rw,sec=sys,noexec,noatime,tcp,hard,rsize=65536,wsize=65536,intr,nordirplus,nfsvers=3,tcp,actimeo=120 I tested with "nocto" or without "nocto" - nothing changes ...... nfs options in node: mmap_disable = yes mail_fsync = always I bet the configuration is correct and I wonder why the problem occurs with other kernels 3.x.x - ok 4.x - not ok I check and user who have problem did not connect to another node in this time I dont have idea why problem exists on the kernel 4.x but not in 3.x

6 14

Long Term Archival
by Rupert Gallagher 29 Jan '21

29 Jan '21

Hello, I would like to know what is your strategy for legally compliant long term archival of e-mails (up to 10 years). Thank you

3 2

10G mails use 90G on disk
by Markus Schönhaber 29 Jan '21

29 Jan '21

Hello, on a system I administer the disk where Dovecot's mailstore (mdbox) resides got filled up to the brim although the combined quotas for the users are much smaller than the disk's capacity. For one user I see the following: doveadm quota get -u <USER>@<DOMAIN> Username Quota name Type Value Limit % <USER>@<DOMAIN> User quota STORAGE 10231248 20971520 48 <USER>@<DOMAIN> User quota MESSAGE 11176 - 0 So this user has used ~10G of his 20G quota. But looking at the space used on disk: # du -hs /var/spool/vmail/mail/<DOMAIN>/<USER>/storage/ 90G /var/spool/vmail/mail/<DOMAIN>/<USER>/storage/ What might be the reason that mail size and disk space used differ so much? And most of all: how can I prevent that from happening? Regards mks # doveconf -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 4.19.0-13-amd64 x86_64 Debian 10.7 ext4 # Hostname: … auth_mechanisms = plain login dict { quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } imap_id_log = * login_log_format_elements = user=<%u> method=%m rip=%r lip=%l lport=%a mpid=%e %c mail_home = /var/spool/vmail/home/%d/%n mail_location = mdbox:/var/spool/vmail/mail/%d/%n mail_plugins = " quota acl" 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 { special_use = \Drafts } mailbox Entwürfe { special_use = \Drafts } mailbox Entw&APw-rfe { special_use = \Drafts } mailbox "Gelöschte Objekte" { special_use = \Trash } mailbox "Gel&APY-schte Objekte" { special_use = \Trash } mailbox "Gesendete Objekte" { special_use = \Sent } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = dict:User quota::proxy::quota recipient_delimiter = + sieve = file:~/sieve;active=~/.dovecot.sieve sieve_redirect_envelope_from = orig_recipient } protocols = " imap lmtp sieve" service auth-worker { user = $default_internal_user } service auth { inet_listener { port = 12345 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service stats { client_limit = 10000 unix_listener stats-writer { group = vmail user = vmail } } ssl_cert = </etc/letsencrypt/live/<DOMAIN>/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = " quota acl quota sieve" } protocol lda { mail_plugins = " quota acl sieve" } protocol imap { mail_plugins = " quota acl imap_quota acl" } remote 192.168.1.0/24 { protocol imap { disable_plaintext_auth = no } }

2 4

mail event
by Marc Roos 29 Jan '21

29 Jan '21

> > Using mail_log plugin is always very recommended, > > https://doc.dovecot.org/configuration_manual/plugins/mail_event_logging/ > I am not sure if I am correct, but I think this logs every deleted message not? I was testing with this a while ago. Is there also an option that only logs something like '300 messages deleted'?

1 0

SMTP tool for Email validation
by Amol Kale 29 Jan '21

29 Jan '21

Hi, We are looking for a tool for bulk SMTP testing / Email validation using telnet or similar protocol ( which doesn't send the mails ) It generally involves steps like NSlookup to check MX of destination server, opening port25, telnet to communicate with client server, then finally checking the correctness of user email account. Please connect if you have such ready tool with you or you can develop Process example- <https://blog.mailtrap.io/verify-email-address-without-sending/> https://blog.mailtrap.io/verify-email-address-without-sending/ Thanks & regards Amol Kale Founder Director Talent Trackers HR 7350002596

4 3

Enabling auth_cache_verify_password_with_worker disables proxy mode
by Malte Schmidt 29 Jan '21

29 Jan '21

Setting "auth_cache_verify_password_with_worker = yes" in order to leverage multiple cores for the Dovecot authentication-process causes Dovecot not to proxy anymore. With debug-logging I figured: auth_cache_verify_password_with_worker = no passdb out: OK 1 user=username host=bla port=10993 ssl=any-cert mail_crypt_global_public_key=key mail_crypt_global_private_key=otherkey hostip=123.123.123.123 proxy pass=pw auth_cache_verify_password_with_worker = yes passdb out: OK 1 user=username The rest seems missing. Dovecot version: v2.3.11.3 Searching for this issue, I found at least two posts mentioning the same symptoms: https://dovecot.org/pipermail/dovecot/2018-April/111583.html https://dovecot.org/pipermail/dovecot/2020-April/118564.html https://listen.jpberlin.de/pipermail/dovecot/2020-April/001915.html (same as the english one from april 2020)

2 1

Infinity loop when run "doveadm quota get -A" from Dovecot Director with 500 users
by Duc Anh Do 29 Jan '21

29 Jan '21

Hi all, I have one Dovecot Director, two Dovecot Backends and one LDAP server with about 500 users. I would like to run *doveadm quota get -A* from the Director. In each Backend, there is no problem when run the command: # doveadm quota get -A user1 User quota STORAGE 0 1048576000000000 0 user1 User quota MESSAGE 0 - 0 … user500 User quota STORAGE 0 1048576000000000 0 user500 User quota MESSAGE 0 - 0 However, when I run from the Director, the command might stuck in an infinity loop (I have to terminate to quit): # doveadm quota get -A user1 User quota STORAGE 0 1048576000000000 0 user1 User quota MESSAGE 0 - 0 … user49 User quota STORAGE 0 1048576000000000 0 user49 User quota MESSAGE 0 - 0 user66 User quota STORAGE 0 1048576000000000 0 user66 User quota MESSAGE 0 - 0 ^Cdoveadm(user86): Error: doveadm server failure doveadm: Error: Failed to iterate through some users doveadm: Error: backend2.local:24245: Command quota get failed for user53: EOF doveadm: Error: backend1.local:24245: Command quota get failed for user66: EOF doveadm: Error: Aborted This problem occurs in both Dovecot 2.2.36 and Dovecot 2.3.11, 2.3.13 (I build Dovecot from source). It's ok for me to get quota of one user from the Director: # doveadm quota get -u user1 Quota name Type Value Limit % User quota STORAGE 0 1048576000000000 0 User quota MESSAGE 0 - 0 And if there's only one Backend, *doveadm quota get -A* from the Director works well too. After investigating, I found the infinity loop: File src/doveadm/doveadm-mail-server.c: static void doveadm_server_flush_one(struct doveadm_server *server) { unsigned int count = array_count(&server->queue); do { io_loop_run(current_ioloop); } while (array_count(&server->queue) == count && doveadm_server_have_used_connections(server) && !DOVEADM_MAIL_SERVER_FAILED()); } In case there're many Backends, I see only global variable *current_ioloop* is used to notify in the callback function. Might this be a race condition? I understand there's a workaround to do my work: - Run *doveadm user '*'* to get all users - Loop through all users and run *doveadm quota get -u xxx* Thanks, Anh Do

2 2

Dovecot Mail Server - Cloud Compatibility
by Kristie Buller 28 Jan '21

28 Jan '21

4 3

2.13 read, i_stream_read_memarea: assertion failed: (!stream->blocking)
by Stuart Henderson 28 Jan '21

28 Jan '21

I'm seeing this on some mailboxes with 2.13 on OpenBSD amd64 (recent snapshot): dovecot: imap(sthen)<47220><ARy1oKS5lWDDX7sa>: Panic: file istream.c: line 332 (i_stream_read_memarea): assertion failed: (!stream->blocking) Using sieve, imapsieve, replicator, zlib (zlib_save = lz4 and has been for some time, so the relevant messages probably use this). Using mmap_disable because OpenBSD. Any suggestions how to handle it, preferably automatically? (even if a message is corrupt/lost it would be really nice if a standard client could still access the mailbox rather than kill the imap process while reading headers). bt first for ease of reading, followed by bt full in case it has any additional clues. (gdb) bt #0 thrkill () at /tmp/-:3 #1 0x00000e9158c7c3ae in _libc_abort () at /usr/src/lib/libc/stdlib/abort.c:51 #2 0x00000e91adc00c26 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:459 #3 0x00000e91adbff034 in fatal_handler_real (ctx=0x7f7ffffcdd90, format=<optimized out>, args=<optimized out>) at failures.c:471 #4 0x00000e91adbfffb1 in i_internal_fatal_handler (ctx=0x0, format=0x6 <error: Cannot access memory at address 0x6>, args=0x0) at failures.c:866 #5 0x00000e91adbff266 in i_panic (format=0x6 <error: Cannot access memory at address 0x6>) at failures.c:523 #6 0x00000e91adc0f15c in i_stream_read_memarea (stream=0xe917ead3480) at istream.c:332 #7 0x00000e91adc1925f in read_more (sstream=0xe91431c4800) at istream-seekable.c:149 #8 0x00000e91adc19090 in read_from_buffer (sstream=0xe91431c4800, ret_r=0x7f7ffffcded8) at istream-seekable.c:204 #9 0x00000e91adc1856d in i_stream_seekable_read (stream=0xe91431c4800) at istream-seekable.c:265 #10 0x00000e91adc0f0a4 in i_stream_read_memarea (stream=0xe91431c4880) at istream.c:313 #11 0x00000e91adc16bbc in i_stream_limit_read (stream=0xe91e9ccca00) at istream-limit.c:49 #12 0x00000e91adc0f0a4 in i_stream_read_memarea (stream=0xe91e9ccca80) at istream.c:313 #13 0x00000e91adc0f79c in i_stream_read_copy_from_parent (istream=<optimized out>) at istream.c:387 #14 0x00000e918e9729fa in i_stream_mail_read (stream=0xe91e9ccc000) at istream-mail.c:115 #15 0x00000e91adc0f0a4 in i_stream_read_memarea (stream=0xe91e9ccc080) at istream.c:313 #16 0x00000e91adc104f5 in i_stream_read (stream=0xe91e9ccc080) at istream.c:271 #17 i_stream_read_data (stream=0xe91e9ccc080, data_r=0x7f7ffffce110, size_r=0x7f7ffffce100, threshold=1) at istream.c:747 #18 0x00000e91adbd6a18 in i_stream_read_bytes (stream=0x0, data_r=<optimized out>, size_r=<optimized out>, wanted=<optimized out>) at ../../src/lib/istream.h:214 #19 message_parse_header_next (ctx=0xe9183e1b180, hdr_r=0x7f7ffffce1d0) at message-header-parser.c:85 #20 0x00000e91adbceef2 in read_header (mstream=0xe91e9cc6000) at istream-header-filter.c:195 #21 i_stream_header_filter_read (stream=0xe91e9cc6000) at istream-header-filter.c:450 #22 0x00000e91adc0f0a4 in i_stream_read_memarea (stream=0xe91e9cc6080) at istream.c:313 #23 0x00000e91adc104f5 in i_stream_read (stream=0xe91e9cc6080) at istream.c:271 #24 i_stream_read_data (stream=0xe91e9cc6080, data_r=0x7f7ffffce2c0, size_r=0x7f7ffffce2c8, threshold=0) at istream.c:747 #25 0x00000e91adbdc07b in i_stream_read_bytes (stream=0xe91e9cc6080, data_r=<optimized out>, size_r=<optimized out>, wanted=<error reading variable: Cannot access memory at address 0x1>) at ../../src/lib/istream.h:214 #26 message_get_header_size (input=0xe91e9cc6080, hdr=0x7f7ffffce328, has_nuls_r=0x7f7ffffce3b7) at message-size.c:19 #27 0x00000e8f25e767d9 in imap_msgpart_get_partial_header (mail=0xe91e9cc4848, mail_input=<optimized out>, msgpart=0xe91c92a2048, virtual_size_r=<optimized out>, result_r=0x7f7ffffce408, have_crlfs_r=<optimized out>) at imap-msgpart.c:401 #28 imap_msgpart_open_normal (mail=<optimized out>, msgpart=0xe91c92a2048, part=<optimized out>, virtual_size_r=<optimized out>, result_r=0x7f7ffffce408, have_crlfs_r=<optimized out>) at imap-msgpart.c:637 #29 imap_msgpart_open (mail=<optimized out>, msgpart=0xe91c92a2048, result_r=0x7f7ffffce408) at imap-msgpart.c:706 #30 0x00000e8f25e672ff in fetch_body_msgpart (ctx=0xe9159845368, mail=<optimized out>, body=0xe91e9cb4398) at imap-fetch-body.c:184 #31 0x00000e8f25e65837 in imap_fetch_more_int (ctx=0xe9159845368, cancel=false) at imap-fetch.c:562 #32 0x00000e8f25e6552c in imap_fetch_more (ctx=0xe9159845368, cmd=0xe9159845048) at imap-fetch.c:617 #33 0x00000e8f25e55521 in cmd_fetch (cmd=0xe9159845048) at cmd-fetch.c:337 #34 0x00000e8f25e62d12 in command_exec (cmd=0xe9159845048) at imap-commands.c:201 #35 0x00000e8f25e61576 in client_command_input (cmd=0xe9159845048) at imap-client.c:1204 #36 0x00000e8f25e61682 in client_command_input (cmd=0xe9159845048) at imap-client.c:1269 #37 0x00000e8f25e5ffb4 in client_handle_next_command (client=0xe9159845848, remove_io_r=<optimized out>) at imap-client.c:1313 #38 client_handle_input (client=0xe9159845848) at imap-client.c:1327 #39 0x00000e8f25e5e755 in client_input (client=0xe9159845848) at imap-client.c:1371 #40 0x00000e91adc1c851 in io_loop_call_io (io=0xe91eb5d0b00) at ioloop.c:714 #41 0x00000e91adc1f84c in io_loop_handler_run_internal (ioloop=0xe9162373d00) at ioloop-kqueue.c:164 #42 0x00000e91adc1cfd9 in io_loop_handler_run (ioloop=0xe9162373d00) at ioloop.c:766 #43 0x00000e91adc1cce8 in io_loop_run (ioloop=0xe9162373d00) at ioloop.c:739 #44 0x00000e91adb77655 in master_service_run (service=0xe9193c39600, callback=0x6) at master-service.c:853 #45 0x00000e8f25e70dd1 in main (argc=1, argv=<optimized out>) at main.c:532 (gdb) bt full #0 thrkill () at /tmp/-:3 No locals. #1 0x00000e9158c7c3ae in _libc_abort () at /usr/src/lib/libc/stdlib/abort.c:51 sa = { __sigaction_u = { __sa_handler = 0x0, __sa_sigaction = 0x0 }, sa_mask = 4294967295, sa_flags = 0 } mask = 4294967263 #2 0x00000e91adc00c26 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:459 recursed = 0 backtrace = <optimized out> #3 0x00000e91adbff034 in fatal_handler_real (ctx=0x7f7ffffcdd90, format=<optimized out>, args=<optimized out>) at failures.c:471 status = 6 #4 0x00000e91adbfffb1 in i_internal_fatal_handler (ctx=0x0, format=0x6 <error: Cannot access memory at address 0x6>, args=0x0) at failures.c:866 No locals. #5 0x00000e91adbff266 in i_panic (format=0x6 <error: Cannot access memory at address 0x6>) at failures.c:523 ctx = { type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0, timestamp_usecs = 0, log_prefix = 0x0, log_prefix_type_pos = 0 } args = {{ gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7f7ffffcddf0, reg_save_area = 0x7f7ffffcdce0 }} #6 0x00000e91adc0f15c in i_stream_read_memarea (stream=0xe917ead3480) at istream.c:332 _stream = 0xe917ead3400 old_size = 0 ret = 0 #7 0x00000e91adc1925f in read_more (sstream=0xe91431c4800) at istream-seekable.c:149 ret = <optimized out> size = <optimized out> #8 0x00000e91adc19090 in read_from_buffer (sstream=0xe91431c4800, ret_r=0x7f7ffffcded8) at istream-seekable.c:204 old_skip = <optimized out> stream = 0xe91431c4800 size = <optimized out> data = <optimized out> avail_size = <optimized out> #9 0x00000e91adc1856d in i_stream_seekable_read (stream=0xe91431c4800) at istream-seekable.c:265 sstream = 0xe91431c4800 ret = 16019855444480 size = <optimized out> data = <optimized out> pos = <optimized out> #10 0x00000e91adc0f0a4 in i_stream_read_memarea (stream=0xe91431c4880) at istream.c:313 _stream = 0xe91431c4800 old_size = 0 ret = <optimized out> #11 0x00000e91adc16bbc in i_stream_limit_read (stream=0xe91e9ccca00) at istream-limit.c:49 lstream = 0xe91e9ccca00 pos = 16017421909770 ret = <optimized out> left = <optimized out> #12 0x00000e91adc0f0a4 in i_stream_read_memarea (stream=0xe91e9ccca80) at istream.c:313 _stream = 0xe91e9ccca00 old_size = 0 ret = <optimized out> #13 0x00000e91adc0f79c in i_stream_read_copy_from_parent (istream=<optimized out>) at istream.c:387 stream = 0xe91e9ccc000 pos = <optimized out> ret = <optimized out> #14 0x00000e918e9729fa in i_stream_mail_read (stream=0xe91e9ccc000) at istream-mail.c:115 mstream = 0xe91e9ccc000 ret = <optimized out> size = <optimized out> #15 0x00000e91adc0f0a4 in i_stream_read_memarea (stream=0xe91e9ccc080) at istream.c:313 _stream = 0xe91e9ccc000 old_size = 0 ret = <optimized out> #16 0x00000e91adc104f5 in i_stream_read (stream=0xe91e9ccc080) at istream.c:271 _stream = 0xe91e9ccc000 ret = <optimized out> #17 i_stream_read_data (stream=0xe91e9ccc080, data_r=0x7f7ffffce110, size_r=0x7f7ffffce100, threshold=1) at istream.c:747 read_more = false ret = <error reading variable ret (Cannot access memory at address 0x0)> #18 0x00000e91adbd6a18 in i_stream_read_bytes (stream=0x0, data_r=<optimized out>, size_r=<optimized out>, wanted=<optimized out>) at ../../src/lib/istream.h:214 No locals. #19 message_parse_header_next (ctx=0xe9183e1b180, hdr_r=0x7f7ffffce1d0) at message-header-parser.c:85 skip = <error reading variable skip (Cannot access memory at address 0x0)> line = 0xe9183e1b180 colon_pos = 4294967295 no_newline = <error reading variable no_newline (Cannot access memory at address 0x0)> crlf_newline = <error reading variable crlf_newline (Cannot access memory at address 0x0)> continued = false size = 0 msg = 0xe91adafee50 <uchar_nul> "" startpos = 0 continues = <error reading variable continues (Cannot access memory at address 0x0)> i = <optimized out> parse_size = <optimized out> ret = <optimized out> last_crlf = <optimized out> last_no_newline = <optimized out> #20 0x00000e91adbceef2 in read_header (mstream=0xe91e9cc6000) at istream-header-filter.c:195 highwater_offset = <optimized out> max_buffer_size = 8192 hdr = 0x0 hdr_ret = <optimized out> ret = <optimized out> ret2 = <optimized out> #21 i_stream_header_filter_read (stream=0xe91e9cc6000) at istream-header-filter.c:450 mstream = 0xe91e9cc6000 v_offset = <optimized out> ret = <optimized out> #22 0x00000e91adc0f0a4 in i_stream_read_memarea (stream=0xe91e9cc6080) at istream.c:313 _stream = 0xe91e9cc6000 old_size = 0 ret = <optimized out> #23 0x00000e91adc104f5 in i_stream_read (stream=0xe91e9cc6080) at istream.c:271 _stream = 0xe91e9cc6000 ret = <optimized out> #24 i_stream_read_data (stream=0xe91e9cc6080, data_r=0x7f7ffffce2c0, size_r=0x7f7ffffce2c8, threshold=0) at istream.c:747 read_more = false ret = <error reading variable ret (Cannot access memory at address 0x0)> #25 0x00000e91adbdc07b in i_stream_read_bytes (stream=0xe91e9cc6080, data_r=<optimized out>, size_r=<optimized out>, wanted=<error reading variable: Cannot access memory at address 0x1>) at ../../src/lib/istream.h:214 No locals. #26 message_get_header_size (input=0xe91e9cc6080, hdr=0x7f7ffffce328, has_nuls_r=0x7f7ffffce3b7) at message-size.c:19 size = 0 msg = 0xe91adafee50 <uchar_nul> "" startpos = <error reading variable startpos (Cannot access memory at address 0x0)> missing_cr_count = <error reading variable missing_cr_count (Cannot access memory at address 0x0)> ret = <optimized out> i = <optimized out> #27 0x00000e8f25e767d9 in imap_msgpart_get_partial_header (mail=0xe91e9cc4848, mail_input=<optimized out>, msgpart=0xe91c92a2048, virtual_size_r=<optimized out>, result_r=0x7f7ffffce408, have_crlfs_r=<optimized out>) at imap-msgpart.c:401 hdr_size = { physical_size = 0, virtual_size = 0, lines = 0 } hdr_fields = 0xe91c92a21f8 hdr_count = <optimized out> input = 0xe91e9cc6080 has_nuls = false #28 imap_msgpart_open_normal (mail=<optimized out>, msgpart=0xe91c92a2048, part=<optimized out>, virtual_size_r=<optimized out>, result_r=0x7f7ffffce408, have_crlfs_r=<optimized out>) at imap-msgpart.c:637 hdr_size = { physical_size = 0, virtual_size = 0, lines = 0 } body_size = { physical_size = 0, virtual_size = 0, lines = 0 } input = <optimized out> unknown_crlfs = <error reading variable unknown_crlfs (Cannot access memory at address 0x0)> part_size = <error reading variable part_size (Cannot access memory at address 0x0)> #29 imap_msgpart_open (mail=<optimized out>, msgpart=0xe91c92a2048, result_r=0x7f7ffffce408) at imap-msgpart.c:706 part = <optimized out> ret = <optimized out> virtual_size = 1 binary = <optimized out> have_crlfs = <optimized out> #30 0x00000e8f25e672ff in fetch_body_msgpart (ctx=0xe9159845368, mail=<optimized out>, body=0xe91e9cb4398) at imap-fetch-body.c:184 result = { input = 0x0, size = 0, size_field = (unknown: 0), binary_decoded_input_has_nuls = false } str = <optimized out> #31 0x00000e8f25e65837 in imap_fetch_more_int (ctx=0xe9159845368, cancel=false) at imap-fetch.c:562 _data_stack_cur_id = <optimized out> client = <optimized out> ret = <optimized out> handlers = 0xe91e9cb4020 count = 5 #32 0x00000e8f25e6552c in imap_fetch_more (ctx=0xe9159845368, cmd=0xe9159845048) at imap-fetch.c:617 ret = <optimized out> #33 0x00000e8f25e55521 in cmd_fetch (cmd=0xe9159845048) at cmd-fetch.c:337 qresync_args = { qresync_sample_seqset = 0xe9159845368, qresync_sample_uidset = 0xe9159845020 } args = <optimized out> send_vanished = <optimized out> client = 0xe9159845848 messageset = <optimized out> search_args = 0x0 ret = <optimized out> ctx = 0x0 next_arg = <optimized out> list_arg = <optimized out> #34 0x00000e8f25e62d12 in command_exec (cmd=0xe9159845048) at imap-commands.c:201 hook = <optimized out> #35 0x00000e8f25e61576 in client_command_input (cmd=0xe9159845048) at imap-client.c:1204 client = 0xe9159845848 command = <optimized out> tag = <optimized out> ret = <optimized out> name = <optimized out> #36 0x00000e8f25e61682 in client_command_input (cmd=0xe9159845048) at imap-client.c:1269 client = 0xe9159845848 command = <optimized out> tag = <optimized out> ret = <optimized out> name = <optimized out> #37 0x00000e8f25e5ffb4 in client_handle_next_command (client=0xe9159845848, remove_io_r=<optimized out>) at imap-client.c:1313 No locals. #38 client_handle_input (client=0xe9159845848) at imap-client.c:1327 _data_stack_cur_id = <optimized out> handled_commands = false ret = <optimized out> remove_io = <optimized out> #39 0x00000e8f25e5e755 in client_input (client=0xe9159845848) at imap-client.c:1371 output = 0xe92088000a0 bytes = 218 cmd = <optimized out> #40 0x00000e91adc1c851 in io_loop_call_io (io=0xe91eb5d0b00) at ioloop.c:714 ioloop = 0xe9162373d00 t_id = 0 #41 0x00000e91adc1f84c in io_loop_handler_run_internal (ioloop=0xe9162373d00) at ioloop-kqueue.c:164 tv = { tv_sec = 3, tv_usec = 410626 } ts = { tv_sec = 3, tv_nsec = 410626000 } ctx = 0xe9171193980 msecs = <optimized out> events_count = <optimized out> events = <optimized out> ret = <optimized out> i = <optimized out> io = 0xe91eb5d0b00 #42 0x00000e91adc1cfd9 in io_loop_handler_run (ioloop=0xe9162373d00) at ioloop.c:766 No locals. #43 0x00000e91adc1cce8 in io_loop_run (ioloop=0xe9162373d00) at ioloop.c:739 No locals. #44 0x00000e91adb77655 in master_service_run (service=0xe9193c39600, callback=0x6) at master-service.c:853 No locals. #45 0x00000e8f25e70dd1 in main (argc=1, argv=<optimized out>) at main.c:532 set_roots = {0xe91adc66270 <smtp_submit_setting_parser_info>, 0xe8f25e7e310 <imap_setting_parser_info>, 0x0} login_set = { auth_socket_path = 0xe9136774490 "HEADER.FIELDS (DATE FROM SENDER SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL)", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0xe8f25e70fc0 <login_client_connected>, failure_callback = 0xe8f25e712b0 <login_client_failed>, request_auth_token = true } username = <optimized out> storage_service_flags = <optimized out> service_flags = <optimized out> auth_socket_path = <optimized out> c = <optimized out> error = 0x7f7ffffcea18 "]\353\374\377\177\177" (gdb)

2 3

Where is dovemon
by lists＠mlserv.org 27 Jan '21

27 Jan '21

7 7

doveadm http api expunge call
by tim＠linux-daus.de 26 Jan '21

26 Jan '21

Hi all, i'm start porting some of my maintenance scripts from doveadm cli to doveadm http api. I stumble over the doveadm expunge call. The response doesn't contain any additional output but the generic doveadmresponse object without any additional information. The list is always empty wether the expunge has expunged some emails or not: [['doveadmResponse', [], 'tag1']] Other then the cli command wich outputs a list of the mails that were expunged. Is this a bug? Best regards, Tim

1 0

Forwarding parameters for imapc
by bra＠fsn.hu 26 Jan '21

26 Jan '21

Hi, I have the following IMAP setup: dovecot proxy -> dovecot server -> IMAP backend (imapc) What I want to achieve is to have the original client parameters from the proxy in the IMAP backend. Dovecot in proxy mode sends them via an ID command, like this: ID ("x-session-id" "SESS" "x-originating-ip" "IP" "x-originating-port" "PORT" "x-connected-ip" "IP" "x-connected-port" "PORT" "x-proxy-ttl" "4") Is it possible with current dovecot versions to send this to the imapc backend as well? Of course I would expect that if the dovecot proxy is in login_trusted_networks, information from it should be used (IMAP: ID, POP/LMTP: XCLIENT). If this is not the case, could you please implement it? Thanks,

1 0

Error "collect2: error: ld returned 213 exit status" when build Dovecot 2.3.13 on CentOS 7&8 with Valgrind
by Duc Anh Do 26 Jan '21

26 Jan '21

Hi all, I'm building Dovecot from source of Dovecot 2.3.13. When doing make check, I saw an error: make[1]: Entering directory '/home/xxx/rpmbuild/BUILD/xxx/dovecot-2.3.13/src/lib-ssl-iostream' for bin in test-iostream-ssl; do \ if ! /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \ done collect2: error: ld returned 213 exit status Failed to run: ./test-iostream-ssl This is my configuration in spec file: %configure \ INSTALL_DATA="install -c -p -m644" \ --docdir=%{_docdir}/%{name} \ --disable-static \ --disable-rpath \ --with-nss \ --with-shadow \ --with-pam \ --with-gssapi=plugin \ --with-ldap=plugin \ --with-sql=plugin \ --with-pgsql \ --with-mysql \ --with-sqlite \ --with-zlib \ --with-libcap \ --with-ssl=openssl \ --with-ssldir=%{ssldir} \ --with-docs I installed OpenSSL and Valgrind: # yum list installed | egrep "valgrind|openssl" openssl-devel.x86_64 1:1.1.1g-12.el8_3 @BaseOS openssl-libs.x86_64 1:1.1.1g-12.el8_3 @BaseOS valgrind.x86_64 1:3.16.0-2.el8 @AppStream valgrind-devel.x86_64 1:3.16.0-2.el8 @AppStream I investigated the problem and found something: - Unlike other lib-xxx, libtool doesn't generate executable binary test-iostream-ssl inside lib-ssl-iostream directory. That's a shell script and actual executable binary is inside ./libs directory ( https://www.gnu.org/software/libtool/manual/libtool.html#Linking-executables ): $ pwd /home/xxx/rpmbuild/BUILD/xxx/dovecot-2.3.13/src/lib-ssl-iostream $ file test-iostream-ssl test-iostream-ssl: POSIX shell script, ASCII text executable, with very long lines $ file .libs/test-iostream-ssl .libs/test-iostream-ssl: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=c6a800c253c38a7eb78886286ef779d871550a6c, with debug_info, not stripped, too many notes (256) That means when running make check, Valgrind will monitor the shell script generated by libtool instead of the actual test code. And error occurs. - To confirm, I changed Makefile a bit: $ pwd /home/xxx/rpmbuild/BUILD/xxx/dovecot-2.3.13/src/lib-ssl-iostream $ vim Makefile check-local: for bin in $(test_programs); do \ export LD_LIBRARY_PATH=./.libs; \ if ! $(RUN_TEST) ./.libs/$$bin; then exit 1; fi; \ done Then do make check: $ cd ~/rpmbuild/BUILD/xxx/dovecot-2.3.13 $ make -C src/lib-ssl-iostream/ clean $ make -C src/lib-ssl-iostream/ check make[1]: Entering directory '/home/xxx/rpmbuild/BUILD/xxx/dovecot-2.3.13/src/lib-ssl-iostream' for bin in test-iostream-ssl; do \ export LD_LIBRARY_PATH=./.libs; \ if ! /bin/sh -x ../../run-test.sh ../.. ./.libs/$bin; then exit 1; fi; \ #if ! /bin/sh -x ../../run-test.sh ../.. ./$bin; then exit 1; fi; \ done ssl: handshake ....................................................... : ok ssl: o_stream_get_buffer_avail_size .................................. : ok ssl: small packets ................................................... : ok 0 / 3 tests failed + ret=0 + test -s test.out~19257 + test 0 '!=' 0 + exit 0 + rm -f test.out~19257 make[1]: Leaving directory '/home/xxx/rpmbuild/BUILD/xxx/dovecot-2.3.13/src/lib-ssl-iostream' make: Leaving directory '/home/xxx/rpmbuild/BUILD/xxx/dovecot-2.3.13/src/lib-ssl-iostream' - According to the manual of libtool, if I use libtool to generate library and executable binary, I should use libtool to execute (or debug or anything else). That will avoid misconfiguration and unexpected errors: - https://www.gnu.org/software/libtool/manual/html_node/Debugging-executables… - https://stackoverflow.com/a/14186488 My patch looks like this: diff --git a/src/lib-ssl-iostream/Makefile.am b/src/lib-ssl-iostream/Makefile.am index 5aaea5d..17ebf1d 100644 --- a/src/lib-ssl-iostream/Makefile.am +++ b/src/lib-ssl-iostream/Makefile.am @@ -56,6 +56,6 @@ noinst_PROGRAMS = $(test_programs) check-local: for bin in $(test_programs); do \ - if ! $(RUN_TEST) ./$$bin; then exit 1; fi; \ + if ! $(LIBTOOL) --mode execute $(RUN_TEST) ./$$bin; then exit 1; fi; \ done endif Result: make[2]: Entering directory '/home/xxx/rpmbuild/BUILD/xxx/dovecot-2.3.13/src/lib-ssl-iostream' make check-local make[3]: Entering directory '/home/xxx/rpmbuild/BUILD/xxx/dovecot-2.3.13/src/lib-ssl-iostream' for bin in test-iostream-ssl; do \ if ! /bin/sh ../../libtool --mode execute /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \ done ssl: handshake ....................................................... : ok ssl: o_stream_get_buffer_avail_size .................................. : ok ssl: small packets ................................................... : ok 0 / 3 tests failed make[3]: Leaving directory '/home/xxx/rpmbuild/BUILD/xxx/dovecot-2.3.13/src/lib-ssl-iostream' make[2]: Leaving directory '/home/xxx/rpmbuild/BUILD/xxx/dovecot-2.3.13/src/lib-ssl-iostream' Can anyone help to correct my understanding and my patch? Thanks, Anh Do

2 2

Deliver to different namespace with address detail
by Tobia Grosselle [ Terralink ] 25 Jan '21

25 Jan '21

can anyone confirm this?

1 0

Re: [BUG REPORT] In some cases dovecot sends (huge) binary data to solr for indexing
by Alexey Panov 25 Jan '21

25 Jan '21

Hello John, Sorry for a bit delayed reply. For some reason some of dovecot mail list messages are not reaching my inbox :( Indeed, I can confirm that your patch works as expected: meaning strips out just the message body. So yes, in my report I supposed to say: message bodies of affected messages are being ignored completely. Sorry for confusion and thanks again for such a useful patch!

1 0

New dovecot server, authentication confusion
by Jeff Abrahamson 24 Jan '21

24 Jan '21

I've set up a new dovecot+postfix instance with virtual (not system) users. I've a few questions, mostly about auth. I /think/ that postfix handles auth by asking dovecot. Users need to provide user + password to send (smtps) and receive (imaps). I see where I've configured this for dovecot, which is /etc/dovecot/passwd.db. That file contains lines like this: jeff@mobilitains.fr:{BLF-CRYPT}$2y$05$c... What concerns me is that I see occasional log items like this: Jan 24 11:26:33 nantes-m1 postfix/smtpd[4597]: fatal: no SASL authentication mechanisms (Also, I can't connect with thunderbird.) But I think I've configured SASL auth, so I'm not sure what to look at / how to debug this. I'm looking for suggestions how to approach this. I do not see how postfix knows who is allowed to connect, however. Am I correct that postfix delegates SASL to dovecot? This is the relevant config, I think: [T] jeff@nantes-m1:log $ doveconf -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-64-generic x86_64 Ubuntu 20.04.1 LTS # Hostname: nantes-m1.p27.eu auth_verbose = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = username_format=%u scheme=blf-crypt /etc/dovecot/passwd.db driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /var/mail/vmail/sieve-after sieve_before = /var/mail/vmail/sieve-before sieve_dir = ~/sieve } protocols = " imap" ssl = required ssl_cert = </etc/letsencrypt/live/nantes-m1.p27.eu/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 { args = uid=4000 gid=4000 home=/var/mail/vmail/%d/%n driver = static } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster@{{ primary_domain }} quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags mail_max_userip_connections = 20 } [T] jeff@nantes-m1:log $ [T] jeff@nantes-m1:log $ postconf -n | grep -i sasl broken_sasl_auth_clients = yes smtpd_recipient_restrictions = reject_unknown_client_hostname,reject_unknown_sender_domain,reject_unknown_recipient_domain,permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination,reject_invalid_hostname,reject_non_fqdn_sender smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot [T] jeff@nantes-m1:log $ postconf -Mf smtp inet n - y - - smtpd submission inet n - y - - smtpd -o syslog_name=postfix/submission -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions= -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o milter_macro_daemon_name=ORIGINATING smtps inet n - y - - smtpd -o syslog_name=postfix/smtps -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_reject_unlisted_recipient=no -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions= -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o milter_macro_daemon_name=ORIGINATING ... Many thanks for any pointers. I'm also a bit confused on how to test it, really, short of connecting with a regular email client (mutt, thunderbird, etc.). If there are more appropriate tools that I've missed, I'm quite open to pointers. -- Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255 http://p27.eu/jeff/ http://transport-nantes.com/

2 2

New dovecot server, authentication confusion
by Jeff Abrahamson 24 Jan '21

24 Jan '21

I've set up a new dovecot+postfix instance with virtual (not system) users. I've a few questions, mostly about auth. I /think/ that postfix handles auth by asking dovecot. Users need to provide user + password to send (smtps) and receive (imaps). I see where I've configured this for dovecot, which is /etc/dovecot/passwd.db. That file contains lines like this: jeff@mobilitains.fr:{BLF-CRYPT}$2y$05$c... What concerns me is that I see occasional log items like this: Jan 24 11:26:33 nantes-m1 postfix/smtpd[4597]: fatal: no SASL authentication mechanisms (Also, I can't connect with thunderbird.) But I think I've configured SASL auth, so I'm not sure what to look at / how to debug this. I'm looking for suggestions how to approach this. I do not see how postfix knows who is allowed to connect, however. Am I correct that postfix delegates SASL to dovecot? This is the relevant config, I think: [T] jeff@nantes-m1:log $ doveconf -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-64-generic x86_64 Ubuntu 20.04.1 LTS # Hostname: nantes-m1.p27.eu auth_verbose = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = username_format=%u scheme=blf-crypt /etc/dovecot/passwd.db driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /var/mail/vmail/sieve-after sieve_before = /var/mail/vmail/sieve-before sieve_dir = ~/sieve } protocols = " imap" ssl = required ssl_cert = </etc/letsencrypt/live/nantes-m1.p27.eu/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 { args = uid=4000 gid=4000 home=/var/mail/vmail/%d/%n driver = static } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster@{{ primary_domain }} quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags mail_max_userip_connections = 20 } [T] jeff@nantes-m1:log $ [T] jeff@nantes-m1:log $ postconf -n | grep -i sasl broken_sasl_auth_clients = yes smtpd_recipient_restrictions = reject_unknown_client_hostname,reject_unknown_sender_domain,reject_unknown_recipient_domain,permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination,reject_invalid_hostname,reject_non_fqdn_sender smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot [T] jeff@nantes-m1:log $ postconf -Mf smtp inet n - y - - smtpd submission inet n - y - - smtpd -o syslog_name=postfix/submission -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions= -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o milter_macro_daemon_name=ORIGINATING smtps inet n - y - - smtpd -o syslog_name=postfix/smtps -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_reject_unlisted_recipient=no -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions= -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o milter_macro_daemon_name=ORIGINATING ... Many thanks for any pointers. I'm also a bit confused on how to test it, really, short of connecting with a regular email client (mutt, thunderbird, etc.). If there are more appropriate tools that I've missed, I'm quite open to pointers. -- Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255 http://p27.eu/jeff/ http://transport-nantes.com/

1 0

Massive /tmp files
by MRob 22 Jan '21

22 Jan '21

Hello, I just found user who has single folder (standard maildir format) that filled with over 8mil files and 800GB in the /tmp subdirectory of that folder: /email/domain/username/.Folder/tmp The files in there are normal maildir email files. I think the dir ran out of inode space so its not ongoing problem. My question is only can I purge that folder without breaking something more? If it tries to re-fill again I will try to debug Thankyou!!

5 8

[BUG REPORT] In some cases dovecot sends (huge) binary data to solr for indexing
by Alexey Panov 21 Jan '21

21 Jan '21

In some cases (exact condition still unknown) dovecot sends binary data (attachments) to SOLR for indexing. This reduces index and overall FTS efficiency dramatically. In extreme condition (below an example of 20MB) dovecot’s hardwired timeout of 60s gets triggered during HTTP exchange with SOLR on just a single file. This results in an unfinished index which, by initial indexing, gets restarted over and over. With multiple affected mailboxes even on moderate usage this can cause an IO overload of the whole system. Message example (doveadm fetch text): https://filebin.ca/5oy5Wc1QrBK3/fetch-text.obfuscated.txt <https://filebin.ca/5oy5Wc1QrBK3/fetch-text.obfuscated.txt> Corresponding raw log data: https://filebin.ca/5oy6yqLSCr3H/rawlog.obfuscated.txt <https://filebin.ca/5oy6yqLSCr3H/rawlog.obfuscated.txt> (Both files were processed with perl doveadm-obfuscate.pl <https://www.dovecot.org/tools/doveadm-obfuscate.pl>; the script doesn’t replace non-latin characters so they were replaced with ‘R’ manually) Workaround: there is a useful patch by John Fawcett <https://www.mail-archive.com/dovecot@dovecot.org/msg82296.html> that allows to set the FTS indexing message body maximum size. It works perfectly, but affected messages are getting completely ignored by FTS. This bug report is a summarised result of this discussion <https://www.mail-archive.com/dovecot@dovecot.org/msg82599.html>.

2 1

Deliver to different namespace with address detail
by Tobia Grosselle [ Terralink ] 21 Jan '21

21 Jan '21

Hello, with this settings: Dovecot 2.3.7.2 (3c910f64b) namespace { list = yes type = private inbox = yes prefix = INBOX/ separator = / } namespace Archive { list = yes type = private inbox = no prefix = Archive/ separator = / mailbox Incoming { auto = create } } lmtp_save_to_detail_mailbox = yes recipient_delimiter = + userdb_query = SELECT accounts.username AS user, accounts.home AS home, CONCAT('mdbox:', accounts.home, '/mdbox') AS mail, CONCAT('mdbox:', accounts.home, '/archive') AS 'namespace/Archive/location', 'vmail' AS uid, 'vmail' as gid FROM accounts WHERE accounts.username = '%u' it is possible to deliver an email to Archive namespace instead of inbox with address detail (email+Archive/Incoming@domain)? If i try i see that the lmtp service search the path from the inbox namespace (so INBOX/Archive/Incoming). Thanks

2 2

Sieve fileinto :create is failing
by Ron Garret 21 Jan '21

21 Jan '21

I’m trying to get a sieve script to move messages into a folder, and to create that folder if it doesn’t already exist. I’m following the example code at: https://doc.dovecot.org/configuration_manual/sieve/examples/ and doing this: > require ["fileinto", "mailbox”]; > … > fileinto :create “myfolder”; > … That results in this error in the log file: error: unknown tagged argument ':create' for the fileinto command What am I doing wrong? rg

4 8

Where does sieve store its "vacation" state?
by Ron Garret 21 Jan '21

21 Jan '21

Pigeonhole/sieve has a “vacation” feature that keeps track of which addresses it has sent messages to already so it doesn’t send too many. The state for this feature seems to survive a dovecot restart, so it must be persistent somewhere and not just stored in RAM. But I don’t recall configuring any place where that state would reside. So where is it? rg

2 1

Mail crypt plugin with HSM
by Dima Kovalyov 21 Jan '21

21 Jan '21

Hello Dovecot developers, I'm using a mail-crypt plugin to perform encryption at rest using per user keys encrypted with their password. Great plugin and I really appreciate it's continuous development and improvement. I have a question regarding mail-crypt keys being stored in HSM. Is it possible? I'm almost sure I've seen some discussion about usage of PKCS#11 in mail-crypt but can't find it in the mailing list. Please advise. Thanks! - Dima

1 0

Timeout/Event leak
by Lefteris Tsintjelis 20 Jan '21

20 Jan '21

Hi, any idea what all this is? Jan 19 18:23:00 master: Warning: Killed with signal 15 (by pid=33729 uid=0 code=kill) Jan 19 18:23:03 config: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Jan 19 18:23:03 stats: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Jan 19 18:23:03 auth: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Jan 19 18:23:03 auth: Warning: Timeout leak: 0x1059ce0 (auth-request-handler.c:617) Jan 19 18:23:03 auth: Warning: Timeout leak: 0x1059ce0 (auth-request-handler.c:617) Jan 19 18:23:03 auth: Warning: Timeout leak: 0x1059ce0 (auth-request-handler.c:617) Jan 19 18:23:03 auth: Warning: Timeout leak: 0x1059ce0 (auth-request-handler.c:617) Jan 19 18:23:03 auth: Warning: Timeout leak: 0x1059ce0 (auth-request-handler.c:617) Jan 19 18:23:03 auth: Warning: Timeout leak: 0x1059ce0 (auth-request-handler.c:617) Jan 19 18:23:03 auth: Warning: Timeout leak: 0x1059ce0 (auth-request-handler.c:617) Jan 19 18:23:03 auth: Warning: Timeout leak: 0x1059ce0 (auth-request-handler.c:617) Jan 19 18:23:03 auth: Warning: Timeout leak: 0x1059ce0 (auth-request-handler.c:617) Jan 19 18:23:03 auth: Warning: Timeout leak: 0x1059ce0 (auth-request-handler.c:617) Jan 19 18:23:03 auth: Warning: Event 0x120f0020 leaked (parent=0x120ecc20): auth-request.c:621 Jan 19 18:23:03 auth: Warning: Event 0x120ece20 leaked (parent=0x120ecc20): auth-request.c:111 Jan 19 18:23:03 auth: Warning: Event 0x120ecc20 leaked (parent=0x120ca620): auth-request.c:110 Jan 19 18:23:03 auth: Warning: Event 0x120eca20 leaked (parent=0x120ec620): auth-request.c:621 Jan 19 18:23:03 auth: Warning: Event 0x120ec820 leaked (parent=0x120ec620): auth-request.c:111 Jan 19 18:23:03 auth: Warning: Event 0x120ec620 leaked (parent=0x120b8620): auth-request.c:110 Jan 19 18:23:03 auth: Warning: Event 0x120ec220 leaked (parent=0x1207ee20): auth-request.c:667 Jan 19 18:23:03 auth: Warning: Event 0x120ec020 leaked (parent=0x1207ee20): auth-request.c:111 Jan 19 18:23:03 auth: Warning: Event 0x1207ee20 leaked (parent=0x12087220): auth-request.c:110 Jan 19 18:23:03 auth: Warning: Event 0x1207ec20 leaked (parent=0x1207e820): auth-request.c:667 Jan 19 18:23:03 auth: Warning: Event 0x1207ea20 leaked (parent=0x1207e820): auth-request.c:111 Jan 19 18:23:03 auth: Warning: Event 0x1207e820 leaked (parent=0x12087220): auth-request.c:110 Jan 19 18:23:03 auth: Warning: Event 0x1207e620 leaked (parent=0x1207e220): auth-request.c:621 Jan 19 18:23:03 auth: Warning: Event 0x1207e420 leaked (parent=0x1207e220): auth-request.c:111 Jan 19 18:23:03 auth: Warning: Event 0x1207e220 leaked (parent=0x120ca620): auth-request.c:110 Jan 19 18:23:03 auth: Warning: Event 0x1207e020 leaked (parent=0x120ada20): auth-request.c:621 Jan 19 18:23:03 auth: Warning: Event 0x120adc20 leaked (parent=0x120ada20): auth-request.c:111 Jan 19 18:23:03 auth: Warning: Event 0x120ada20 leaked (parent=0x120ad820): auth-request.c:110 Jan 19 18:23:03 auth: Warning: Event 0x120ad820 leaked (parent=0x12087220): auth-client-connection.c:338 Jan 19 18:23:03 auth: Warning: Event 0x120ad220 leaked (parent=0x120b8a20): auth-request.c:621 Jan 19 18:23:03 auth: Warning: Event 0x120ad020 leaked (parent=0x120b8a20): auth-request.c:111 Jan 19 18:23:03 auth: Warning: Event 0x120b8a20 leaked (parent=0x120ca620): auth-request.c:110 Jan 19 18:23:03 auth: Warning: Event 0x120b8420 leaked (parent=0x120cac20): auth-request.c:621 Jan 19 18:23:03 auth: Warning: Event 0x120cae20 leaked (parent=0x120cac20): auth-request.c:111 Jan 19 18:23:03 auth: Warning: Event 0x120cac20 leaked (parent=0x120caa20): auth-request.c:110 Jan 19 18:23:03 auth: Warning: Event 0x120caa20 leaked (parent=0x12087220): auth-client-connection.c:338 Thank you

2 2

Dovecot Gmail OAuth2.0 Setting Question
by 福田泰葵 19 Jan '21

19 Jan '21

Dear Sir or Madam Unable to build OAuth2.0 authentication to Gmail using dovecot as proxy. I have a question about how to use dovecot as a proxy to perform OAuth 2.0 authentication to Gmail using a mail client. 1. Is the following all I need to do to authenticate to Gmail using dovecot as a proxy? - passdb passdb { driver = oauth2 mechanisms = oauthbearer xoauth2 args = /etc/dovecot/dovecot-oauth2.token.conf.ext } passdb { driver = oauth2 mechanisms = plain login args = /etc/dovecot/dovecot-oauth2.plain.conf.ext } - create dovecot-oauth2.token.conf.ext and dovecot-oauth2.plain.conf.ext - create gmail service account api 2. grant_url in dovecot-oauth2.token.conf.ext and dovecot-oauth2.plain.conf.ext is URL for obtaining a Google access token for a web server that I have built myself? 3. I use a Gmail service account, so I don’t need a client ID and secret ID, right? 4. Do I set introspection_url to the URL of my own web server with the access token used for authentication to Google as the response? 5. The documentation says “pass_attrs = host=127.0.0.1”, but if you are authenticating to Gmail, I should use “pass_attrs = proxy=y host=%{if;%s;eq;imap;imap.gmail.com;%{if;%s;eq;pop3;smtp .gmail.com;pop.gmail.com}} port=%{if;%s;eq;imap;993;%{if;%s;eq;pop3;587;465}} proxy_mech=xoauth2 pass=%{oauth2:access_token} user=%{oauth2:email oauth2:email}”? 6. What is the difference between dovecot-oauth2.token.conf.ext and dovecot-oauth2.plain.conf.ext ? Do I need to configure both? I used https://doc.dovecot.org/configuration_manual/authentication/oauth2/#proxy as a reference. I would appreciate your reply. Yours faithfully, ------------------------------ e-mail: taiki.fukuda(a)justsystems.com TEL: 03-5324-7900 mobile: 080-6198-7328 ------------------------------

1 0

dovecot 2.3.13 : make check FAILURE : Assert failed: buffer_append_full_file
by J Lumby 19 Jan '21

19 Jan '21

After successfully building dovecot 2.3.13 (linux kernel 5.10.1 , glibc-2.32 , gcc-9.3) make check had one failure as follows : test-buffer-istream.c:54: Assert failed: buffer_append_full_file(result, TEST_FILENAME, SIZE_MAX, &error) == BUFFER_APPEND_READ_ERROR test-buffer-istream.c:56: Assert failed: error != NULL && *error != '\0' buffer_append_full_file .............................................. : FAILED After a brief look at the referenced code in test-buffer-istream.c , I can't find out what this FAIL really means or whether it is serious. The assert is finding that the result of the call to buffer_append_full_file is not BUFFER_APPEND_READ_ERROR, but it does not report what the result code actually was. Maybe errno was actually 0 and call succeeded? I don't know. Nor can I see how to add some code to find out. Can anyone offer any advice on what this means and/or how to investigate? Cheers, John Lumby

2 6

Changing the default delivery mailbox to something other than INBOX
by Ron Garret 18 Jan '21

18 Jan '21

Is there an easy way (i.e. a built-in configuration setting) to change the name of the mailbox that the dovecot LDA delivers mail into? The default is INBOX but I’d like mail to be delivered to some other mailbox. The reason for this is that I want all incoming mail to be invisible to the user by default until it has been screened for viruses and spam. I know I could do this with Sieve, but that is a PITA. More details in case anyone is interested: The goal of this filter is to make it work with very little training. To bootstrap the process, the filter is given access to outgoing mail (via a milter) which it uses as a reliable training corpus for good messages. It then leverages that information to filter incoming messages. For example, messages from senders which have been the recipients of outgoing messages are presumed to be good. There is also a spam honeypot to provide a reliable spam corpus. One of the heuristics I want to use is to look for the same subject line in multiple messages from unknown users received over a period of an hour or so because those are almost invariably spam. But that requires a time delay between when a message is received and when it is filtered, and that in turn requires a place to store messages for a while before they are processed. While they are in that temporary storage, I don’t want them in the user’s face, but I do want them to be accessible if the user wants to see them (e.g. if they know that an important message is coming in which may be stuck in the temp storage). So I’d like to make something like an INCOMING mailbox where all mail is delivered. The messages in INCOMING are scanned by the filter and moved to Junk or INBOX as appropriate. Thanks, rg

3 12

mbox to pst advice
by Marc Roos 18 Jan '21

18 Jan '21

Anyone an idea how to convert mbox ot pst on linux?

3 6

fts_solr: Indexing failed (fails on particular messages/mailboxes by timeout)
by Alexey Panov 18 Jan '21

18 Jan '21

Hello, I am running recent dovecot 2.3.13 (89f716dc2) within dockerized mailcow setup. During just another update routine I decided to reindex all mailboxes and some of them fail (timeout) on exactly SAME messages in SAME mailboxes: > doveadm(u@d): Error: fts_solr: Indexing failed: Request timed out (Request queued 73.213 secs ago, 1 send attempts in 73.098 secs, 60.597 in http ioloop, 0.000 in other ioloops, connected 127.875 secs ago) > doveadm(u@d): Error: Mailbox Sent: Mail search failed: Internal error occurred. Refer to server log for more information. [2021-01-14 11:23:46] > doveadm(u@d): Error: Mailbox Sent: Transaction commit failed: FTS transaction commit failed: backend deinit This error is persistent and affects only some, but always same folders of same mailboxes (i mean solr can't finish indexing them at all). I/O is in perfect condition and has no corruptions. I also tried to do fts rescan which made no change. RAM is fine, I haven't seen OOM conditions. During my research I found this discussion <https://www.mail-archive.com/dovecot@dovecot.org/msg76944.html> which lead me idea of reducing the batch_size to as low as 10 (for testing purposes). Observing SOLR logs during reindexing on the mailbox/folder causing the error I noticed the following strange behaviour. Firstly, it goes very fast but then always kinda freezes on these messages: > solr-mailcow_1 | 2021-01-14 16:05:09.615 INFO (qtp524223214-1151) [ x:dovecot-fts] o.a.s.u.p.LogUpdateProcessorFactory [dovecot-fts] webapp=/solr path=/update params={}{add=[6883/78a0ec27b091da5e4054000013681708/u@d (1688878773188952064), 6884/78a0ec27b091da5e4054000013681708/u@d (1688878773203632128), 6885/78a0ec27b091da5e4054000013681708/u@d (1688878773218312192), 6886/78a0ec27b091da5e4054000013681708/u@d (1688878773227749376), 6887/78a0ec27b091da5e4054000013681708/u@d (1688878773237186560), 6888/78a0ec27b091da5e4054000013681708/u@d (1688878773244526592), 6889/78a0ec27b091da5e4054000013681708/u@d (1688878773250818048), 6890/78a0ec27b091da5e4054000013681708/u@d (1688878773259206656), 6891/78a0ec27b091da5e4054000013681708/u@d (1688878773272838144), 6892/78a0ec27b091da5e4054000013681708/u@d (1688878773288566784)]} 0 101 > solr-mailcow_1 | 2021-01-14 16:06:42.540 INFO (qtp524223214-1143) [ x:dovecot-fts] o.a.s.u.p.LogUpdateProcessorFactory [dovecot-fts] webapp=/solr path=/update params={}{add=[6893/78a0ec27b091da5e4054000013681708/u@d (1688878773329461248), 6894/78a0ec27b091da5e4054000013681708/u@d (1688878773332606976), 6895/78a0ec27b091da5e4054000013681708/u@d (1688878774361260032), 6896/78a0ec27b091da5e4054000013681708/u@d (1688878850290745344), 6897/78a0ec27b091da5e4054000013681708/u@d (1688878851347709952), 6898/78a0ec27b091da5e4054000013681708/u@d (1688878852404674560), 6899/78a0ec27b091da5e4054000013681708/u@d (1688878853586419712), 6900/78a0ec27b091da5e4054000013681708/u@d (1688878870704422912), 6901/78a0ec27b091da5e4054000013681708/u@d (1688878870709665792), 6902/78a0ec27b091da5e4054000013681708/u@d (1688878870727491584)]} 0 92891 It takes almost one and a half minute to get those ten messages (6893-6902) indexed. It freezes exactly on that position every time I restart indexing. Actually only reducing the batch_size to 10 made it through. It was timing out with the default batch_size exactly here each time. Than it goes further again blazing fast until it reaches here: > solr-mailcow_1 | 2021-01-14 16:07:26.148 INFO (qtp524223214-1151) [ x:dovecot-fts] o.a.s.u.p.LogUpdateProcessorFactory [dovecot-fts] webapp=/solr path=/update params={}{add=[7443/78a0ec27b091da5e4054000013681708/u@d (1688878884286627840), 7444/78a0ec27b091da5e4054000013681708/u@d (1688878884293967872), 7445/78a0ec27b091da5e4054000013681708/u@d (1688878884304453632), 7446/78a0ec27b091da5e4054000013681708/u@d (1688878884502634496), 7447/78a0ec27b091da5e4054000013681708/u@d (1688878900331937792), 7448/78a0ec27b091da5e4054000013681708/u@d (1688878900508098560), 7449/78a0ec27b091da5e4054000013681708/u@d (1688878916409753600), 7450/78a0ec27b091da5e4054000013681708/u@d (1688878916424433664), 7451/78a0ec27b091da5e4054000013681708/u@d (1688878916438065152), 7452/78a0ec27b091da5e4054000013681708/u@d (1688878916448550912)]} 0 30682 > solr-mailcow_1 | 2021-01-14 16:09:40.277 INFO (qtp524223214-1325) [ x:dovecot-fts] o.a.s.u.p.LogUpdateProcessorFactory [dovecot-fts] webapp=/solr path=/update params={}{add=[7463/78a0ec27b091da5e4054000013681708/u@d (1688879057103486976)]} 0 1 > solr-mailcow_1 | 2021-01-14 16:10:00.628 INFO (qtp524223214-1009) [ x:dovecot-fts] o.a.s.u.p.LogUpdateProcessorFactory [dovecot-fts] webapp=/solr path=/update params={}{add=[7453/78a0ec27b091da5e4054000013681708/u@d (1688878916486299648), 7454/78a0ec27b091da5e4054000013681708/u@d (1688878916489445376), 7455/78a0ec27b091da5e4054000013681708/u@d (1688878916496785408), 7456/78a0ec27b091da5e4054000013681708/u@d (1688878917584158720), 7457/78a0ec27b091da5e4054000013681708/u@d (1688878994974310400), 7458/78a0ec27b091da5e4054000013681708/u@d (1688879073177108480), 7459/78a0ec27b091da5e4054000013681708/u@d (1688879074234073088), 7460/78a0ec27b091da5e4054000013681708/u@d (1688879075288940544), 7461/78a0ec27b091da5e4054000013681708/u@d (1688879076339613696), 7462/78a0ec27b091da5e4054000013681708/u@d (1688879077392384000)]} 0 154455 This results in the following error on the console where I start reindexing: > $ docker-compose exec dovecot-mailcow doveadm index -u u@d 'Sent' > doveadm(u@d): Error: fts_solr: Indexing failed: Request timed out (Request queued 134.122 secs ago, 1 send attempts in 134.098 secs, 131.923 in http ioloop, 0.000 in other ioloops, connected 376.408 secs ago) > doveadm(u@d): Error: Mailbox Sent: Mail search failed: Internal error occurred. Refer to server log for more information. [2021-01-14 17:09:40] > doveadm(u@d): Error: Mailbox Sent: Transaction commit failed: FTS transaction commit failed: backend deinit The last message about indexed block of ten messages (2021-01-14 16:10:00.628 7453-7462) arrives already after reindexing error on the other console occurs and doveadm exits. Interestingly, exactly at the time mentioned in the error message (2021-01-14 17:09:40, i.e. 16:06:40 - I don’t know why timezone differs) a message about indexing of a single message 7463 arrives (which is actually NEXT message to the block that gets indexed 20 seconds later). The whole mailbox consists of 8530 messages and doveadm/solr can’t finish indexing it at all starting over and over. Can you please help me understanding the reason of this behaviour? P.S. Is there any possibility to determine what message in vmail maildir corresponds to solr log, e.g. to 7463/78a0ec27b091da5e4054000013681708/u@d (1688879057103486976) ? Thanks, Programmierus

2 4

Additional custom fields in map dict with static values.
by Mimiko 17 Jan '21

17 Jan '21

Hello. Dovector version 2.2.27. How can I add custom fields in the map for the last_login. For example: map { pattern = shared/last_login/imap/$user/$client_ip table = users_last_login value_field = last_login_imap_int value_type = string fields { userid = $user last_login_client_ip_imap = $client_ip custom_field_name = some_static_value } }

1 0

Antispam plugin
by Maciej Milaszewski 17 Jan '21

17 Jan '21

Hi System centos8 + dovecot-2.3.8 from repo # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-193.19.1.el8_2.x86_64 x86_64 CentOS Linux release 8.2.2004 (Core) I need "Antispam plugin". What antispam-plugin I must use ? In older version dovecot-2.2.36.4 i use "dovecot-antispam-plugin" but in centos I had a problem with configure - probably toold wersion "./configure: line 3193: DC_DOVECOT: command not found" In wiki dovect is "antispam-plugin" I try this http://hg.dovecot.org/dovecot-antispam-plugin but get 404 Backand spamassassin

4 3

Re: dovecot 2.3.13 : make check FAILURE : Assert failed: buffer_append_full_file
by steve＠keptprivate.com 16 Jan '21

16 Jan '21

I was experiencing multiple failures with make check on a fresh installation of CentOS 8.3.The solution for me was to use mock instead of rpmbuild. (I was not building as root with rpmbuild.) With mock all tests were successful. Sent from my T-Mobile 4G LTE device------ Original message------From: J LumbyDate: Sat, Jan 16, 2021 11:31 AMTo: dovecot(a)dovecot.org;Cc: Subject:dovecot 2.3.13 : make check FAILURE : Assert failed: buffer_append_full_fileAfter successfully building dovecot 2.3.13 (linux kernel 5.10.1 , glibc-2.32 , gcc-9.3) make check had one failure as follows : test-buffer-istream.c:54: Assert failed: buffer_append_full_file(result, TEST_FILENAME, SIZE_MAX, &error) == BUFFER_APPEND_READ_ERROR test-buffer-istream.c:56: Assert failed: error != NULL && *error != '\0' buffer_append_full_file .............................................. : FAILED After a brief look at the referenced code in test-buffer-istream.c , I can't find out what this FAIL really means or whether it is serious. The assert is finding that the result of the call to buffer_append_full_file is not BUFFER_APPEND_READ_ERROR, but it does not report what the result code actually was. Maybe errno was actually 0 and call succeeded? I don't know. Nor can I see how to add some code to find out. Can anyone offer any advice on what this means and/or how to investigate? Cheers, John Lumby

1 0

outlook 2019 imap folder subscription
by Alexander Rivanykov 16 Jan '21

16 Jan '21

1 0

The use of %w in password_query leads to "Failed to expand plugin setting" error
by Filidor Wiese 16 Jan '21

16 Jan '21

Hi, I'm trying to convert my existing users to a more modern password scheme by following the how-to at https://wiki.dovecot.org/HowTo/ConvertPasswordSchemes. One of the steps is to include the use of '%w' in the password_query, like so: password_query = \ SELECT domain, password, '%w' AS userdb_plain_pass, \ domain as userdb_domain, concat('*:storage=', quota) AS userdb_quota_rule, 5000 as userdb_uid, 5000 as userdb_gid, '/home/%d/%n' as userdb_home \ FROM users WHERE (catch='%n' AND domain='%d') and also to configure: userdb { driver = prefetch } in order to combine the user/password_query into one. Now that all seemed to work well, except for one thing. When a user has a % sign in their password, the following error occurs: Error: Failed to expand plugin setting plain_pass = 'Tfew3322gYEp$%5Qjk0': Unknown variable '%Q' Which indicates that dovecot is trying to expand variables in the password. As a consequence, the login process fails. Is there some way around this behavior? Thanks in advance, Filidor Wiese

4 5