- dovecot - dovecot.org

doveadm rebuild: Failed to add attachment keywords
by Patrick Ben Koetter 27 Mar '20

27 Mar '20

Greetings, I'm using the current dovecot release 2.3.10 and I try to rebuild mailboxes with broken attachment paths. When I run this command: doveadm rebuild attachments -u user(a)example.com ALL I runs fine for 6199 of 6223 messages and fails then at message 6200 with this message: doveadm(user(a)example.com): Error: Mailbox INBOX: UID=6200: read(attachments-connector(/MailStore/mail/mailboxes/CFEE0E67-6269-4AD3-8DED-6AB71A8E4BD7/dbox/mailboxes/INBOX/dbox-Mails/u.6200)) failed: read(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200[base64:19 b/l]) failed: open(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200) failed: No such file or directory (read reason=) doveadm(user(a)example.com): Error: Mailbox INBOX: UID=6200: read(attachments-connector(/MailStore/mail/mailboxes/CFEE0E67-6269-4AD3-8DED-6AB71A8E4BD7/dbox/mailboxes/INBOX/dbox-Mails/u.6200)) failed: read(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200[base64:19 b/l]) failed: open(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200) failed: No such file or directory (read reason=) doveadm(user(a)example.com): Error: Mailbox INBOX: UID=6200: Failed to add attachment keywords: mail_get_parts() failed: Mailbox INBOX: UID=6200: read(attachments-connector(/MailStore/mail/mailboxes/CFEE0E67-6269-4AD3-8DED-6AB71A8E4BD7/dbox/mailboxes/INBOX/dbox-Mails/u.6200)) failed: read(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200[base64:19 b/l]) failed: open(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200) failed: No such file or directory (read reason=) 6200 error Assuming the attachments are still there, what would I need to do to 'fix' that? And if I can't fix it, can 'rebuild' skip the error and go on rebuilding the rest? TIA, p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

2 1

Deliver log with "msgid=?" when email come from Exchange/Office 365
by Alessio Cecchi 27 Mar '20

27 Mar '20

Hi, I noticed that all emails that come from Exchange/Office 365 have the message-id, in deliver log, reported as msgid=? <DBBPRDD0(a)DBBPR023.eurprd08.prod.outlook.com> instead of expected msgid=<DBBPRDD0(a)DBBPR023.eurprd08.prod.outlook.com> My deliver_log format is: deliver_log_format = deliverytime=%{delivery_time}, msgid=%m, sender=%e, from=%f, subject="%s": %$ The behaviour is the same on Dovecot 2.2 and 2.3, and only dovecot have the "?", we have a mail filter before dovecot and the message-id is registred fine, without the ? in front. Is an issue of my setup or a bug in dovecot? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

1 0

Not able to start dovecot
by Adam Raszkiewicz 26 Mar '20

26 Mar '20

Freshly compiled dovecot 2.3.9.3 on Centos 7 for some reason not able to start sudo systemctl status dovecot.service ● dovecot.service - LSB: Starts the Dovecot POP3/IMAP service Loaded: loaded (/etc/rc.d/init.d/dovecot; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2020-03-18 16:32:17 UTC; 15s ago Docs: man:systemd-sysv-generator(8) Process: 2868 ExecStart=/etc/rc.d/init.d/dovecot start (code=exited, status=127) Mar 18 16:32:17 systemd[1]: Starting LSB: Starts the Dovecot POP3/IMAP service... Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 34: log_info_msg: command not found Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 35: start_daemon: command not found Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 36: evaluate_retval: command not found Mar 18 16:32:17 systemd[1]: dovecot.service: control process exited, code=exited status=127 Mar 18 16:32:17 systemd[1]: Failed to start LSB: Starts the Dovecot POP3/IMAP service. Mar 18 16:32:17 systemd[1]: Unit dovecot.service entered failed state. Mar 18 16:32:17 systemd[1]: dovecot.service failed. I have compiled the same code on Centos 6 and had no problem to run it. Any thoughts on that? Thanks, Adam

4 4

Understanding doveadm rebuild
by Patrick Ben Koetter 26 Mar '20

26 Mar '20

Greetings, I'm trying to understand if the doveadm rebuild command is suited to fix a problem we have on a customers platform. The customer uses sdbox in combination with SIS and for $REASONS dovecot cannot find the attachements anymore. They are there, but the references to them in the messages seem to be wrong. Is that what the rebuild subcommand has been made for? Will it e.g. scan the messages for attachment references and try to find them in the SIS storage location and then fix the references in messages? TIA, p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

1 0

At rest encryption (with protected crypto keys)
by Kees de Jong 25 Mar '20

25 Mar '20

Hi, As stated on the Dovecot documentation, at rest encryption is possible [1]. However, these keys are present on the system itself and are unprotected. Therefore, if a system is compromised, the attacker has access to the encrypted mail and the keys. There is no security benefit in that situation, except for hoping that the attacker doesn't understand that this is happening and how. Nextcloud does this a bit better. A key is used to encrypt user data as well [2]. However, that key is protected with the user's password. When the user logs in and requests data, the user's password unlocks the key and data can be read and written safely. This also takes into account password changes. Files don't need to be encrypted again, the encryption key is simply re-encrypted with the new user's password. How does the Dovecot community see this? Is at rest encryption needed in times of increased security and privacy problems? I think it is a must, just like 2FA, but that's a different story. I think the current possibility of at rest encryption is not well applied enough. Is this something that's on the agenda to improve? Or am I missing something? Is there a better way of doing this? [1] https://doc.dovecot.org/configuration_manual/mail_crypt_plugin/#mail-crypt-… [2] https://nextcloud.com/encryption/

2 1

dovecot-2.2.36-4 and antispam
by Maciej Milaszewski 24 Mar '20

24 Mar '20

Hi I use dovecot-2.2.36.4 on Debian 8.11 and plugin dovecot-antispam from http://johannes.sipsolutions.net/Projects/dovecot-antispam All works fine but in roundcube i get two folder: Spam (real: Junk) and SPAM in sieve i have: require ["fileinto","imap4flags"]; # rule:[SPAM Box] if header :contains "X-Spam-Flag" "YES" { setflag "\\Seen"; fileinto "SPAM"; # ---> because dovecot-antispam need folder SPAM to teach spam or ham stop; } problem probably fixed when I change fileinto "SPAM"; to fileinto "Junk"; But plugin "dovecot-antispam" probably not working ... Maybe I think wrongly Can you recommend any other plugin that will work properly and teach spam with Junk for dovecot2.2.36-4 in dovecot: 15-mailboxes.conf: ....... mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox SPAM { special_use = \Junk } mailbox Trash { special_use = \Trash } .... 90-plugin.conf: ..... antispam_backend = MAILTRAIN #antispam_mail_sendmail_args = --for;%u 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*;wiadomo&AVs-ci-&AVs-mieci;kosz antispam_debug_target = syslog antispam_verbose_debug = 1 script to learn 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 -- Maciej Miłaszewski Starszy Administrator Systemowy IQ PL Sp. z o.o. Biuro Obsługi Klienta: e-mail: bok(a)iq.pl tel.: +48 58 326 09 90 - 94 fax: +48 58 326 09 99 Dział pomocy: https://www.iq.pl/pomoc Informacja dotycząca przetwarzania danych osobowych: https://www.iq.pl/kontakt IQ PL Sp. z o.o. z siedzibą w Gdańsku (80-298), ul. Geodetów 16, KRS 0000007725, Sąd rejestrowy: Sąd Rejonowy w Gdańsku VII Wydział KRS, kapitał zakładowy: 140.000 PLN, NIP 5832736211, REGON 192478853

3 2

imapc quota support
by Сергей Петренко 24 Mar '20

24 Mar '20

Hi, I use Dovecot 2.3.9.2 as IMAP proxy for other mail server and configure it with imapc_host/imapc_port/imapc_user options. All works fine exclude quota information. Although my IMAP server supported quota Dovecot does not relay it to users. As I read in docs/MailboxFormat.imapc.txt in Dovecot v2.2.30+ there is a way to relay quota data to end users: Quota ----- Using the "imapc" quota backend allows asking for the quota from remote IMAP server (v2.2.30+). By default it uses GETQUOTAROOT INBOX for getting the quota. There are also two parameters that can be used to control how the quota is looked up: * box=<mailbox>: Use GETQUOTAROOT <mailbox> * root=<name>: Use GETQUOTA <name> For example: ---%<------------------------------------------------------------------------- plugin { quota = imapc:root=User Quota } ---%<------------------------------------------------------------------------- The above example is not clear. Please advise how to configure Dovecot in IMAP proxy mode with quota support.

1 0

Question on pop3
by ratatouille 23 Mar '20

23 Mar '20

Hello! Email is stored as plain textfile in /var/mail/andreas. I assume this is mbox-format. I get the following in the log telneting to localhost: 2020-03-22 20:21:10 imap(andreas(a)dualbit.de): Error: chdir(/var/spool/mail/andreas) failed: Not a directory 2020-03-22 20:21:10 imap(andreas(a)dualbit.de): Error: Namespace '': Mail storage autodetection failed with home=/var/spool/mail/andreas 2020-03-22 20:21:10 imap(andreas(a)dualbit.de): Info: Namespace '': Mail storage autodetection failed with home=/var/spool/mail/andreas in=0 out=372 In case in the passwd-file I specify userdb_mail=mbox:/var/mail/andreas:INBOX=/var/mail/%n I see: 2020-03-22 20:31:00 imap(andreas(a)dualbit.de): Error: chdir(/var/spool/mail/andreas) failed: Not a directory 2020-03-22 20:31:00 imap(andreas(a)dualbit.de): Error: Namespace '': mbox: mbox root directory can't be a file: /var/mail/andreas (http://wiki2.dovecot.org/MailLocation/Mbox) How can I make this work? Regards Andreas

2 1

Problem with mail_uid
by ratatouille 23 Mar '20

23 Mar '20

Hello! I have problems fetching mail for a system user. In use is a passwd-file. If I set (for virtual users) mail_uid = vmail mail_gid = vmail in 10-mail.conf, I get permission denied. 2020-03-23 18:39:23 imap(andreas(a)dualbit.de): Error: chdir(/home/andreas/Maildir/) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +x perm: /home/andreas/Maildir, dir owned by 5006:5006 mode=0700) The mailbox has permissions drwx------. 9 andreas susers If I don't set mail_uid I get an error because of missing mail_uid. I can only access the users mailbox if I set mail_uid = 5006 in 10-mail.conf On another system I don't haver this problem. I made diffs, read alot of stuff and can't find a solution. What is the way to go, please? I would like to know why this does not work. Below my doveconf -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 3.10.0-1062.9.1.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) # Hostname: dualbit1.dualbit.de auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain cram-md5 auth_verbose = yes auth_verbose_passwords = yes debug_log_path = /var/log/dovecot-debug disable_plaintext_auth = no first_valid_uid = 1000 listen = *,[::] log_path = /var/log/dovecot log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = vmail mail_home = /home/%n/Maildir mail_location = maildir:~/ mail_plugins = " quota" mail_privileged_group = vmail mail_uid = 5006 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4fl ags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot-sql.conf driver = sql } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { quota = dict:user::file:/var/vmail/%d/%n/.quotausage sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } user = root } service imap-login { client_limit = 1000 process_limit = 500 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv3 userdb { driver = prefetch } userdb { args = /etc/dovecot-sql.conf driver = sql } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota postmaster_address = root@localhost } protocol lmtp { mail_plugins = quota sieve } Any help appreciated. Andreas

2 3

imapc master login for shared mailboxes
by Mark Zealey 21 Mar '20

21 Mar '20

Hi there, I'm trying to set up shared mailboxes such that any access to the shared namespace like INBOX/shared/<sub-email-address> will take <current-user> and use imapc to log in with <sub-email-address>*<current-user> (ie the current user is the master account for imapc). I've set up like https://wiki2.dovecot.org/SharedMailboxes/ClusterSetup on centos8 latest dovecot build (a late 2.2 series version I believe. However I'm running in to a couple of issues: 1) setting imapc_master_user = %u has %u as <sub-email-address> rather than <current-user>. I can't find any sort of variable substitution that will allow me to access the details of <current-user>. From looking at the logs it seems to do a userdb lookup for<sub-email-address> to check it exists but then the substitutions appear to be using these rather than the current user's details 2) In a similar vein, I believe imapc_password = %w (ie trying to just get current user logging in with the password that was specified when they initially logged in, but as a master user) is also not substituting correctly and is just a blank string Is there any way around this so I don't have to worry about trying to do sharing based on the filesystem and the same process but rather just allow the main user to log in to any other account (in this case domain owner logging in to any accounts under their domain) ? Thanks Mark

1 0