- dovecot - dovecot.org

Welcome plugin - user and domain vars?
by Tony 31 Jul '18

31 Jul '18

Hi List, I have multiple mail domains and depending on the domain name was looking for a way to pass the user and domain into a welcome.sh script. I looked at the quota script and saw of the 3 vars one of them is for the user. BOUNDARY="$1" USER="$2" MSG="" For the username - could we still reference USER="$2" in order to pass the username in the welcome email or is this only supported with the quota plugin? For the domain - how could one pass the 1st time login user's mail domain to the script? I looked at the welcome-plugin.c source, but didn't find anything that might reference a domain. Ideally I was hoping maybe something similar to the quota script could work.. MSG="" if [[ "$DOMAIN" = "domain.net" ]]; then MSG="..." elif [[ "$DOMAIN" = "domain.com" ]]; then MSG="..." elif [[ "$DOMAIN" = "domain.me" ]]; then MSG="..." elif [[ "$DOMAIN" = "domain.email" ]]; then MSG="..." fi Thanks for any suggestions. Cheers, Tony

2 1

uid problem
by Andras Kemeny 31 Jul '18

31 Jul '18

hi, contacting this mailing list is my last-ditch effort to somehow come to a working configuration where postfix "ends in" dovecot, IE for special LDAP-based users, featured in the virtual mailbox delivery, dovecot would act as LDA. here's the deal. i've set up dovecot's access to the LDAP server, and for the purposes of being an IMAP server and a SASL auth backend, dovecot works brilliantly and without a glitch. i can access my test mailbox (in maildir format), i can use the LDA as root and it delivers the message correctly (after a switch to the target user's UID), and even postfix's submission works with dovecot as its SASL backend. what does not work is dovecot as LDA from postfix. i'm getting these errors in the log: Jul 31 03:40:40 rhyno dovecot: lda(aik): Error: user aik: Auth USER lookup failed Jul 31 03:40:40 rhyno dovecot: auth: Error: userdb(aik): client doesn't have lookup permissions for this user: userdb uid (10001) doesn't match peer uid (5000) (to bypass this check, set: service auth { unix_listener /var/run/dovecot/auth-userdb { mode=0777 } }) Jul 31 03:40:40 rhyno dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. for the sake of clarity, i've tried the "to bypass this check" instructions, didn't help. also, for the sake of operational clarity, "aik" is the LDAP account with the following parameters: dn: uid=aik,ou=People,dc=rhyno,dc=tech objectClass: account objectClass: posixAccount objectClass: postfixUser cn: aik uid: aik uidNumber: 10001 gidNumber: 10001 homeDirectory: /home/aik loginShell: /bin/sh gecos: aik description: User account structuralObjectClass: account entryUUID: db947584-0369-1038-98b3-675e2f0cea17 creatorsName: cn=admin,dc=rhyno,dc=tech createTimestamp: 20180613152616Z email: *********** userPassword:: ************************* mailacceptinggeneralid: andras.kemeny mailacceptinggeneralid: kemeny.andras mailacceptinggeneralid: aik mailacceptinggeneralid: pdx mailacceptinggeneralid: @rhyno.tech mailacceptinggeneralid: @rhynotechnologies.com maildrop: aik and postfix's master.cf says: dovecot unix - n n - - pipe flags=ODRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -e -f ${sender} -d ${user} so i'm stuck at this point. obviously, if the LDA is spawned with vmail:vmail perms, it cannot become uid 10001 (btw, the LDAP and passwd accounts were once connected, but for security reasons, the connection has been severed -- still the /home/aik/mail dir is owned by uid 10001 etc). what am i doint wrong? thanks, a

2 1

dovecot 2.3.x, ECC and wildcard certificates, any issues
by David Mehler 31 Jul '18

31 Jul '18

Hello, Does dovecot 2.3.x have any issues recognizing or using certificates that are ECC and wildcard? I'm trying to switch my letsencrypt implementation from acme-client which does not support either of those capabilities to acme.sh which does. Since then external clients checking their email has not worked. A manual telnet to mail.example.com 993 gives a connected message but then nothing no greeting or capabilities. The certificate is for example.com with an alt name of *.example.com if that's not right let me know, i'm not sure about that one, connecting to the web sites of these pages seems noticeably slower, I'm wondering if both of these issues aren't key related? Thanks. Dave.

5 12

mdbox_deleted proper syntax
by Johan Huldtgren 31 Jul '18

31 Jul '18

hello, on the wiki, https://wiki2.dovecot.org/MailboxFormat/dbox, it says that one can use either doveadm fetch or doveadm import, however I can find no correct syntax with fetch that'll actually work. Is the idea to simply override the mail_location with -o ? That seems to work for doveadm mailbox but not for doveadm fetch or search # doveadm -f table mailbox status -u johan all dovecot mailbox messages recent uidnext uidvalidity unseen highestmodseq vsize guid firstsaved dovecot 0 0 1 1362145026 0 1 164208086 64bd9f0003af305190040000b9256959 1471825482 # doveadm -f table -o "mail_location=mdbox_deleted:~/mdbox" mailbox status -u johan all dovecot mailbox messages recent uidnext uidvalidity unseen highestmodseq vsize guid firstsaved dovecot 0 0 1 0 0 1 0 ddb9421479f0595bf21b0100b9256959 18446744073709551615 # doveadm -f flow fetch -u johan size.virtual mailbox dovecot size.virtual=2869 size.virtual=2960 size.virtual=8023 size.virtual=6683 ... # # doveadm -f flow -o "mail_location=mdbox_deleted:~/mdbox" fetch -u johan size.virtual mailbox dovecot # # doveadm search -u johan mailbox dovecot subject "LMTP Log" 64bd9f0003af305190040000b9256959 8642 64bd9f0003af305190040000b9256959 21302 64bd9f0003af305190040000b9256959 21373 64bd9f0003af305190040000b9256959 21420 64bd9f0003af305190040000b9256959 21434 64bd9f0003af305190040000b9256959 21435 64bd9f0003af305190040000b9256959 21460 64bd9f0003af305190040000b9256959 21461 64bd9f0003af305190040000b9256959 21463 64bd9f0003af305190040000b9256959 23684 # doveadm -o "mail_location=mdbox_deleted:~/mdbox" search -u johan mailbox dovecot subject "LMTP Log" # What I'm really trying to accomplish is see if a mail which a user deleted still exists in mdbox_deleted, so I wanted to do a fetch / search to see and then try to copy / import that message back. This is on OpenBSD 6.3-current with dovecot 2.2.36, doveconf -n below. thanks, .jh --- # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: OpenBSD 6.3 amd64 # Hostname: www.example.com auth_mechanisms = plain login first_valid_gid = 0 first_valid_uid = 507 imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_id_log = * last_valid_uid = 1059 listen = 127.0.0.1 mail_home = /home/vmail/%d/%n mail_location = mdbox:~/mdbox mail_plugins = stats fts fts_solr mail_privileged_group = _dovecot mailbox_list_index = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext spamtest spamtestplus virustest mbox_write_locks = fcntl mmap_disable = yes namespace { inbox = yes location = mailbox spam { auto = subscribe special_use = \Junk } mailbox drafts { auto = subscribe special_use = \Drafts } mailbox sent-mail { auto = subscribe special_use = \Sent } mailbox trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-pgsql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-pgsql2.conf driver = sql } passdb { args = cache_key=%u%r%l * driver = bsdauth } plugin { antispam_backend = mailtrain antispam_mail_notspam = learn_ham antispam_mail_sendmail = /usr/local/bin/rspamc antispam_mail_sendmail_args = -h;127.0.0.1:11334;-P;q1 antispam_mail_spam = learn_spam antispam_spam = caughtspam antispam_trash = trash fts = solr fts_autoindex = yes fts_solr = url=http://127.0.0.1:8983/solr/dovecot/ recipient_delimiter = + sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/dovecot/sieve/before/ sieve_default = /var/dovecot/sieve/default.sieve sieve_extensions = +spamtest +spamtestplus +virustest sieve_spamtest_max_header = X-Spamd-Result: default: [[:alnum:]]+ \[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\] sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+ \[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\] sieve_spamtest_status_type = score sieve_virustest_status_header = X-Virus-Scan: Found to be (.+)\. sieve_virustest_status_type = text sieve_virustest_text_value1 = clean sieve_virustest_text_value5 = infected stats_refresh = 30 secs stats_track_cmds = yes } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = _postfix mode = 0666 user = _postfix } } service imap-login { inet_listener imaps { port = 993 ssl = yes } process_limit = 200 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = _postfix user = _postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service stats { fifo_listener stats-mail { mode = 0666 user = _postfix } } ssl = required ssl_cert = </etc/ssl/acme/example.com/fullchain.pem ssl_key = # hidden, use -P to show it userdb { args = uid=507 gid=507 driver = static } userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { mail_plugins = stats fts fts_solr sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = stats fts fts_solr antispam imap_stats }

2 2

Doveadm protocol; dovecot v2.2.10
by David White 31 Jul '18

31 Jul '18

Hi there, Just wondering what is considered current best practice for managing dovecot? The options I see are: Doveadm binary Doveadm protocol via socket Doveadm http protocol I’m currently on v2.2.10 and it appears the doveadm protocol command set is limited to just the “mailbox” commands and the http protocol hasn’t been implemented. Is the doveadm http protocol still experimental in v2.3.2? Thanks, David White ISP Engineer Trustpower T 021 223 6208 E david.white(a)trustpower.co.nz<mailto:david.white@trustpower.co.nz> Trustpower Limited, Private Bag 12023, Tauranga Mail Centre, Tauranga 3143 ------------------------------------------------------------------------------------ The contents of this email and any attachments are confidential and may be privileged. If you are not the intended recipient, you may not use, copy or disclose this email or its attachments. Please notify the sender immediately by e-mail if you have received this e-mail in error and delete both emails from your system. It is your responsibility to check this email and any attachments for viruses or other harmful code before opening or sending on. Trustpower Limited and its subsidiaries (collectively, Trustpower) accepts no responsibility for any such virus or any effects of a virus on your systems or data. Trustpower does not endorse anything in this email that is not related to its official business. Please think of the environment before printing this email. ------------------------------------------------------------------------------------

2 1

2.3.2.1 - ssl_alt_key revealed with dovecot -n
by ѽ҉ᶬḳ℠ 31 Jul '18

31 Jul '18

Seems like a minor cosmetic bug with [ dovecot -n ] ssl_alt_key = </etc/pki/private/some.key.pem ssl_key = # hidden, use -P to show it

1 0

Restricting SSL/TLS protocol versions on Dovecot 2.2.22
by J Doe 30 Jul '18

30 Jul '18

Hello, I have a question regarding SSL/TLS settings for Dovecot version 2.2.22. In: 10-ssl.conf there are two parameters: ssl_protocols ssl_cipher_list ssl_protocols is commented with “SSL protocol to use” and ssl_cipher_list is commented with “SSL ciphers to use”. If I want to disable SSLv3, for example, do I need to use both parameters or will disabling SSLv3 ciphers in ssl_cipher_list do the same thing ? So is: ssl_cipher_list = !SSLv3 …equivalent to: ssl_protocols = !SSLv3 ssl_cipher_list = !SSLv3 Thanks, - J

4 4

[Dovecot] quota-status not working in distributed environment
by Benoit Panizzon 30 Jul '18

30 Jul '18

Hello List Quick overview of our set-up: Postfix / Dovecot (2.2.2.1) / MySQL Cluster on (at the moment) three Servers to create a HA environment where you could easily add additional servers as the demand or load grows. Circular dovecot replication is used so each server uses another one as replication partner and allowing one server to fail. Dovecot Proxy Feature being used, so we can use round-robin DNS and each server can forward the connecting user to the correct 'master' for his mailbox. So far, everything works as expected. Now we want to reject emails to 'full' mailboxes during SMTP to prevent backscatter and use the quota-status policy service from within postfix. That works fine, if the mailbox or it's replica is present on the machine where quota-status is called, but it fails if it's run on a machine where neither the mailbox or the replica is present. In our case, we get a correct SMTP 550 'Mailbox Full' Reject in two cases and a LMTP generated bounce in the later case. Also `doveadm quota get -u user(a)example.com` return the correct quota if run on the two machines which have the mailbox and it's copy locale, but return 0% used if run on the other machine. Is there a way to get quota-status to also use the proxy feature to request the quota information from the correct machine? Or is the postfix policy daemon call to the quota-status socket documented somewhere (it must be, but where?) so we could implement it from within the Milter? (we use the sendmail Milter API from postfix to filter spam and viruses, do sender/recipient rewriting, forward bounce matching, rate limmiting, login/IP statistics to block botnets abusing phished addresses and legal intercept stuff anyway) Kind regards Benoit Panizzon -- I m p r o W a r e A G - ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 07 CH-4133 Pratteln Fax +41 61 826 93 02 Schweiz Web http://www.imp.ch ______________________________________________________

5 6

OT - copied maildir from 2T drive to 4T drive
by Marc Perkel 30 Jul '18

30 Jul '18

And it's taking up more space on the 4T drive. What did I miss?

2 1

[SOLR] Where is solr-schema.xml?
by Peter Nabbefeld 27 Jul '18

27 Jul '18

Hello, running dovecot 2.3.2.1 on Arch Linux, and installed solr 7.4.0. According to the wiki, there should be doc/solr-schema.xml, but I cannot find it. Tried "whereis dovecot": dovecot: /usr/bin/dovecot /usr/lib/dovecot /etc/dovecot /usr/include/dovecot /usr/share/dovecot /usr/share/man/man1/dovecot.1.gz But I cannot find any xml files using find /usr/{lib,share}/dovecot -name "*.xml" Kind regards Peter

4 5