- dovecot - dovecot.org

Problem with converting mdbox to MailDir
by Adam Raszkiewicz 03 Oct '19

03 Oct '19

I have a problem to convert mdbox to MailDir. Log from that process looks like: /bin/dsync -Dv -u user(a)domian.com mirror maildir:/tmp/destination/mailboxes/user@domian.com Debug: Loading modules from directory: /lib/dovecot Debug: Module loaded: /lib/dovecot/lib01_acl_plugin.so Debug: Loading modules from directory: /lib/dovecot/doveadm Debug: Module loaded: /lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_lookup (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Debug: Module loaded: /lib/dovecot/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_list_backend (this is usually intentional, so just ignore this message) doveadm(user(a)domian.com): Debug: Effective uid=503, gid=503, home=/var/mailboxes/%2Mu/%2.2Mu/%u doveadm(user(a)domian.com): Debug: Home dir not found: /var/mailboxes/%2Mu/%2.2Mu/%u doveadm(user(a)domian.com): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:/var/mailboxes/64/b1/user@domian.com doveadm(user(a)domian.com): Debug: fs: root=/var/mailboxes/64/b1/user(a)domian.com, index=, indexpvt=, control=, inbox=, alt= doveadm(user(a)domian.com): Debug: acl: initializing backend with data: vfile doveadm(user(a)domian.com): Debug: acl: acl username = user(a)domian.com doveadm(user(a)domian.com): Debug: acl: owner = 1 doveadm(user(a)domian.com): Debug: acl vfile: Global ACLs disabled doveadm(user(a)domian.com): Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=mdbox:/var/mailboxes/%2Mu/%2.2Mu/%u doveadm(user(a)domian.com): Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= doveadm(user(a)domian.com): Debug: acl: initializing backend with data: vfile doveadm(user(a)domian.com): Debug: acl: acl username = user(a)domian.com doveadm(user(a)domian.com): Debug: acl: owner = 0 doveadm(user(a)domian.com): Debug: acl vfile: Global ACLs disabled doveadm(user(a)domian.com): Debug: acl vfile: file /var/mailboxes/64/b1/user(a)domian.com/mailboxes/INBOX/dbox-Mails/dovecot-acl not found doveadm(user(a)domian.com): Debug: acl vfile: file /var/mailboxes/64/b1/user(a)domian.com/mailboxes/Drafts/dbox-Mails/dovecot-acl not found doveadm(user(a)domian.com): Debug: acl vfile: file /var/mailboxes/64/b1/user(a)domian.com/mailboxes/Sent/dbox-Mails/dovecot-acl not found doveadm(user(a)domian.com): Debug: acl vfile: file /var/mailboxes/64/b1/user(a)domian.com/mailboxes/Trash/dbox-Mails/dovecot-acl not found doveadm(user(a)domian.com): Debug: Namespace : Using permissions from /var/mailboxes/64/b1/user(a)domian.com: mode=0700 gid=default dsync(user(a)domian.com): Debug: Effective uid=503, gid=503, home=/var/mailboxes/%2Mu/%2.2Mu/%u dsync(user(a)domian.com): Debug: Home dir not found: /var/mailboxes/%2Mu/%2.2Mu/%u dsync(user(a)domian.com): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/tmp/destination/mailboxes/user@domian.com dsync(user(a)domian.com): Debug: maildir++: root=/tmp/destination/mailboxes/user(a)domian.com, index=, indexpvt=, control=, inbox=/tmp/destination/mailboxes/user(a)domian.com, alt= dsync(user(a)domian.com): Debug: Namespace : /tmp/destination/mailboxes/user(a)domian.com doesn't exist yet, using default permissions dsync(user(a)domian.com): Debug: Namespace : Using permissions from /tmp/destination/mailboxes/user(a)domian.com: mode=0700 gid=default dsync(user(a)domian.com): Debug: acl: initializing backend with data: vfile dsync(user(a)domian.com): Debug: acl: acl username = user(a)domian.com dsync(user(a)domian.com): Debug: acl: owner = 1 dsync(user(a)domian.com): Debug: acl vfile: Global ACLs disabled dsync(user(a)domian.com): Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=mdbox:/var/mailboxes/%2Mu/%2.2Mu/%u dsync(user(a)domian.com): Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= dsync(user(a)domian.com): Debug: acl: initializing backend with data: vfile dsync(user(a)domian.com): Debug: acl: acl username = user(a)domian.com dsync(user(a)domian.com): Debug: acl: owner = 0 dsync(user(a)domian.com): Debug: acl vfile: Global ACLs disabled dsync(user(a)domian.com): Error: User initialization failed: namespace configuration error: All list=yes namespaces must use the same separator but when I will specify namespace to the inbox like /bin/dsync -Dv -u user(a)domian.com mirror maildir:/tmp/destination/mailboxes/user@domian.com -n inbox it throws different error: doveadm(user(a)domian.com): Debug: Namespace : Using permissions from /var/mailboxes/64/b1/user(a)domian.com: mode=0700 gid=default doveadm(user(a)domian.com): Fatal: execvp(maildir:/tmp/destination/mailboxes/user@domian.com) failed: No such file or directory dsync-local(user(a)domian.com): Error: read(remote) failed: EOF (version not received when /tmp/destination/mailboxes/user(a)domian.com directory exists What I’m doing wrong in the process? -- Adam

1 2

lmtp and virtual users
by David Wells - Alfavinil S.A. 02 Oct '19

02 Oct '19

Good afternoon. I have dovecot setup to authenticate virtual users using either gssapi or doind a bind to an ldap server to achieve a single sign on capable imap server connected to a samba active directory DC. What I am also trying to achieve is to have dovecot's lmtp daemon handle the mails passed from postfix. However, the only way I've gotten this to work is setting allow_all_users = yes in the userdb but this causes lmtp to deliver mails to non existant accounts without rejection. I've been searching but haven't found a way to set this same thing up but having dovecots lmtp check the validity of the mails recipient against the same samba AD DC through ldap before delivering it and rejecting unknown email addresses. Could someone please provide some insight into how to achieve this? Thank you very much in advance. Best regards, David Wells.

3 7

Unable to connect/authenticate after Debian SSL update
by paul 02 Oct '19

02 Oct '19

Just applied Debian SSL updates, due to vulnerabilities reported: "Package : openssl CVE ID : CVE-2019-1547 CVE-2019-1549 CVE-2019-1563 Three security issues were discovered in OpenSSL: A timing attack against ECDSA, a padding oracle in PKCS7_dataDecode() and CMS_decrypt_set1_pkey() and it was discovered that a feature of the random number generator (RNG) intended to protect against shared RNG state between parent and child processes in the event of a fork() syscall was not used by default. For the oldstable distribution (stretch), these problems have been fixed in version 1.1.0l-1~deb9u1. For the stable distribution (buster), these problems have been fixed in version 1.1.1d-0+deb10u1." I am running Buster. Upon installing these updates, Dovecot immediately stopped allowing authentication: Oct 1 16:47:11 relay monit[539]: 'dovecot' failed protocol test [IMAP] at [localhost]:993 [TCP/IP TLS] -- SSL connection error: error:00000000:lib(0):func(0):reason(0) Oct 1 16:50:22 relay monit[539]: 'dovecot' failed protocol test [IMAP] at [localhost]:993 [TCP/IP TLS] -- SSL connection error: error:00000000:lib(0):func(0):reason(0) and Oct 01 16:51:18 imap-login: Info: Disconnected: TLS initialization failed. (no auth attempts in 0 secs): user=<>, rip=71.198.57.170, lip=10.0.0.81, session=<0EdTB+KT+/NHxjmq> Each time this occurs, dovecot restarts: Oct 01 16:50:23 master: Info: Dovecot v2.3.7.2 (3c910f64b) starting up for pop3, imap (core dumps disabled) Oct 01 16:50:42 master: Info: Dovecot v2.3.7.2 (3c910f64b) starting up for pop3, imap (core dumps disabled) Oct 01 16:51:10 master: Info: Dovecot v2.3.7.2 (3c910f64b) starting up for pop3, imap (core dumps disabled) Oct 01 16:53:35 master: Info: Dovecot v2.3.7.2 (3c910f64b) starting up for pop3, imap (core dumps disabled) Oct 01 16:56:46 master: Info: Dovecot v2.3.7.2 (3c910f64b) starting up for pop3, imap (core dumps disabled) Oct 01 16:59:57 master: Info: Dovecot v2.3.7.2 (3c910f64b) starting up for pop3, imap (core dumps disabled) Oct 01 17:03:08 master: Info: Dovecot v2.3.7.2 (3c910f64b) starting up for pop3, imap (core dumps disabled) I am at a loss. Dovecot had been working fine for ages. It's not clear to me why a routine SSL update would completely break it. I'm unclear how to proceed. This is a small personal server, but nevertheless I have a number of people using it who rely on it. Here is my local.conf ( I added the ssl_protocols and ssl_min_protocol entries just a few minutes ago while attempting to resolve) auth_cache_size = 100 k auth_cache_ttl = 12 hours auth_cache_negative_ttl = 12 hours auth_cache_verify_password_with_worker=yes auth_verbose = yes auth_failure_delay = 7 secs default_client_limit = 500 default_process_limit = 50 default_vsz_limit = 100 M verbose_proctitle = yes protocols = pop3 imap pop3_uidl_format = %08Xu%08Xv imap_idle_notify_interval = 244 secs info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot-error.log maildir_very_dirty_syncs=yes mail_location = maildir:~/Maildir mailbox_idle_check_interval = 244 secs mailbox_list_index = yes 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 = } passdb { driver = passwd-file args = /etc/dovecot/deny deny = yes } passdb { driver = pam } userdb { driver = passwd } service auth { unix_listener auth-client { mode = 0660 user = Debian-exim } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } protocol imap { mail_max_userip_connections = 20 } service imap { unix_listener imap-master { user = dovecot } } imap_hibernate_timeout = 1 mins service imap { extra_groups = dovenull } service imap-hibernate { unix_listener imap-hibernate { mode = 0660 group = dovenull } } ssl = required ssl_protocols = TLSv1 TLSv1.1 TLSv1.2 ssl_min_protocol=TLSv1 ssl_dh=</etc/dovecot/dh.pem ssl_cert = </etc/letsencrypt/live/relay.anastrophe.com/fullchain.pem ssl_key = </etc/letsencrypt/live/relay.anastrophe.com/privkey.pem

1 1

Lost mails with sieve "duplicate" extension in case of failure
by Hanno Stock 01 Oct '19

01 Oct '19

Hi! we just experienced the following issue: We have a global sieve_before script using the duplicate extension. require ["duplicate", "imap4flags"]; if duplicate { discard; } Now the storage of our mailbox store got full and lmtp deliveries started to fail. This resulted in logs like this: Sep 25 16:14:56 mail-rc1 dovecot: lmtp(USERNAME): Error: o_stream_send_istream(/var/mail/vhosts/mail.COMPANY.com/USERNAME/.dovecot/t… failed: No space left on device Sep 25 16:14:56 mail-rc1 dovecot: lmtp(USERNAME): Error: write(/var/mail/vhosts/mail.COMPANY.com/USERNAME/.dovecot/tmp/1569420896.M6… failed: No space left on device Sep 25 16:14:56 mail-rc1 dovecot: lmtp(USERNAME): Error: KT9HJGB2i128FgAATXMPig: sieve: msgid=<redmine.journal-441799.20190925141453.94a97fd570706f2f(a)mail.COMPANY.com>: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2019-09-25 16:14:56] Sep 25 16:14:56 mail-rc1 dovecot: lmtp(USERNAME): Error: KT9HJGB2i128FgAATXMPig: sieve: Execution of script /mnt/data/var/mail/vhosts/mail.COMPANY.com/USERNAME/.sieve/.dovecot.sieve was aborted due to temporary failure (user logfile /mnt/data/var/mail/vhosts/mail.COMPANY.com/USERNAME/.sieve/.dovecot.sieve.log may reveal additional details) Sep 25 16:14:56 mail-rc1 postfix/lmtp[5851]: 4D27690AC: to=<USERNAME(a)mail.COMPANY.com>, orig_to=<USER.NAME(a)COMPANY.com>, relay=mail-rc1.bvd.COMPANY.x[private/dovecot-lmtp], delay=1.3, delays=1.3/0/0/0.01, dsn=4.2.0, status=deferred (host mail-rc1.bvd.COMPANY.x[private/dovecot-lmtp] said: 451 4.2.0 <USERNAME(a)mail.COMPANY.com> Internal error occurred. Refer to server log for more information. [2019-09-25 16:14:56] (in reply to end of DATA command)) So far, so good... A 451 response is what we wanted. However on the next delivery attempt the following happens: Sep 25 16:24:00 mail-rc1 postfix/lmtp[7040]: 4D27690AC: to=<USERNAME(a)mail.COMPANY.com>, orig_to=<USER.NAME(a)COMPANY.com>, relay=mail-rc1.bvd.COMPANY.x[private/dovecot-lmtp], delay=545, delays=545/0.09/0.02/0.01, dsn=2.0.0, status=sent (250 2.0.0 <USERNAME(a)mail.COMPANY.com> DBcCEYB4i11qGwAATXMPig Saved) Sep 25 16:24:00 mail-rc1 dovecot: lmtp(USERNAME): DBcCEYB4i11qGwAATXMPig: sieve: msgid=<redmine.journal-441799.20190925141453.94a97fd570706f2f(a)mail.COMPANY.com>: marked message to be discarded if not explicitly delivered (discard action) Sep 25 16:24:00 mail-rc1 postfix/lmtp[7040]: 4D27690AC: to=<USERNAME(a)mail.COMPANY.com>, orig_to=<USER.NAME(a)COMPANY.com>, relay=mail-rc1.bvd.COMPANY.x[private/dovecot-lmtp], delay=545, delays=545/0.09/0.02/0.01, dsn=2.0.0, status=sent (250 2.0.0 <USERNAME(a)mail.COMPANY.com> DBcCEYB4i11qGwAATXMPig Saved) As the duplicate extension has already seen the mail, it is now immediately discarded. RFC 7352 however explicitly states: Implementations MUST only update the internal duplicate-tracking list when the Sieve script execution finishes successfully. If failing script executions add the unique ID to the duplicate-tracking list, all "duplicate" tests in the Sieve script would erroneously yield "true" for the next delivery attempt of the same message. Dovecot seems not to honour this specification. Maybe this is because the "before_script" is not the script that fails, but the subsequent scripts fail? Am I missing some configuration option that would propagate the subsequent failure back to the before_script? Or is this a general limitation of the before_script mechanism? Any help appreciated how to alleviate this issue! Best regards Hanno --- Filesystem: ext4 Dovecot config: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-11-amd64 x86_64 Debian 9.11 auth_cache_negative_ttl = 0 auth_cache_size = 1 M auth_cache_ttl = 2 hours auth_mechanisms = plain login auth_username_format = %Ln mail_gid = vmail mail_home = /var/mail/vhosts/mail.COMPANY.com/%n mail_location = maildir:~/.dovecot mail_plugins = " acl" mail_privileged_group = vmail mail_uid = vmail 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 editheader imapflags notify namespace { hidden = yes list = no location = maildir:~/.dovecot-top-namespace prefix = separator = . subscriptions = yes type = private } namespace { location = maildir:/var/mail/vhosts/mail.COMPANY.com/%%n/.dovecot:INDEXPVT=/var/mail/v… 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 = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db sieve = file:/var/mail/vhosts/mail.COMPANY.com/%n/.sieve/sieve;active=/var/mail/vho… sieve_after = /var/mail/sieve/global-after.sieve sieve_before = /var/mail/sieve/global-before.sieve sieve_default = /var/mail/sieve/global.sieve sieve_extensions = +imapflags +notify +editheader sieve_global = /var/mail/sieve } protocols = imap lmtp sieve service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } process_limit = 9000 } service imap { process_limit = 9000 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 0 } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.COMPANY.com/fullchain.pem ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 30 mail_plugins = " acl imap_acl" } protocol sieve { mail_debug = yes }

2 2

Mailbox INBOX sync: mailbox_delete failed
by Alex La 01 Oct '19

01 Oct '19

Hi. When I run the backup I always get this error. ``` [root@mail.DOMAIN.com:~]# doveadm -o mail_fsync=never backup -D -R -u office(a)DOMAIN.com imapc: dsync(office(a)DOMAIN.com): Info: imapc(imap.mailbox.org:993): Connected to 2001:67c:2050:106::143:199:993 (local 2a01:4f8:c2c:6d05::1:59928) dsync(office(a)DOMAIN.com): Info: Mailbox deleted: Drafts dsync(office(a)DOMAIN.com): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. ``` The suggested solution from this mail works, but is this still the best solution for the error above? https://dovecot.org/pipermail/dovecot/2016-January/102988.html My versions are # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.2 (aaba65b7) # OS: Linux 3.10.0-1062.1.1.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) Best regards Alex

2 2

Migration
by Hans Brage 01 Oct '19

01 Oct '19

Hi! I'm currently running an small imap-server on Dovecot 2.2.4 but will retire that server. I've set up an new server with Dovecot 2.3.4 and will migrate the mailboxes (maildir-format) from the old to the new server. I'm planning to restructure the accounts a bit when migrating so I need to move them one by one. Its only a few so thats not a big issue. Both servers are using virtual accounts (users file). I've understood that best method for migration is to run doveadm backup -R from the new server. But I really cant figure out what other parameters or settings that I need to perform that task and if it should be run as user vmail or root. Would be greatful for any tips, hints, links or similiar. Regards, Hans

6 9

Best way to move mail from one server to another
by James Brown 01 Oct '19

01 Oct '19

I’d like to migrate to a new server. I only need to transfer the mail store, have already done the users. I’ve seen different recommendations: IMAP-Sync Rsync Doveadmin backup and dsync What are the pros and cons of each? What would be best for me? I’m thinking that Doveadmin backup is the way to go. Both old and new servers are on same network. New server is running Dovecot 2.3.2.1, old server is 2.2.32. macOS X. Does anyone have any advice or examples? Thanks, James.

13 29

courier to dovecot migration
by tovises 01 Oct '19

01 Oct '19

I have a quite old home server based on Debian 6.x packages using courier imap server (exim4, fetchmail, courier, apache2, squirrelmail) to keep my and my wife emails (about 25G). I want renew my server to Debian 10 (buster) and got a recommendation to use dovecot instead of courier. For this purpose I'm using a different PC as a sandbox. Debian 10 currently offer dovecot version 2.3.4.1 Installation was "peaceful" but stuck with the migration. I have choose migration using dsync, from Wiki I was choose this command: For per-user user/passwords use: doveadm -o imapc_user=foo -o pop3c_user=foo -o imapc_password=bar -o pop3c_password=bar backup -R -u user@domain imapc: (foo and bar placed real username and password) But I get error: doveadm(tovis(a)nusi.tovis-lab.mydomain.org): Error: User doesn't exist Strongly I have no real domain, I'm using "freedns". "nusi" is the local name of my old server, "tovis-lab" is conjunction with "mydomain.org" choose from freedns. I was trying short as "nusi" which is in /etc/hosts file even ip address but the same result. 143 and 943 ports are working only inside the firewall (OpenWrt). I was checked using telnet courier on the "remote" box and dovecot on the localhost. I was able to login. What should I use as "user@domain" in this situation? tovis

4 10

Mail-crypt won't encrypt emails
by Serveria Support 01 Oct '19

01 Oct '19

Hi, We're running Dovecot 2.2.36 and we need to set up the mail-crypt plugin to encrypt all incoming and outgoing emails. Outgoing emails seem to get encrypted fine but the incoming ones don't. We tried everything including this config: mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_plugins = $mail_plugins mail_crypt plugin { mail_crypt_global_private_key = <ecprivkey.pem mail_crypt_global_public_key = <ecpubkey.pem mail_crypt_save_version = 2 } also this one: plugin { mail_crypt_curve = prime256v1 mail_crypt_save_version = 2 } but to no avail. There are no visible errors, Dovecot restarts fine and outgoing emails get encrypted. Any ideas?

1 0

Sieve replication - does not replicate
by Daniel Botting 30 Sep '19

30 Sep '19

Hi, I have two servers replicating mail as required, the directory structure (per user), however they will not replicate the sieve scripts directory: server 1 Maildir sieve server 2 Maildir Output of doveconf -n on server 1: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:51: ssl_protocols has been replaced by ssl_min_protocol doveconf: Error: Could not find a minimum ssl_min_protocol setting from ssl_protocols = !SSLv2 !SSLv3: Unrecognized protocol 'SSLv2' doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:51: ssl_protocols has been replaced by ssl_min_protocol doveconf: Error: Could not find a minimum ssl_min_protocol setting from ssl_protocols = !SSLv2 !SSLv3: Unrecognized protocol 'SSLv2' # OS: Linux 4.19.0-6-amd64 x86_64 Debian 10.1 # Hostname: a_tld auth_verbose = yes default_vsz_limit = 0 doveadm_password = # hidden, use -P to show it first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_gid = 8 mail_location = maildir:~/Maildir mail_plugins = " notify replication" mail_uid = 8 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 editheader imapflags 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 = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { mail_replica = tcps:a_tld:12345 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +editheader +imapflags } protocols = " imap sieve pop3" replication_max_conns = 4 service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail } } service auth { unix_listener /var/run/dovecot-exim-bridge { mode = 0660 user = Debian-exim } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 512 process_min_avail = 4 service_count = 1 } service imap { process_limit = 1024 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 1 service_count = 8 vsz_limit = 256 M } service managesieve { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </where/the_cert_is_installed/fullchain.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap override_fields = home=/var/mail/%u uid=mail gid=mail } protocol lda { mail_plugins = " notify replication sieve" } protocol imap { mail_max_userip_connections = 32 mail_plugins = " notify replication" } protocol sieve { mail_max_userip_connections = 10 managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 } The only error message I can see in the logs (/var/log/mail.err) is, this is not for every user and is only occasionally: Sep 30 14:46:34 imap2 dovecot: lda(a_user)<1306><f0JXJjoHkl0aBQAAZJ7A9A>: Error: sieve: Failed to initialize script execution: Invalid postmaster_address: invalid address `postmaster@' specified for the postmaster_address setting Any suggestions would be much appreciated. Cheers -- Daniel

2 1

Only some encrypted mailboxes
by filbar＠centrum.cz 29 Sep '19

29 Sep '19

Hello I'm looking in plugin for encrypting mailboxes. Is possible to have encrypted only some of mailboxes and other not? Thanks, Filip Bartmann

1 0

dsync having problems with @-sign in mailbox names
by Philip Iezzi 28 Sep '19

28 Sep '19

Hi there We are running Cyrus-to-Dovecot migrations using dsync on destination Dovecot server (Debian Stretch / latest Dovecot 2.3.7.2 from community repo) like this: $ doveadm -o mail_fsync=never backup -R -u <username> imapc: For imapc configuration to connect to remote Cyrus server, see below [1]. While this works great for hundreds of mailaccounts, dsync fails with the following error on accounts with @-sign in mailbox names: dsync(<username>): Error: Failed to access mailbox INBOX/entrance/admin@example: Invalid mailbox name I can confirm, Dovecot supports @-sign in mailbox names and no client (tested with Thunderbird, Apple Mail, Roundcube webmail) has issue with this character. Also Cyrus was always supporting this. So I guess this is an issue with dsync. Can we somehow tune charset (UTF-8 ?) in imapc configuration? Thanks, Philip [1] /etc/dovecot/conf.d/90-migration.conf: ## IMAP imapc_host = imap.example.com imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = yes imapc_user = %u imapc_master_user = cyrus imapc_password = ********** imapc_features = rfc822.size fetch-headers mail_prefetch_count = 20 imapc_list_prefix = INBOX ## POP3 pop3c_host = pop3.example.com pop3c_port = 995 pop3c_ssl = pop3s pop3c_ssl_verify = yes pop3c_user = %u pop3c_master_user = cyrus pop3c_password = ********** namespace { prefix = POP3-MIGRATION-NS/ location = pop3c: list = no hidden = yes } protocol doveadm { mail_plugins = $mail_plugins pop3_migration } plugin { pop3_migration_mailbox = POP3-MIGRATION-NS/INBOX }

2 5

Mail received but not indexed?
by Marc Roos 28 Sep '19

28 Sep '19

I have recently that some users are complaining about that they are not getting emails. While I see that they are delivered and in the inbox. When I do a doveadm force-resync -u xxxx INBOX it resolves the problem. I think this is something recent. Where/how should I resolve this issue? Recent changes 1. did some os updates 2019-08-27 2. provider took away the ssd for index storage (maybe config issue having less iops storage?) CentOS Linux release 7.6.1810 (Core) dovecot-2.2.36-3.el7.x86_64 mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u:CONTROL=~/mail/control:INDEX=/var/d ovecot2/%u/index:LAYOUT=maildir++ PS during force-resync, I am getting these "index/.INBOX/dovecot.index.log was locked for 176 seconds" on some users

3 4

Debug one user possible?
by Marc Roos 27 Sep '19

27 Sep '19

Is it possible to mail debug just one user? Maybe via the userdb?

3 2

limits in high-security mode with ssl
by sergio 27 Sep '19

27 Sep '19

Hello. I'm using dovecot in high-security mode: service_count = 1 for imap-login service starttls is requires, so the maximum number of active connections is process_limit (which is set to 1024) for the same imap-login service. But with this setup I got: doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (1324) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1227) 1. Where did 1324 and 1227 come from? 2. How configuration should be updated so these warnings disappear? -- sergio.

1 0

doveadm / vsize
by Paul Macdonald 27 Sep '19

27 Sep '19

Hi, i want to keep track of user mailbox size, I'm using doveadm mailbox status -u <user> vsize INBOX for a given mailbox this is under reporting ( by a lot) is this recursive? what shoud i be using to get an accurate disk usage metric? thanks Paul. -- ------------------------- Paul Macdonald IFDNRG Ltd Web and video hosting ------------------------- t: 0131 5548070 m: 07970339546 e: paul(a)ifdnrg.com w: http://www.ifdnrg.com ------------------------- IFDNRG 40 Maritime Street Edinburgh EH6 6SA ---------------------------------------------------- Virtual Servers from £50.00pm High specification Dedicated Servers from £150.00pm ----------------------------------------------------

3 4

Re: Website Down? Not down.
by dundir＠gmail.com 27 Sep '19

27 Sep '19

Its not down, its most likely your providers DNS resolution. www.dovecot.org resolves to: ipv4 : 94.237.85.39 ipv6: 2a04:3542:1000:910:acc1:5bff:fe5e:3b83 Best Regards, D.

3 2

Website down?
by ＠lbutlr 27 Sep '19

27 Sep '19

I am not able to reach the dovecot site on any one of three connections (home, office, mobile). Trying to look up DNS shows no records. -- But just because you've seen me on your TV Doesn't mean I'm any more enlightened than you

1 0

File manager or browser for IMAP?
by Steve Litt 26 Sep '19

26 Sep '19

Hi all, I could really use a file manager or browser to browse my Dovecot IMAP. Ideally it would have hotkeys to move, copy, delete and send. The send part needn't be coded: Just a call to a shellscript which can handle the send the way it's locally the most convenient. Anyone know of such a file manager or browser for IMAP? SteveT Steve Litt Author: The Key to Everyday Excellence http://www.troubleshooters.com/key Twitter: http://www.twitter.com/stevelitt

11 13

Typo in wiki
by Mika Pflüger 26 Sep '19

26 Sep '19

Hi, on https://wiki2.dovecot.org/Plugins/LastLogin the link to the new documentation page is wrong and leads to a 404. The correct link is https://doc.dovecot.org/plugin-settings/last-login-plugin/ . I tried correcting it myself in the wiki, but the Captcha was too hard for me. Cheers, Mika

2 1

Dovecot UIDs and POP.
by Plutocrat 26 Sep '19

26 Sep '19

Hi, I recently performed a mail server migration for a client under fairly serious time constraints (ahem, yes one of those jobs). I would normally use imapsync to get all the mail copied to the new server, but under the circumstances, I had to write a script to rsync each of the mailboxes over ssh, from one server to another. This all worked fine, except for the fact that if a client was using a POP email client, when they connected to the new server, they re-downloaded all their mail, creating duplicates of everything in their Outlook client. Of course they weren't happy about this. IMAP email clients were OK. No duplicates, and everything was fine. So while I was migrating the mail, I did try for a while to understand the format of the UID files, but failed to do so in the available time, so the client just had to deal with duplicate emails. But now the smoke has cleared, I'd like to understand the problem a little better, and I was hoping someone on this forum could explain it to me, and the changes I'd need to make to the files so that the POP client DIDN'T download the duplicate emails. Here's what I understand. The list of dovecot files in an account looks like this: -rw-r----- 1 admin mail 0 Jul 11 2018 dovecot-acl-list -rw-r----- 1 admin mail 14K Sep 20 08:36 dovecot.index -rw-r----- 1 admin mail 216K Sep 20 17:24 dovecot.index.cache -rw-r----- 1 admin mail 29K Sep 20 17:24 dovecot.index.log -rw-r----- 1 admin mail 388 Dec 17 2017 dovecot.list.index -rw-r----- 1 admin mail 1.6K Jul 11 2018 dovecot.list.index.log -rw-r----- 1 admin mail 24 Jul 11 2018 dovecot.mailbox.log -rw-r----- 1 admin mail 53 Sep 12 09:42 dovecot-quota -rw-r----- 1 admin mail 52K Sep 20 17:24 dovecot-uidlist -rw-r----- 1 admin mail 8 Jul 11 2018 dovecot-uidvalidity -rw-r----- 1 admin mail 0 Jul 4 2016 dovecot-uidvalidity.5779bbeb It seems that the dovecot-uidlist is an index of all the mail files in the account. As far as I can gather, this should be the same on both servers after I've rsynced them over ssh: The files and the list of them in dovecot-uidlist should correspond. So what is it that the POP client looks at and decides to re-download all the emails? And how could I have stopped it from doing that, and get it to realize that the list of emails it holds internally is the same as the list on the server? What would I need to change in the dovecot files? Thanks for any insight into the process. As a secondary question -- and perhaps I should put this in a separate message -- I did notice that "doveadm sync" would apparently have helped me with this, but I wasn't able to get that to work either. I believe it was something to do with the fact that all the mailboxes were under the same linux user account on the target server, and I couldn't figure out all the paths and permissions in time. Would 'doveadm sync' have fixed all the UID and duplicate POP email issues? P.

6 11

NFS Locking and Submission Service Authentication
by Asai 26 Sep '19

26 Sep '19

Greetings, We're in the process of upgrading our Dovecot server to new hardware and new expanded storage. We planned on using an NFS share for the mail storage, as we're running Postfix / Dovecot on a VM and wanted to separate out the mail storage from the VM for backup reasons. I read as much as I could find on line regarding configuring Dovecot to use NFS, and set it up as best I could, but I'm still running into lock errors e.g.: Sep 25 10:30:35 triata4 dovecot: imap(user(a)triata.globalchange.media)<75580><enQ/AWSTkQkKCgDu>: Error: fcntl(/vmail/triata.globalchange.media/user/dovecot.index.log, write-lock, F_SETLKW) locking failed: No locks available Sep 25 10:30:35 triata4 dovecot: imap(user(a)triata.globalchange.media)<75580><enQ/AWSTkQkKCgDu>: Error: mail_index_wait_lock_fd() failed with file /vmail/triata.globalchange.media/user/dovecot.index.log: No locks available Also, I have been trying to configure the Dovecot submission service to authenticate with Postfix, but I keep running into errors which are related to how I'm configuring the authentication. How do we set the user@domain and password string for submission in the configs? Thank you. Please see doveconf -n below, if you see any other errors in this config, I'd be grateful if you pointed them out: # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 (7372921a) # OS: Linux 3.10.0-957.27.2.el7.x86_64 x86_64 CentOS Linux release 7.6.1810 (Core) nfs auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot-debug.log deliver_log_format = msgid=%m: from=%f: %$ hostname = triata.globalchange.media mail_debug = yes mail_fsync = always mail_home = /vmail/%d/%n/home mail_location = maildir:/vmail/%d/%n 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 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 { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { mail_log_fields = uid box msgid from flags sieve = file:/vmail/%d/%n/sieve;active=/vmail/%d/%n/.dovecot.sieve } protocols = imap lmtp submission sieve service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 1024 } service submission-login { inet_listener submission { port = 587 } } ssl_cert = </etc/letsencrypt/live/triata.globalchange.media/fullchain.pem ssl_key = # hidden, use -P to show it submission_relay_host = triata.globalchange.media submission_relay_password = # hidden, use -P to show it submission_relay_port = 587 submission_relay_ssl = starttls submission_relay_trusted = yes submission_relay_user = %u userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { mail_plugins = }

3 4

Spam Blocking by filtering on username / id
by Plutocrat 26 Sep '19

26 Sep '19

This is probably quite an easy question, but I haven't been able to find the answer. I'm running a server where all the email addresses are in the format "user(a)domain.com". I've noticed that a large number of fake login attempts use the format "user" eg. reception, service, root, admin. Is it possible to prevent any such logins to these email users without an @domain.com? Or maybe ignore them. Or drop them from the logging. P.

5 5

'director_tag' field returned from passdb lookup results in 'unknown passdb extra field'
by Dan 25 Sep '19

25 Sep '19

Hello all, I'm working with director in tandem with 'director_tags' to group some backend hosts. I've assigned the groups to the hosts by appending a '@' character after the IP address of a backend host under director_mail_servers: ... director_mail_servers = 192.168.0.1@foo 192.168.0.2@bar 192.168.0.3@foobar ... I can confirm that the backend hosts possess the correct tags by issuing: # doveadm director status mail server ip tag vhosts state state changed users 192.168.0.1 foo 100 up - 0 192.168.0.2 bar 100 up - 0 192.168.0.3 foobar 100 up - 0 And examining that the tags have been assigned correctly. My passdb lookup is using mysql, and it appears as such: passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } This file looks like: driver = mysql connect = host=localhost dbname=xxx user=xxx password=xxx password_query = select director_tag, username, domain, password, 'Y' as `proxy` from users where username = '%n' and domain = '%d' iterate_query = select director_tag, username, domain from users I have a database that contains the following columns: username, domain, password, home, UID, GID, active, and director_tag To assign users to a backend, I went off of the documentation that states: > " A passdb lookup can return "director_tag" field containing the wanted tag name. " To fulfill this, I return the 'director_tag' in the passdb lookup, through password_query. The mapping seems to work. When I change the row in the database, the user gets proxied to the new backend on the next connection. However, My question is, Why does this appear in the logs? "dovecot[1963]: imap-login: Debug: Ignoring unknown passdb extra field: director_tag" How could this be an unknown passdb extra field, when the documentation states that you may return a field containing this key? In the file core/src/login-common/client-common-auth.c - Starting at line 142, there is no if condition checking for 'director_tag'. This causes that line to be output to debug handle. Is this intentional? Thank you for your time. Full configuration: auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = yes director_mail_servers = 192.168.0.1@foo 192.168.0.2@bar 192.168.0.3@foobar director_servers = x.x.x.x y.y.y.y director_user_expire = 5 mins disable_plaintext_auth = no doveadm_port = 24245 haproxy_trusted_networks = x.x.x.x y.y.y.y 127.0.0.1 login_greeting = Dovecot At Your Service 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 passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service director { fifo_listener login/proxy-notify { mode = 0666 user = $default_login_user } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imap { haproxy = yes port = 143 } inet_listener imaps { haproxy = yes port = 993 ssl = yes } } service ipc { unix_listener ipc { user = dovecot } } service pop3-login { executable = pop3-login director inet_listener pop3 { haproxy = yes port = 110 } inet_listener pop3s { haproxy = yes port = 995 ssl = yes } } ssl_cert = </etc/dovecot/private/dovecot.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol doveadm { auth_socket_path = director-userdb }

2 1

Can't Get SASL to Work
by Christopher Wooley 25 Sep '19

25 Sep '19

I have been fighting with this for almost 2 days. I can't seem to get the SMTP server to authenticate through SASL. I have turned so many things off and on, I don't remember what I've done, anymore. Can someone look at these and tell me what I'm missing. I get this in the log, anytime postfix tries to authenticate. Sep 24 19:48:14 ubuntu postfix/smtpd[14464]: warning: SASL: Connect to smtpd failed: No such file or directory Sep 24 19:48:14 ubuntu postfix/smtpd[14464]: fatal: no SASL authentication mechanisms Sep 24 19:48:15 ubuntu postfix/master[14048]: warning: process /usr/lib/postfix/sbin/smtpd pid 14464 exit status 1 srw-rw-rw- 1 postfix postfix 0 Sep 24 19:10 auth 10-auth.conf disable_plaintext_auth = no auth_ssl_require_client_cert = no auth_mechanisms = plain !include auth-system.conf.ext -------------- 10-master.conf service imap-login { inet_listener imap { } inet_listener imaps { } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { mode = 0666 user = postfix group = postfix } } service imap { } service pop3 { } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } unix_listener auth-userdb { mode = 0666 user = postfix group = postfix } } service auth-worker { } service dict { unix_listener dict { } } -------------- main.cf smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no compatibility_level = 2 smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = ubuntu.local.acr-live.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydestination = $myhostname, ubuntu, localhost.localdomain, xyz.com , localhost mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = all smtpd_sasl_type = dovecot smtpd_sasl_auth_enable = yes smtp_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_tls_security_level = may ---------------------------------- master.cf 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_tls_auth_only=yes -o smtpd_reject_unlisted_recipient=no -o smtpd_sasl_type=dovecot -o smtpd_sasl_path=private/auth -o smtpd_recipient_restrictions= -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o milter_macro_daemon_name=ORIGINATING pickup unix n - y 60 1 pickup cleanup unix n - y - 0 cleanup qmgr unix n - n 300 1 qmgr tlsmgr unix - - y 1000? 1 tlsmgr rewrite unix - - y - - trivial-rewrite bounce unix - - y - 0 bounce defer unix - - y - 0 bounce trace unix - - y - 0 bounce verify unix - - y - 1 verify flush unix n - y 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - y - - smtp relay unix - - y - - smtp -o syslog_name=postfix/$service_name showq unix n - y - - showq error unix - - y - - error retry unix - - y - - error discard unix - - y - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - y - - lmtp anvil unix - - y - 1 anvil scache unix - - y - 1 scache maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient} uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient scalemail-backend unix - n n - 2 pipe flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}

2 2