- dovecot - dovecot.org

mdbox + alt storage + purge = wtf ...
by Matt Bryant 14 Jul '18

14 Jul '18

All, Is there a bug in doveadm purge ? Configured alt storage and move messages in inbox to the alternate path all well and good. However, after deleting some messages and running a purge on the mailbox found that all messages got recopied over to primary location. I guess this maybe because its re-writing the file and ditching the purged mail .. but shouldnt it keep a track that they were located on alt storage path ?? rgds Matt

1 0

Question about verbose_proctitle
by J Doe 13 Jul '18

13 Jul '18

Hello, I have a question relating to the detail that the verbose_proctitle parameter enables for ps. I have TLS configured for IMAP as follows: /etc/dovecot/dovecot.conf ssl = required ssl_cert = </path/to/cert.pem> ssl_key = </path/to/key.pem> protocols = imap lmtp service imap-login { # Disable insecure IMAP over TCP 143 inet_listener imap { port=0 } } . . . verbose_proctitle = yes If I have a single MUA connect (Apple Mail in this case), I see: $ ps aux | grep -i dovevot dovenull 5552 0.0 0.1 18820 5444 ? S 18:53 0:00 dovecot/imap-login [1 connections (1 TLS)] vmail 5553 0.3 0.1 13612 4304 ? S 18:53 0:00 dovecot/imap [user(a)example.com 1.2.3.4 IDLE] The first part makes sense to me - imap-login is showing the user being connected via imap-login and with TLS. The second part, however, shows the IMAP session with the username, IP address and IMAP command (IDLE), but it does not state TLS. Does this mean that I have logins for IMAP connections protected by TLS but the actual IMAP traffic (mail contents, etc.), is *NOT* configured to use TLS ? That is to say, IMAP traffic is flowing over port 993 without TLS ? From the wiki [1] it appears to state that I only have to configure TLS settings for IMAP if the IMAP protocol is being secured via a *DIFFERENT* TLS certificate. Is this correct ? Thanks, - J Sources: [1] https://wiki2.dovecot.org/SSL/DovecotConfiguration

2 3

Whitelist file for LDAP authentication
by whpang 13 Jul '18

13 Jul '18

Hi, The dovecot version is 2.2.33.2 and we are using LDAP to do the authentication for SMTP service. We have the following configuration in auth-ldap.conf.ext to deny some users for LDAP auth. passdb { args = /etc/dovecot/deny.smtp driver = passwd-file deny = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } And now we want to change the mechanism and only users in the list can send to LDAP auth and deny all others: passdb { args = /etc/dovecot/allow.smtp driver = passwd-file deny = no result_failure = return-fail result_internalfail = return-fail result_success = continue-fail } passdb { # Path for LDAP configuration file, see example-config/dovecot-ldap.conf.ext args = /etc/dovecot/dovecot-ldap.conf driver = ldap } Since we do not have the users’ password in the plain text file “allow.smtp”, the authentication process will fail and exit in the first passdb. Anyone can help to advice how to configure dovecot to have a whitelist for user LDAP authentication? Thank you very much. Best regards, William Pang Academic Computing and Technology Services Section Information and Communication Technology Office University of Macau Tel: 8822 8407

3 2

Pigeonhole extdata repo?
by tai74＠vfemail.net 12 Jul '18

12 Jul '18

Pigeonhole download page has links for extdata plugin up to v0.4 but nothing more and no link to the master repository https://pigeonhole.dovecot.org/download.html I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. Thanks for helping ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!

3 4

sievescript is not working
by ratatouille 12 Jul '18

12 Jul '18

Hello! I have a problem with a sieve-script which works for one domain but not for another one. Both domains are hostet on the same server running dovecot and postfix. This is the script that works: require ["vacation"]; # rule:[Out of office] if true { vacation :days 1 :addresses "a.meyer(a)nimmini.de" :subject "absent" "Ich bin nicht da."; } This one does not, a vacation message is not sent: require ["vacation"]; # rule:[Out of office] if true { vacation :days 1 :addresses "a.meyer(a)bitcorner.de" :subject "absent" "Ich bin nicht da."; } I don't know why. A sieve-test shows # sieve-test ./managesieve.sieve ./testfile -D sieve-test(andreas): Debug: sieve: Pigeonhole version 0.4.2 initializing sieve-test(andreas): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. debug: script binary ./managesieve.svbin is not up-to-date. debug: script `managesieve' from ./managesieve.sieve successfully compiled. Performed actions: * send vacation message: => seconds : 86400 => subject : Nicht im Büro => handle : Bin bis zum 25.06.2018 nicht im Büro. Email wird beantwortet, sobald ich wieder zurück bin.Nicht im Büro<default-from><NO-MIME> START MESSAGE Bin bis zum 25.06.2018 nicht im Büro. Email wird beantwortet, sobald ich wieder zurück bin. END MESSAGE Implicit keep: * store message in folder: INBOX sieve-test(andreas): Info: final result: success Any help appreciated! Kind regards Andreas

3 3

Sieve_default
by ＠lbutlr 12 Jul '18

12 Jul '18

I created a sieve_default to move any spam-tagged messages into the Junk mailbox automatically, but it doesn’t appear to be working (though the other imapsieve_mailbox… scripts are working). From doveconf -n plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/usr/lib/dovecot/sieve/mark-read.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = Archive sieve = file:~/.sieve;active=~/.active_sieve sieve_default = /usr/lib/dovecot/sieve/default.sieve sieve_default_name = spamassassin sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } And # cat /usr/lib/dovecot/sieve/default.sieve if header :contains "X-spam-flag" "YES" { fileinto "Junk"; } There are no user sieve files # find /home -name "*sieve*" -type f # The x-spam-flag header in the message in my mailbox is definitely there and definitely set to yes.

5 9

Re: LMTP crashing heavily for my 2.2.36 installation (and now with 2.3.2.1)
by Wolfgang Rosenauer 12 Jul '18

12 Jul '18

Hi, I will try to create a coredump later but now I see version 2.3.2.1 also crashing in LMTP :-( 2018-07-12T10:09:57.336062+02:00 saruman dovecot: lmtp(an007498)<11814><zrPDEdUMR1smLgAAQ/KzDw>: Fatal: master: service(lmtp): child 11814 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) 2018-07-12T10:09:57.382925+02:00 saruman dovecot: lmtp(an007498)<11819><fqw2E9UMR1srLgAAQ/KzDw>: Panic: file imap-bodystructure.c: line 116 (part_write_body_multipart): assertion failed: (part->data != NULL) 2018-07-12T10:09:57.383835+02:00 saruman dovecot: lmtp(an007498)<11819><fqw2E9UMR1srLgAAQ/KzDw>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc9e06) [0x7ff42cac0e06] -> /usr/lib64/dovecot/libdovecot.so.0(+0xc9ebe) [0x7ff42cac0ebe] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff42ca35813] -> /usr/lib64/dovecot/libdovecot.so.0(imap_bodystructure_write+0x3b1) [0x7ff42ca95f81] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xbd397) [0x7ff42ce2b397] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xc005c) [0x7ff42ce2e05c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_special+0x20d) [0x7ff42ce2e4cd] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_special+0xd) [0x7ff42cdb0b6d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_set_attachment_keywords+0x162) [0x7ff42cdb0f42] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xbdd25) [0x7ff42ce2bd25] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xbe10b) [0x7ff42ce2c10b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_parts+0x60) [0x7ff42ce2dcd0] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_parts+0x28) [0x7ff42cdb04d8] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x2f11e) [0x7ff4285e611e] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_message_body_get_text+0x38) [0x7ff4285e76a8] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(ext_body_get_part_list+0x47) [0x7ff42861b187] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x648d2) [0x7ff42861b8d2] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0x71) [0x7ff4285f8611] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7ff4285f886b] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x53fb2) [0x7ff42860afb2] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_multiscript_run+0x38) [0x7ff42860bd28] -> /usr/lib64/dovecot/modules/lib90_sieve_plugin.so(+0x3907) [0x7ff428873907] -> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver+0xdc) [0x7ff42d0c41cc] -> dovecot/lmtp(lmtp_local_data+0x6eb) [0x55d90309e95b] -> dovecot/lmtp(cmd_data_continue+0x23d) [0x55d90309d4ed] -> /usr/lib64/dovecot/libdovecot.so.0(+0x507f0) [0x7ff42ca477f0] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55) [0x7ff42cad7b35] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7ff42cad9307] I'm still on maildir and my current setting about attachments is: mail_attachment_detection_options = add-flags-on-save exclude-inlined Wolfgang

1 0

Re: LMTP crashing heavily for my 2.2.36 installation
by Wolfgang Rosenauer 12 Jul '18

12 Jul '18

On Wed, Jul 11, 2018 at 6:03 PM, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > One alternative is to migrate into sdbox format, in which this is supported > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Wolfgang Rosenauer <wrosenauer(a)gmail.com> > Date: 11/07/2018 18:14 (GMT+02:00) > To: Timo Sirainen <tss(a)iki.fi> > Cc: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Re: LMTP crashing heavily for my 2.2.36 installation > > follow up question. > > Is there a commit which is reasonable to backport for me into the packages > or is it too intrusive or based on heavily changed code? > > > Thanks, > Wolfgang > > On Wed, Jul 11, 2018 at 3:32 PM, Wolfgang Rosenauer <wrosenauer(a)gmail.com> > wrote: > >> >> On Wed, Jul 11, 2018 at 10:46 AM, Timo Sirainen <tss(a)iki.fi> wrote: >> >>> On 11 Jul 2018, at 8.41, Wolfgang Rosenauer <wrosenauer(a)gmail.com> >>> wrote: >>> > >>> > I'm running 2.2.36 (as provided by openSUSE in their server:mail >>> repository) and at least at one of my systems LMTP is crashing regularly on >>> certain messages (apparently a lot of them). >>> > >>> > Sometimes (but not always a backtrace is posted to the logs: >>> > >>> > 2018-07-11T07:34:56.741848+02:00 saruman dovecot: lmtp(14690): Fatal: >>> master: service(lmtp): child 14690 killed with signal 11 (core dumps >>> disabled) >>> > 2018-07-11T07:34:56.820474+02:00 saruman dovecot: lmtp(an007498): >>> Panic: file imap-bodystructure.c: line 116 (part_write_body_multipart): >>> assertion failed: (part->data != NULL) >>> .. >>> > storage.so.0(mail_set_attachment_keywords+0x162) [0x7ff549773662] >>> >>> Looks like it's because of the "mail_attachment_detection_options = >>> add-flags-on-save" setting. What mailbox format do you use? It's currently >>> broken with mbox and in v2.2.36 with Maildir (which was fixed in v2.3.2). >>> >>> I'm indeed using maildir so this is a known issue and yes I use >> mail_attachment_detection_options=add-flags-on-save (or rather I tried >> to but now have to disable it). Not sure when I get to upgrade to 2.3.x. >> >> >> Thanks, >> Wolfgang >> > >

1 1

Re: Authentication failure with OpenLDAP
by Anushka Bandara 12 Jul '18

12 Jul '18

Hi all, Thank you all for the help. The was with the ldap user attributes. I corrected it. Now I am having an error with dovecot. User can log into ldap but, system doesn't allow user to create user's directory in Maildir. Error is below, * Error: User initialization failed: Namespace '': mkdir(/home/users/"user"/Desktop/Maildir) failed: Permission denied (euid=1000(myuser) egid=5000(<unknown>) missing +w perm: /home, we're not in group 100(users), dir owned by 0:100 mode=0775)* How should I give the permission to overcome this error. This is a dovecot error. LDAP authentication is successful. And also, I don't know the default user whom is creating mail directories for mail users. I think the problem will be solved if I grant user the permission. But I don't know how to grant. Best regards, Anushka Bandara Research Engineer, Lanka Software Foundation +94715846018 On Tue, Jul 10, 2018 at 2:54 PM, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > Turn on auth_verbose=yes and auth_debug=yes and post logs. > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Anushka Bandara <anushkab(a)opensource.lk> > Date: 10/07/2018 08:53 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Authentication failure with OpenLDAP > > Hi all, > > > *Dovecot version: 2.2.22 (fe789d2)* > > *Ubuntu version: 16.04* > *OpenLDAP version: openldap-2.4.42+dfsg* > > Configurations > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > *# 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf# Pigeonhole version 0.4.13 > (7b14904)# OS: Linux 4.10.0-28-generic x86_64 Ubuntu 16.04.3 LTS > disable_plaintext_auth = nolisten = *log_path = > /var/log/dovecot.logmail_location = maildir:~/Maildirnamespace 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}protocols = pop3 > imapservice auth { unix_listener /var/spool/postfix/private/auth { mode > = 0666 }}ssl = nouserdb { args = /etc/dovecot/dovecot-ldap.conf.ext > driver = ldap}* > I am having "*Authentication failed" *problem with dovecot-ldap. Before > it, I had binding error and I fixed it. Now I am having authentication > problem when I am trying to log dovecot (usign telnet localhost 110) using > a user which is created in ldap server. I can provide any configuration > file and I did this configurations according to this " > https://help.ubuntu.com/community/DovecotLDAP". > Now I am having an authentication error. > > Thank you > >

2 2

Storing Messages in the cloud
by Jerry 12 Jul '18

12 Jul '18

A colleague asked me if it was possible for Dovecot to store messages in the cloud. I have not heard of it being done and therefore assume it is not possible, but I thought I would ask regardless. I tried checking on the “One Drive” forum; however, I have not received any response back yet. Thanks! -- Jerry

7 6