- dovecot - dovecot.org

question about using procmail
by Joe Wong 01 Aug '18

01 Aug '18

Hello, I am new to Dovecot, testing the setup with Solr FTS plugin. Currently I am using procmail to delivery email into user's mailbox. I am using maildir on file system. I found that if email is delivered via procmail, the indexer-worker is not being called. But when I move the email between folders via IMAP, indexer is involved. Is this expected? - Joe

3 5

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

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

Imap post-login script
by j.emerlik 27 Jul '18

27 Jul '18

Dovecot v.2.2.32 and I have configured two imap post-login scripts and it seems like after successfully login scripts are not closed (dovecot_node/imap imap-postlogin : multiple processes are running still) and after some times there are too many processes and the limit is reached (imap proces_limit 1500): 1) #!/bin/sh case $IP in 10.10.1[1-2][0-7].*) exec "$@" ;; 10.11.2.4[0-9]) exec "$@" ;; esac CHECK_USER=`PGPASSWORD="password" /usr/local/pg952/bin/psql -h 10.11.1.3 -q -t -U postfixuser -d mail -c "select imap_allowed from users where name = '$USER' LIMIT 1"` if [ $CHECK_USER == "t" ] ; then exec "$@" fi if [ $CHECK_USER == "f" ] ; then exit 0 fi 2) PGPASSWORD="password" /usr/local/pg952/bin/psql -U postfixuser -d mail2 -h 10.11.1.3 -c "select last_auth('$USER','$RIP2','1')" > /dev/null exec "$@" Regards, Jack

1 0

Aw: Re: Re: Re: Panic: Leaked view for index - virtual mailbox
by wertstoffe＠nurfuerspam.de 26 Jul '18

26 Jul '18

1 0

Aw: Re: Re: Re: Panic: Leaked view for index - virtual mailbox
by wertstoffe＠nurfuerspam.de 26 Jul '18

26 Jul '18

1 0

Panic: Leaked view for index - virtual mailbox
by Jakobus Schürz 26 Jul '18

26 Jul '18

Hi There! I run into this problem with virtual Mailboxes on release-2.3.2 (and also in master and in older versions of dovecot) I added the core-file. Jul 25 04:11:29 aldebaran dovecot[10573]: imap(jakob)<11292><rg2GZclxHaPAqADc>: Panic: Leaked view for index /var/lib/dovecot/db/indexes/Maildir/jakob/&ANY-BB/dovecot.index: Opened in index-storage.c:338 Jul 25 04:11:29 aldebaran dovecot[10573]: imap(jakob)<11292><rg2GZclxHaPAqADc>: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0xcedf1) [0x7ffad9ac0df1] -> /usr/local/lib/dovecot/libdovecot.so.0(+ 0xceeba) [0x7ffad9ac0eba] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ffad9a2efe8] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xf7022) [0x7ffad9c66022] -> /usr/local/lib/dovecot/libdovecot-s torage.so.0(index_storage_mailbox_close+0x9a) [0x7ffad9c3d72a] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) [0x7ffad9bbb1aa] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0xab80) [0 x7ffad9792b80] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_backend_box_open+0x2b) [0x7ffad9792d3b] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_storage_sync_init+0x12a9) [0x7ffad9795f1 9] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x51) [0x7ffad9bbd6d1] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7ffad9bbd787] -> /usr/local/lib/dovecot/libdo vecot-storage.so.0(index_storage_get_status+0x31) [0x7ffad9c3bed1] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0x9ead) [0x7ffad9791ead] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xb0f83) [0x7ffad 9c1ff83] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x10602) [0x7ffad97b4602] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0xf813) [0x7ffad99e9813] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox _get_status+0x31) [0x7ffad9bbdb91] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_storage_sync_init+0xf0b) [0x7ffad9795b7b] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x51) [0 x7ffad9bbd6d1] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7ffad9bbd787] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7ffad9c3bed1] -> /usr/loca l/lib/dovecot/lib20_virtual_plugin.so(+0x9ead) [0x7ffad9791ead] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xb0f83) [0x7ffad9c1ff83] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x10602) [0x7ffad97b460 2] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0xf813) [0x7ffad99e9813] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7ffad9bbdb91] -> /usr/local/lib/dovecot/lib20_virtual_plug in.so(virtual_storage_sync_init+0xf0b) [0x7ffad9795b7b] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x51) [0x7ffad9bbd6d1] Jul 25 04:11:29 aldebaran dovecot[10573]: imap(jakob)<11292><rg2GZclxHaPAqADc>: Fatal: master: service(imap): child 11292 killed with signal 6 (core dumped) Jul 25 04:11:29 aldebaran dovecot[10573]: auth: Debug: client in: AUTH 19 PLAIN service=imap secured=tls session=9KKNZclxHqPAqADc lip=192.168.0.14 rip=192.168.0.2 20 lport=143 rport=41758 local_name=aldebaran.xundeenergie.at ssl_cipher=ECDHE-RSA-AES128-GCM-SHA256 ssl_cipher_bits=128 ssl_pfs=KxECDHE ssl_protocol=TLSv1.2 Jul 25 04:11:29 aldebaran dovecot[10573]: auth: Debug: client passdb out: CONT 19 Jul 25 04:11:29 aldebaran dovecot[10573]: auth: Debug: client in: CONT<hidden> Jul 25 04:11:29 aldebaran dovecot[10573]: auth: Debug: passwd-file(jakob,192.168.0.220,<9KKNZclxHqPAqADc>): lookup: user=jakob file=/usr/local/etc/dovecot/users Jul 25 04:11:29 aldebaran dovecot[10573]: auth: Debug: client passdb out: OK 19 user=jakob Jul 25 04:11:29 aldebaran dovecot[10573]: auth: Debug: master in: REQUEST 2436366337 10570 19 dd4c468bbfe617d4ef06a1b8ce6c111d session_pid=11298 request_auth_token Jul 25 04:11:29 aldebaran dovecot[10573]: auth: Debug: passwd-file(jakob,192.168.0.220,<9KKNZclxHqPAqADc>): lookup: user=jakob file=/usr/local/etc/dovecot/users Jul 25 04:11:29 aldebaran dovecot[10573]: auth: Debug: master userdb out: USER 2436366337 jakob home=/var/mail/jakob acl_groups=home,admin auth_token=3ea3b630e131 3bf5beb0f26ff740450189f63e3e Jul 25 04:11:29 aldebaran dovecot[10573]: imap-login: Login: user=<jakob>, method=PLAIN, rip=192.168.0.220, lip=192.168.0.14, mpid=11298, TLS, session=<9KKNZclxHqPAqADc> Jul 25 04:11:29 aldebaran dovecot[10573]: imap(jakob)<11298><9KKNZclxHqPAqADc>: Panic: Leaked view for index /var/lib/dovecot/db/indexes/Maildir/jakob/&ANY-BB/dovecot.index: Opened in index-storage.c:338 Jul 25 04:11:29 aldebaran dovecot[10573]: imap(jakob)<11298><9KKNZclxHqPAqADc>: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0xcedf1) [0x7fbd982b2df1] -> /usr/local/lib/dovecot/libdovecot.so.0(+ 0xceeba) [0x7fbd982b2eba] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbd98220fe8] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xf7022) [0x7fbd98458022] -> /usr/local/lib/dovecot/libdovecot-s torage.so.0(index_storage_mailbox_close+0x9a) [0x7fbd9842f72a] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) [0x7fbd983ad1aa] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0xab80) [0 x7fbd97f84b80] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_backend_box_open+0x2b) [0x7fbd97f84d3b] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_storage_sync_init+0x12a9) [0x7fbd97f87f1 9] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x51) [0x7fbd983af6d1] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7fbd983af787] -> /usr/local/lib/dovecot/libdo vecot-storage.so.0(index_storage_get_status+0x31) [0x7fbd9842ded1] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0x9ead) [0x7fbd97f83ead] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xb0f83) [0x7fbd9 8411f83] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x10602) [0x7fbd97fa6602] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0xf813) [0x7fbd981db813] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox _get_status+0x31) [0x7fbd983afb91] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_storage_sync_init+0xf0b) [0x7fbd97f87b7b] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x51) [0 x7fbd983af6d1] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7fbd983af787] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7fbd9842ded1] -> /usr/loca l/lib/dovecot/lib20_virtual_plugin.so(+0x9ead) [0x7fbd97f83ead] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xb0f83) [0x7fbd98411f83] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x10602) [0x7fbd97fa660 2] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0xf813) [0x7fbd981db813] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7fbd983afb91] -> /usr/local/lib/dovecot/lib20_virtual_plug in.so(virtual_storage_sync_init+0xf0b) [0x7fbd97f87b7b] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x51) [0x7fbd983af6d1] Jul 25 04:11:30 aldebaran dovecot[10573]: imap(jakob)<11298><9KKNZclxHqPAqADc>: Fatal: master: service(imap): child 11298 killed with signal 6 (core dumped) jakob

4 12

doveadm who reverse dns lookups
by Michael Grant 25 Jul '18

25 Jul '18

Perhaps this is a feature request... It would be nice if the ‘doveadm who’ command printed out the reverse dns name of where the user was logged in from. Would it be possible to either add some option to doveadm who for this, or make it the do it by default and add a ‘-n’ option (like many of the other programs that look up ip addresses by default) and take a -n option to not do that? Not sure if that would break some existing thing which is why I hesitate. Might be safer to add, say, a -r option to do the rDNS lookup. However, it would definitely save me a step in figuring out where someone was logged in from to know if it’s legit. Michael Grant

3 2

Re: doveadm expunge didn't clear Trash mailbox
by Joseph Tam 25 Jul '18

25 Jul '18

On Mon, 23 Jul 2018, Michael Wagner wrote: > here works a dovecot 2.2.27 on a raspberrypi and the behaviour is as > expected. > > doveadm -f tab fetch -u <user> "uid date.saved" mailbox Trash > uid date.saved > 314 2018-06-23 00:35:59 > 315 2018-06-23 12:39:10 > 316 2018-06-24 10:32:43 > ... > > And I have a cron script that expunges the mails older than 30 days. > /usr/bin/doveadm expunge -u <user> mailbox Trash savedbefore 30d Hi Michael, Thanks for your observation. I think you probably use maildir format, yes? I think my problem stems from the fact I use mbox, so one file contains many messages, whereas maildir uses one file for each message. Dovecot, from my understanding, will use the message file's mtime for date.saved if it doesn't have it in the cached. This is probably why I am seeing multiple messages with the same value. What's confusing is that if I query a message's date.saved, that value -- whether from the cache or the mailbox's mtime -- remains in the cache, so the next query will give me that value. So running "doveadm fetch ... date.saved", will get the mailbox's mtime at the time I fetched those values. In order to get near accurate date.saved values, I would have to run "doveadm fetch ... date.saved" frequently. (I think this behaviour must have changed recently because this no longer works consistently.) However, if each message is stored in a separate file (like maildir does), then each message can have an accurate date.saved(=mtime). Once you have accurate date.saved, then the "expunge savedbefore" works correctly. Another reason I really ought to switch to maildir. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: Panic: Leaked view for index - virtual mailbox
by Jakob Schuerz 25 Jul '18

25 Jul '18

1 0