- dovecot - dovecot.org

lmtp + tcpwrap
by A. Schulze 01 Aug '18

01 Aug '18

Hello, Using the TCP Wrapper Dovecot could control access to IMAP and POP3 servers. Is it also possible to controll access to an LMTP Server listening on Port 24? Andreas

1 0

Re: Get rid of the "dbox-Mails"-folder
by Hativ 31 Jul '18

31 Jul '18

Hey Aki, DIRNAME with empty value has no effect, just like with FULLDIRNAME. "~/sdbox" instead of "~/" doesn't change that.. Greetings, Hativ Am 07.07.2018 um 20:24 schrieb Aki Tuomi: > Does it work better if you use > > mail_location=sdbox:~/sdbox:DIRNAME= > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Hativ <hativ3(a)gmail.com> > Date: 07/07/2018 20:53 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Re: Get rid of the "dbox-Mails"-folder > > Hey again, > > sorry, but I have to correct me: Even with dot it's not working > completely. The subscriptions file is not created and the dovecot-acl > file has the wrong path, too. > > :-( > > Greetings, > > Hativ > > Am 07.07.2018 um 02:26 schrieb Hativ: >> Hey again, >> >> I've found a working configuration: mail_location = >> sdbox:~/:FULLDIRNAME=. >> >> I use a dot instead of slash or empty value. >> >> Now my folder structure looks like I want and Dovecot is working fine. >> >> Can anyone (maybe even a Dovecot developer?) say if the configuration >> is okay? I've tried to check the source code, but I don't know C as >> good as it's needed for that. >> >> Greetings, >> >> Hativ >> >> Am 06.07.2018 um 16:10 schrieb Hativ: >>> Hey to all, >>> >>> is it possible to get rid of the "dbox-Mails"-folder when using sdbox? >>> >>> Currently my folder structure looks like this (I hope the output >>> from tree would be formatted well): >>> /srv/mail/ >>> └── example.com >>> └── user >>> ├── dovecot-acl-list >>> ├── dovecot-attributes >>> ├── dovecot.list.index.log >>> ├── dovecot.mailbox.log >>> ├── dovecot-uidvalidity >>> ├── dovecot-uidvalidity.5b3f746f >>> ├── mailboxes >>> │ ├── Drafts >>> │ │ └── dbox-Mails >>> │ │ └── dovecot.index.log >>> │ ├── INBOX >>> │ │ └── dbox-Mails >>> │ │ ├── dovecot.index.cache >>> │ │ ├── dovecot.index.log >>> │ │ └── u.1 >>> │ ├── Junk >>> │ │ └── dbox-Mails >>> │ │ └── dovecot.index.log >>> │ ├── Sent >>> │ │ └── dbox-Mails >>> │ │ └── dovecot.index.log >>> │ └── Trash >>> │ └── dbox-Mails >>> │ └── dovecot.index.log >>> └── subscriptions >>> >>> I would like to let it look like this: >>> /srv/mail/ >>> └── example.com >>> └── user >>> ├── dovecot-acl-list >>> ├── dovecot-attributes >>> ├── dovecot.list.index.log >>> ├── dovecot.mailbox.log >>> ├── dovecot-uidvalidity >>> ├── dovecot-uidvalidity.5b3f746f >>> ├── mailboxes >>> │ ├── Drafts >>> │ │ └── dovecot.index.log >>> │ ├── INBOX >>> │ │ └── dovecot.index.cache >>> │ │ └── dovecot.index.log >>> │ │ └── u.1 >>> │ ├── Junk >>> │ │ └──dovecot.index.log >>> │ ├── Sent >>> │ │ └── dovecot.index.log >>> │ └── Trash >>> │ └── dovecot.index.log >>> └── subscriptions >>> >>> My path configuration: >>> mail_attribute_dict = file:%h/dovecot-attributes >>> mail_home = /srv/mail/%d/%n/ >>> mail_location = sdbox:~/ >>> >>> I have tried >>> mail_location = sdbox:~/:FULLDIRNAME= >>> and >>> mail_location = sdbox:~/:FULLDIRNAME=/ >>> but it doesn't work. >>> >>> The first doesn't change anything. The second auto-creates the >>> folders after first login like I want, but after next login they are >>> greyed out and no longer accessible. >>> >>> Is it possible to get rid of the "dbox-Mails"-folder? I want this >>> because I don't like to have an unneeded deep folder structure. Or >>> is there a good reason to let the "dbox-Mails" folder in my setup? >>> >>> Greetings, >>> >>> Hativ >>> >> >

2 2

Re: uid problem
by Aki Tuomi 31 Jul '18

31 Jul '18

https://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP Aki On 31.07.2018 14:35, Andras Kemeny wrote: > > can you point me to an url regarding LTMP between postfix and dovecot? > it might be an area worth exploring for me. > > thanks, > a > > > 2018. 07. 31. 12:46 keltezéssel, Aki Tuomi írta: >> >> Well, I don't know about yuuuge security risk (not saying there isn't >> any...), but if this concerns you, you can also use LTMP instead, >> which is probably a better solution here. >> >> Aki >> >> >> On 31.07.2018 13:42, Andras Kemeny wrote: >>> >>> yeah, the only problem about that is it's a yuuuge security risk :), >>> and also, postfix simply won't let me: >>> >>> Jul 31 02:20:37 rhyno postfix/pipe[29532]: fatal: user= command-line >>> attribute specifies root privileges >>> >>> so it's entirely possible i'm knocking on the wrong door, and >>> instead i should be asking this in the postfix mailing list. >>> >>> however, i'm also worried about this: "to bypass this check, set: >>> service auth { unix_listener /var/run/dovecot/auth-userdb { >>> mode=0777 } }", as i have done what it says, and the check wasn't >>> bypassed so i'm wary about something bad coming up once i somehow >>> fix this initial UID problem. >>> >>> thanks, >>> a >>> >>> >>> 2018. 07. 31. 7:12 keltezéssel, Aki Tuomi írta: >>>> You could run dovecot-lda as root. It will setuid to correct account. >>>> >>>> >>>> >>>> --- >>>> Aki Tuomi >>>> Dovecot oy >>>> >>>> -------- Original message -------- >>>> From: Andras Kemeny <pdx(a)pdx.hu> >>>> Date: 31/07/2018 04:46 (GMT+02:00) >>>> To: dovecot(a)dovecot.org >>>> Subject: uid problem >>>> >>>> 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 >>> >> >

1 0

Almost there with Sieve
by Danny Horne 31 Jul '18

31 Jul '18

Hi all, Dovecot - 2.2.35 Pigeonhole - 0.4.23 I've recently moved mail filtering from local filtering (using Thunderbird) to Sieve. I've got filtering into folders and flagging emails working fine, but for possibly one tiny glitch. When specifying folders to filter into I have to use the format 'INBOX/Folder name' instead of just 'Folder name'. Can this be corrected? No real biggie but would be nice if it could. [root@kepler ~]# dovecot -n # 2.2.35 (b1cb664): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.23 (b2e41927) # OS: Linux 4.17.3-200.fc28.x86_64 x86_64 Fedora release 28 (Twenty Eight) xfs # Hostname: kepler.trisect.uk auth_mechanisms = cram-md5 base_dir = /var/run/dovecot/ mail_access_groups = mail mail_home = /var/spool/vhosts/homedir/%d/%n mail_location = mbox:/var/spool/vhosts/%d/%n:INBOX=/var/spool/mail/%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 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 = } passdb { args = scheme=cram-md5 /etc/cram-md5.pwd driver = passwd-file } passdb { driver = pam } plugin { sieve = file:/var/spool/vhosts/sieve-scripts;active=/var/spool/vhosts/sieve-scripts/%u.sieve sieve_user_email = postmaster(a)trisect.uk } protocols = imap lmtp sieve sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 0 vsz_limit = 256 M } service managesieve { process_limit = 1024 } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail driver = static } userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 200 } protocol sieve { mail_max_userip_connections = 25 managesieve_implementation_string = Dovecot Pigeonhole managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 } Thanks for looking

2 2

Re: uid problem
by Aki Tuomi 31 Jul '18

31 Jul '18

Well, I don't know about yuuuge security risk (not saying there isn't any...), but if this concerns you, you can also use LTMP instead, which is probably a better solution here. Aki On 31.07.2018 13:42, Andras Kemeny wrote: > > yeah, the only problem about that is it's a yuuuge security risk :), > and also, postfix simply won't let me: > > Jul 31 02:20:37 rhyno postfix/pipe[29532]: fatal: user= command-line > attribute specifies root privileges > > so it's entirely possible i'm knocking on the wrong door, and instead > i should be asking this in the postfix mailing list. > > however, i'm also worried about this: "to bypass this check, set: > service auth { unix_listener /var/run/dovecot/auth-userdb { mode=0777 > } }", as i have done what it says, and the check wasn't bypassed so > i'm wary about something bad coming up once i somehow fix this initial > UID problem. > > thanks, > a > > > 2018. 07. 31. 7:12 keltezéssel, Aki Tuomi írta: >> You could run dovecot-lda as root. It will setuid to correct account. >> >> >> >> --- >> Aki Tuomi >> Dovecot oy >> >> -------- Original message -------- >> From: Andras Kemeny <pdx(a)pdx.hu> >> Date: 31/07/2018 04:46 (GMT+02:00) >> To: dovecot(a)dovecot.org >> Subject: uid problem >> >> 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 >

1 0

2.3.2.1 - EC keys suppport?
by ѽ҉ᶬḳ℠ 31 Jul '18

31 Jul '18

Hi, facing [ no shared cipher ] error with EC private keys. This happens when the private key is generated with [ openssl ecparam -name brainpoolP512t1 -genkey ] with OpenSSL 1.1.0hh on the same machine Dovecot is running on. Tried some variations of [ ssl_cipher_list ] but to no avail - the [ no shared cipher ] error persists. Once the key is generated with [ openssl genpkey -algorithm RSA ] however the error is gone. Thus wondering whether (1) I am missing something or (2) this a bug or (3) there is no support for EC keys?

3 21

Re: dsync: expunge from pop3 does not replicate
by Jakub Lánský 31 Jul '18

31 Jul '18

Here is it # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.2 (5d6d7c92) # OS: Linux 4.4.0-112-generic x86_64 Ubuntu 16.04.4 LTS # Hostname: mda22 auth_cache_negative_ttl = 2 secs auth_cache_size = 16 M auth_cache_ttl = 1 mins auth_master_user_separator = / auth_mechanisms = plain login auth_verbose = yes default_client_limit = 2000 default_process_limit = 2000 default_vsz_limit = 16894 M deliver_log_format = %m %f/%e %s -> %e %p: %$ dict { sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext sqlsieve = mysql:/etc/dovecot/dovecot-dict-sqlsieve.conf.ext } disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_rcpt_check_quota = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c login_trusted_networks = 10.3.13.0/24 10.3.14.0/24 mail_gid = nogroup mail_home = /datastore/maildir/%d/%n mail_location = maildir:~/ mail_plugins = " quota mail_log notify old_stats replication" mail_uid = nobody maildir_copy_with_hardlinks = no 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 Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Inbox { auto = subscribe } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = subscriptions = yes type = private } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = box msgid from subject size mail_replica = tcp:10.3.13.51:54321 old_stats_command_min_time = 1 mins old_stats_domain_min_time = 12 hours old_stats_ip_min_time = 12 hours old_stats_memory_limit = 16 M old_stats_refresh = 30 secs old_stats_session_min_time = 15 mins old_stats_track_cmds = yes old_stats_user_min_time = 1 hours quota = dict:User quota::proxy::sqlquota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_grace = 50%% quota_warning = storage=95%% quota-warning 95 %u %d size quota_warning2 = messages=95%% quota-warning 95 %u %d count recipient_delimiter = + sieve = file:/datastore/sieve/%d/%n/;active=/datastore/sieve/%d/%n/active.sieve sieve_before = dict:proxy::sqlsieve;name=before_inbox_forward;bindir=/datastore/sieve/%d/%n/ sieve_max_actions = 32 sieve_max_redirects = 50 sieve_max_script_size = 1M sieve_redirect_envelope_from = recipient sieve_user_log = /datastore/sieve/%d/%n/.sieve.log } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_reuse_xuidl = yes pop3_save_uidl = yes protocols = " imap lmtp sieve pop3 sieve" replication_max_conns = 100 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = nobody } unix_listener replication-notify { mode = 0666 user = nobody } } service auth { inet_listener { port = 12345 ssl = yes } } service dict { unix_listener dict { group = nogroup user = nobody } } service doveadm { inet_listener { port = 54321 ssl = no } } service imap-login { process_limit = 32 process_min_avail = 8 service_count = 0 } service imap { process_limit = 16384 } service lmtp { executable = lmtp -L inet_listener lmtp { port = 24 ssl = no } process_min_avail = 5 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 2 service_count = 1 vsz_limit = 196 M } service managesieve { process_limit = 2048 } service old-stats { fifo_listener old-stats-mail { mode = 0666 user = nobody } inet_listener { address = 127.0.0.1 port = 24242 } } service pop3 { process_limit = 2048 } service quota-warning { executable = script /etc/dovecot/quota-warning.sh unix_listener quota-warning { mode = 0666 user = nobody } user = nobody } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 user = nobody } } service stats { idle_kill = 5 mins unix_listener stats-reader { group = nogroup mode = 0666 user = nobody } unix_listener stats-writer { group = nogroup mode = 0666 user = nobody } } ssl_cert = </etc/dovecot/private/mda.vshosting.cloud/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes submission_host = 10.3.14.30:587 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota mail_log notify old_stats replication sieve" } protocol lda { mail_plugins = " quota mail_log notify old_stats replication sieve" } protocol imap { mail_max_userip_connections = 50 mail_plugins = " quota mail_log notify old_stats replication imap_quota imap_old_stats" } protocol sieve { managesieve_max_line_length = 65536 } protocol pop3 { mail_max_userip_connections = 50 } -- Jakub Lánský IT administration/support technician jakub(a)lansky.biz GSM: +420776172737 Jabber/GTalk: lenny(a)blesmrt.net -------- Původní zpráva -------- Od: Aki Tuomi <aki.tuomi(a)dovecot.fi> Komu: Jakub Lánský <jakub(a)lansky.biz>, dovecot(a)dovecot.org Předmět: Re: dsync: expunge from pop3 does not replicate Datum: Wed, 25 Jul 2018 14:04:14 +0300 Please provide doveconf -n --- Aki Tuomi Dovecot oy -------- Original message -------- From: Jakub Lánský <jakub(a)lansky.biz> Date: 25/07/2018 11:37 (GMT+02:00) To: dovecot(a)dovecot.org Subject: dsync: expunge from pop3 does not replicate Hi, I'm using dovecot 2.3.2.1 on Xenial from upstream packages on two Dovecot servers connected with dsync over TCP. E-mails which are deleted via POP3 protocol are not correctly deleted on second server via dsync. Jul 25 09:29:19 mda11 dovecot: pop3(jakub@***)<7587><8xaJ1c1x9uEqAB7QADwAAAAAAAAAAL7v>: expunge: box=INBOX, msgid=<6a75db5d84ff257216a4340d7c0405b2(a)blesmrt.eu>, size=3238, from=lenny@***, subject=dovecot pop3 test Nothing happened on the second machine then. After running # doveadm replicator replicate "jakub@***", e-mail got expunged immediately on second server. Jul 25 09:50:56 mda22 dovecot: dsync- local(jakub@***)<Xt6oFy8nWFsjIwAA0YRh9g>: expunge: box=INBOX, msgid=< 6a75db5d84ff257216a4340d7c0405b2(a)blesmrt.eu>, size=3238, from=lenny@***, subject=dovecot pop3 test Any ideas what to do or test? Thank you

2 3

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