- dovecot - dovecot.org

Replication problems
by Thomas Kristensen 19 Jul '18

19 Jul '18

Hey I am trying to setup a dovecot cluster with 2 servers using replication /dsync. In front of it I got a Fortinet ADC (Load balance) and I think that I messing up the dsync. I see mails duplicated in the sync progress. If I disable one of the servers in the ADC, it seems to work and the sync if working without a problem. But if I use both servers with a round robin on the ADC, I see mailed duplicated. Ex. I sent 100 mails thru the SMTP (Postfix) and 107 mails is in both servers, but as said before, if I disable one of the servers in the ADC, I see the correct amount of mails in both dovecot servers. In the header of the duplicated mails I see the exact same postfix id and LMTP id from dovecot. Also I cant seem to get any log from the sync progress. Med venlig hilsen Thomas Kristensen [MM_mail_logo_3_AS] Storhaven 12 - 7100 Vejle Tlf: 75 72 54 99 - Fax: 75 72 65 33 E-mail: tk(a)multimed.dk<mailto:tk@multimed.dk>

2 1

Re: Sendmail Dovecot Trouble
by John Rowan 19 Jul '18

19 Jul '18

/var/mail is a symlink to /var/spool/mail I tried both, neither works. I just wiped out the server, reinstalled from scratch this time I selected e-mail server while selecting packages after specifying GUI-server on the CentOS install. I had previously installed Dovecot after the initial server build. This time Dovecot was installed and active at boot but still can't find my mail in /var/spool/mail. On 7/13/2018 11:44 AM, Aki Tuomi wrote: > Should your INBOX path be /var/spool/mail/%u then? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: John Rowan <rowan(a)rownetco.com> > Date: 13/07/2018 17:44 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Sendmail Dovecot Trouble > > I've been struggling trying to get Thunderbird to read e-mail off a > CentOS 7 server. > > Sendmail writes mail in /var/spool/mail > > I've configured dovecot to try to read from there using Thunderbird > (POP3/SMTP). > > The firewall allows ports 25/110. > > I verified I have mail in /var/spool/mail > > but Thunderbird is unable to retrieve that mail. > > I've googled sendmail / dovecot config, I've looked a the wiki but I > just can't figure this out. > > Please don't suggest using postfix, I just want to get sendmail / > dovecot working. > > > [@mail conf.d]# dovecot --version > 2.2.10 > > [root@mail conf.d]# dovecot -n > # 2.2.10: /etc/dovecot/dovecot.conf > # OS: Linux 3.10.0-327.36.3.el7.i686 i686 CentOS Linux release 7.2.1511 > (AltArch) > auth_mechanisms = plain login > disable_plaintext_auth = no > > mail_location = mbox:~/mail:INBOX=/var/mail/%u > > 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 { > driver = pam > } > protocols = > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > ssl_key = </etc/pki/dovecot/private/dovecot.pem > userdb { > driver = passwd > } > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus >

2 1

Force a user to use POP3
by John Doe Vecot 18 Jul '18

18 Jul '18

[dovecot-2.3.2.1] I have dovecotrunning icw postfixandhave IMAP and POP3 available to retrieve mail. Can you tell me how I can configure Dovecot in order to force certain users to use POP3 (download messages) only? Thanks, Jos

3 2

Re: Sendmail Dovecot Trouble
by John Rowan 18 Jul '18

18 Jul '18

Having reinstalled CentOS 7 including e-mail server in initial software configuration it installed Postfix/Dovecot. I've been using Sendmail for 20 years and no experience with Postfix. Looked in Webmin -> servers -> Postfix and specified Maildir, changed the 10-mail.conf to specify mail_location = maildir:~/Maildir and everything's working. Thanks for help. On 7/13/2018 11:44 AM, Aki Tuomi wrote: > Should your INBOX path be /var/spool/mail/%u then? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: John Rowan <rowan(a)rownetco.com> > Date: 13/07/2018 17:44 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Sendmail Dovecot Trouble > > I've been struggling trying to get Thunderbird to read e-mail off a > CentOS 7 server. > > Sendmail writes mail in /var/spool/mail > > I've configured dovecot to try to read from there using Thunderbird > (POP3/SMTP). > > The firewall allows ports 25/110. > > I verified I have mail in /var/spool/mail > > but Thunderbird is unable to retrieve that mail. > > I've googled sendmail / dovecot config, I've looked a the wiki but I > just can't figure this out. > > Please don't suggest using postfix, I just want to get sendmail / > dovecot working. > > > [@mail conf.d]# dovecot --version > 2.2.10 > > [root@mail conf.d]# dovecot -n > # 2.2.10: /etc/dovecot/dovecot.conf > # OS: Linux 3.10.0-327.36.3.el7.i686 i686 CentOS Linux release 7.2.1511 > (AltArch) > auth_mechanisms = plain login > disable_plaintext_auth = no > > mail_location = mbox:~/mail:INBOX=/var/mail/%u > > 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 { > driver = pam > } > protocols = > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > ssl_key = </etc/pki/dovecot/private/dovecot.pem > userdb { > driver = passwd > } > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus >

1 0

best practices for migrating to new dovecot version
by Shawn Heisey 18 Jul '18

18 Jul '18

I have a machine with my mail service on it running Debian Squeeze. The version of dovecot on that server is 1.2.15. I'm building a new server with Ubuntu 18.04 (started with 16.04, upgraded in place), where the dovecot version is 2.2.33. I plan to migrate all my services to this new machine. The virtual mailboxes are on disk in maildir format, with accounts in a mysql database managed by postfixadmin. When I copy them over to the new machine, would there be any value to excluding the files that dovecot creates, and letting the new version recreate them? In one mailbox here are some of the files I am considering excluding: dovecot.index dovecot.index.cache dovecot.index.log dovecot.index.thread dovecot-keywords dovecot-uidlist dovecot-uidvalidity dovecot-uidvalidity.5876ca77 There are other files under consideration, like maildirsize and maildirfolder. One that I would be sure to *not* remove is subscriptions. If there are recommendations about dovecot files in a maildir that should not be removed during a migration, please let me know. I'm aware that rebuilding this information could be slow. My own personal mailbox on the system is over 8GB in size and has well over nine hundred thousand files in it. Thanks, Shawn

4 3

Dovecot Quota and subject utf-8
by Danilo G. Baio 18 Jul '18

18 Jul '18

Hi. When a user is over quota and a message is rejected, it sends a message back changing partially the subject (depending on the size). With utf-8 it breaks the information, we noticed this behavior when the subject line uses utf-8 and it is broken in more than one line: Subject: Quêm casé erat vim id, vix ín dicit putânt, minim çónsequuntur ea iús. Agam cetêro tê eôs, ád vim ipsum tantâs expetêndis. Ut prõ vidit diçit iudicabit, cum út çômmódo Subject of a delivered message: Subject: =?UTF-8?Q?Qu=C3=AAm_cas=C3=A9_erat_vim_id=2C_vix_=C3=ADn_dicit_p?= =?UTF-8?Q?ut=C3=A2nt=2C_minim_=C3=A7=C3=B3nsequuntur_ea_i=C3=BAs=2E_Agam_?= =?UTF-8?Q?cet=C3=AAro_t=C3=AA_e=C3=B4s=2C_=C3=A1d_vim_ipsum_tant=C3=A2s_e?= =?UTF-8?Q?xpet=C3=AAndis=2E_Ut_pr=C3=B5_vidit_di=C3=A7it_iudicabit=2C_cum?= =?UTF-8?Q?_=C3=BAt_=C3=A7=C3=B4mm=C3=B3do?= Subject of a message rejected with Dovecot Quota: Subject: Rejected: =?UTF-8?Q?Qu=C3=AAm_cas=C3=A9_erat_vim_id=2C_vix_=C3=ADn_dicit_p?=? =?... Auto-Submitted: auto-replied (rejected) Precedence: bulk https://pastebin.com/raw/SWJJARga Regards. -- Danilo G. Baio (dbaio)

1 0

Dovecot and Sieve setup
by Will Merkens 17 Jul '18

17 Jul '18

I thought I had sieve working I could create the rules in TB and it says it's communicating properly and saves the file but the sieve rules do not seem to be working. when I look at /var/spool/maildir/domain/user I see Maildir Maildir =uid=1000 inside Maildir =uid=1000/sieve I see my sieve script I created Test.sieve and a tmp directory Should not this be in the main Maildir/sieve directory. -- William Merkens IT Support Analyst Userful Corporation +1 403.538.7767 ext.289 +1 866.873.0091 Suite 300 736 8th Ave SW Calgary AB T2P 1H4 Canada https://www.userful.com

2 1

dsync panic
by Infoomatic 16 Jul '18

16 Jul '18

Hi, I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder): /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser dsync(standl2): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(standl2): Error: Raw backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb6fa) [0x7f43679986fa] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb769) [0x7f4367998769] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f43679069c1] -> /opt/dovecot/lib/dovecot/libdovecot-storage.so.0(+0x568ff) [0x7f4367c9d8ff] -> /opt/dovecot/bin/doveadm(dsync_mailbox_import_attribute+0x4d) [0x56234f7b68dd] -> /opt/dovecot/bin/doveadm(dsync_brain_sync_mails+0x2fd) [0x56234f7b217d] -> /opt/dovecot/bin/doveadm(dsync_brain_run+0x538) [0x56234f7adb28] -> /opt/dovecot/bin/doveadm(+0x27fec) [0x56234f793fec] -> /opt/dovecot/bin/doveadm(+0x2a0e7) [0x56234f7960e7] -> /opt/dovecot/bin/doveadm(+0x2ad7b) [0x56234f796d7b] -> /opt/dovecot/bin/doveadm(doveadm_mail_try_run+0x1fa) [0x56234f79769a] -> /opt/dovecot/bin/doveadm(main+0x45b) [0x56234f786b2b] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f4367523830] -> /opt/dovecot/bin/doveadm(_start+0x29) [0x56234f786ca9] regards, infoomatic

5 8

ssl_dh required, even though DH is disabled.
by Eric Toombs 16 Jul '18

16 Jul '18

Here's my config: # 2.3.2 (582970113): /etc/dovecot/dovecot.conf # OS: Linux 4.17.5-1-ARCH x86_64 Arch Linux # Hostname: vault passdb { driver = pam } protocols = imap service imap-login { inet_listener imap { port = 0 } } ssl = required ssl_cert = </etc/letsencrypt/live/myhostname.com/fullchain.pem ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384 ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 My filesystem is ext4. Even though I use ssl_cipher_list to forbid DH, dovecot still doesn't work unless I provide an ssl_dh, delivering the following error: Jul 14 21:48:08 vault dovecot[8349]: imap-login: Error: Failed to initialize SSL server context: Couldn't parse DH parameters: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: DH PARAMETERS: user=<>, rip=10.0.0.1, lip=10.0.0.2, session=<4sGi5/9w3pwKAAAB> While providing an ssl_dh is only a minor annoyance, it would be nice if I didn't have to.

2 1

Re: Letsencrypt certificate for repo.dovecot.org expired May 14th..
by DurgaPrasad - DatasoftComnet 15 Jul '18

15 Jul '18

:) Rgds/DP 9849111010 Sent from my iPhone. Pls excuse brevity and typos if any. > On 15-Jul-2018, at 5:00 PM, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > > certbot clearly hates me > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: "B. Reino" <reinob(a)bbmk.org> > Date: 15/07/2018 11:49 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Cc: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Re: Letsencrypt certificate for repo.dovecot.org expired May 14th.. > > Dear Aki, > > I think the renewal failed again. The SSL certificate expired Saturday, > 14 July 2018. > > This affects (at least) the repo.dovecot.org website and debian > repository. > > Thanks, > Bernardo. > > On 2018-05-15 08:15, Aki Tuomi wrote: > > On 15.05.2018 09:14, B. Reino wrote: > >> Dear all, > >> > >> Just in case you've missed it, the certificate for repo.dovecot.org > >> just expired yesterday. > >> > >> This causes errors in e.g. apt-get update. > >> > >> Thanks in advance for fixing it, > >> > >> -- > >> B. Reino > > > > Seems something went wrong during deployment, thanks. It's fixed now. > > > > Aki

1 0

Connection closed (IDLE running for 0.001 + waiting input for
by Sophie Loewenthal 15 Jul '18

15 Jul '18

Hi, Just noticed an Android email client called K9 Mail is producing these entries in a server's dovecot log: Jul 11 21:03:28 mx1 dovecot: imap(me(a)example.org): Connection closed (IDLE running for 0.001 + waiting input for 1728.597 secs, 2 B in + 10+0 B out, state=wait-input) in=353 out=2154 Jul 11 21:03:31 mx1 dovecot: imap(me(a)example.org): Connection closed (IDLE running for 0.001 + waiting input for 1731.069 secs, 2 B in + 10+0 B out, state=wait-input) in=389 out=1910 I cannot find out what this means after googling. Any ideas? Best wishes, Sophie

2 1

Sendmail Dovecot Trouble
by John Rowan 14 Jul '18

14 Jul '18

I've been struggling trying to get Thunderbird to read e-mail off a CentOS 7 server. Sendmail writes mail in /var/spool/mail I've configured dovecot to try to read from there using Thunderbird (POP3/SMTP). The firewall allows ports 25/110. I verified I have mail in /var/spool/mail but Thunderbird is unable to retrieve that mail. I've googled sendmail / dovecot config, I've looked a the wiki but I just can't figure this out. Please don't suggest using postfix, I just want to get sendmail / dovecot working. [@mail conf.d]# dovecot --version 2.2.10 [root@mail conf.d]# dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-327.36.3.el7.i686 i686 CentOS Linux release 7.2.1511 (AltArch) auth_mechanisms = plain login disable_plaintext_auth = no mail_location = mbox:~/mail:INBOX=/var/mail/%u 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 { driver = pam } protocols = ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 2

Re: Sendmail Dovecot Trouble
by Alexander Dalloz 14 Jul '18

14 Jul '18

Am 13.07.2018 um 17:44 schrieb Aki Tuomi: > Should your INBOX path be/var/spool/mail/%u then? /var/spool/mail is the same as /var/mail on CentOS 7 as /var/mail is a symlink. Alexander

1 0

mdbox+ ALT storage + lazyexpunge
by Matt Bryant 14 Jul '18

14 Jul '18

All, Anyone know that if you setup lazyexpounge with mdbox that as ALT storage defined, whether the mail location for namespace used by lazyexpunge also need the ALT= specified ?? rgds Matt

1 1

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 14 Jul '18

14 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 13 Jul '18

13 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

Connection refused (61)
by Teno Deuter 12 Jul '18

12 Jul '18

Dear list, in a box with the following setup: openbsd 6.3 opensmtpd dovecot 2.2.34 roundcubemail 1.3.5 httpd web server when a system user is authenticated via roundcubemail and tries to send an email, the following errors pops in the roundcube log file: Connection refused (61) Failed to connect socket: Connection refused () here is my roundcube config file: $config['default_host'] = '127.0.0.1'; $config['smtp_server'] = 'tls://127.0.0.1'; $config['smtp_server'] = 'tls://127.0.0.1'; $config['smtp_user'] = '%u'; $config['smtp_pass'] = '%p'; and the dovecot config: mail_location = maildir:~/var/mail/%u:LAYOUT=fs log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot-info.log ssl = yes ssl_cert = </etc/ssl/server.crt ssl_key = </etc/ssl/server.key the system users emails are in maildir format and follow the below structure: /var/mail/[user]/Drafts Inbox Sent Spam Trash Thank you for your help

4 47

Re: Connection refused (61)
by Richard 12 Jul '18

12 Jul '18

obvious correction ... sorry. netstat -np | grep :587 > Date: Wednesday, July 11, 2018 21:57:31 +0000 > From: Richard <inbound-dovecot(a)listmail.innovate.net> > what does the output of: > > netstat -n | grep :587 > > run as root, show you? the -p will give the program and pid. > > > >> Date: Wednesday, July 11, 2018 21:51:09 +0000 >> From: Larry Rosenman <larryrtx(a)gmail.com> >> >> Yep, you (probably) need to configure openSMTPD to listen on 587 >> >> (I run exim, so I can't help with that). > >

2 1

LMTP crashing heavily for my 2.2.36 installation
by Wolfgang Rosenauer 11 Jul '18

11 Jul '18

Hi, 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: (p art->data != NULL) 2018-07-11T07:34:56.821410+02:00 saruman dovecot: lmtp(an007498): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xa0eb0) [0x7ff54949ceb0] -> /usr/ lib64/dovecot/libdovecot.so.0(+0xa0f8e) [0x7ff54949cf8e] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff549430f46] -> /usr/lib64/dovecot/libdovecot.so .0(imap_bodystructure_write+0x3b1) [0x7ff5494753b1] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xb8ff5) [0x7ff5497e9ff5] -> /usr/lib64/dovecot/libdovecot- storage.so.0(+0xbbbdc) [0x7ff5497ecbdc] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_special+0x20d) [0x7ff5497ed05d] -> /usr/lib64/dovecot/lib dovecot-storage.so.0(mail_get_special+0xd) [0x7ff54977325d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_set_attachment_keywords+0x162) [0x7ff549773662] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xb9995) [0x7ff5497ea995] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xb9d6b) [0x7ff5497ead6b] -> /usr/lib 64/dovecot/libdovecot-storage.so.0(index_mail_get_parts+0x60) [0x7ff5497ec850] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_parts+0x23) [0x7ff549772 cb3] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x2ed1e) [0x7ff544fefd1e] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_message_body_get_text+0x33) [0x7 ff544ff1283] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(ext_body_get_part_list+0x47) [0x7ff545024ec7] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x64612) [ 0x7ff545025612] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0x6c) [0x7ff545002e4c] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(siev e_interpreter_run+0x2b) [0x7ff54500309b] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x543e2) [0x7ff5450153e2] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(si eve_multiscript_run+0x38) [0x7ff545016018] -> /usr/lib64/dovecot/modules/lib90_sieve_plugin.so(+0x36a7) [0x7ff54527e6a7] -> /usr/lib64/dovecot/libdovecot-lda. so.0(mail_deliver+0xa2) [0x7ff549a81eb2] -> dovecot/lmtp(+0x79ca) [0x5574fc4519ca] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7ff5494b1fd2 ] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7ff5494b3577] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0 x7ff5494b206c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7ff5494b2228] Any idea? thanks, Wolfgang

3 5

Dovecot API for Email Archive
by Nduduzo Phili 11 Jul '18

11 Jul '18

Good day, Is there a Dovecot API for version 2.2.15 and/or above that can be used to archive to Microsoft Archive Storage OR, Is there another tool or cloud archive platform you are aware of that could assist with this? Thank you. [cid:image001.png@01D41918.B96DB030] Nduduzo Phili Product Manager ______________________________________ D: 087 805 1146 | M: A: nduduzo.phili(a)voxtelecom.co.za www.vox.co.za

1 0

Re: Make fails with 2.3.0.1 & 2.2.34 on Mac OS X 10.7.5
by James Brown 11 Jul '18

11 Jul '18

> On 2 Mar 2018, at 6:11 pm, James Brown <jlbrown(a)bordo.com.au> wrote: > > > >> On 2 Mar 2018, at 5:59 pm, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: >> >> >> We have attempted to compile our code with OpenSSL 1.0, 1.0.2 and 1.1.0, but I'll try the specific releases too. >> >> Can you try this patch? >> >> diff --git a/src/lib-dcrypt/dcrypt-openssl.c b/src/lib-dcrypt/dcrypt-openssl.c >> index 26c9b91..187bb75 100644 >> --- a/src/lib-dcrypt/dcrypt-openssl.c >> +++ b/src/lib-dcrypt/dcrypt-openssl.c >> @@ -9,17 +9,17 @@ >> #include "array.h" >> #include "module-dir.h" >> #include "dovecot-openssl-common.h" >> -#include <openssl/evp.h> >> -#include <openssl/sha.h> >> -#include <openssl/err.h> >> -#include <openssl/rsa.h> >> -#include <openssl/ec.h> >> -#include <openssl/bio.h> >> -#include <openssl/pem.h> >> -#include <openssl/x509.h> >> -#include <openssl/engine.h> >> -#include <openssl/hmac.h> >> -#include <openssl/objects.h> >> +#include "openssl/evp.h" >> +#include "openssl/sha.h" >> +#include "openssl/err.h" >> +#include "openssl/rsa.h" >> +#include "openssl/ec.h" >> +#include "openssl/bio.h" >> +#include "openssl/pem.h" >> +#include "openssl/x509.h" >> +#include "openssl/engine.h" >> +#include "openssl/hmac.h" >> +#include "openssl/objects.h" >> #include "dcrypt.h" >> #include "dcrypt-private.h" >> >> And if it does not work, add after the includes >> >> #pragma message("OpenSSL version is " OPENSSL_VERSION_TEXT) >> #error See above >> >> And provide output? >> >> Aki Hi Aki, Change src/lib-dcrypt/dcrypt-openssl.c start to: /* Copyright (c) 2016-2017 Dovecot authors, see the included COPYING file */ #include "lib.h" #include "buffer.h" #include "str.h" #include "hex-binary.h" #include "safe-memset.h" #include "randgen.h" #include "array.h" #include "module-dir.h" #include "dovecot-openssl-common.h" #include "openssl/evp.h" #include "openssl/sha.h" #include "openssl/err.h" #include "openssl/rsa.h" #include "openssl/ec.h" #include "openssl/bio.h" #include "openssl/pem.h" #include "openssl/x509.h" #include "openssl/engine.h" #include "openssl/hmac.h" #include "openssl/objects.h" #include "dcrypt.h" #include "dcrypt-private.h" #pragma message("OpenSSL version is " OPENSSL_VERSION_TEXT) #error See above /** Ie changed the < and > to double quotes. Ran make clean, then ./configure and but it still fails. :-( dcrypt-openssl.c:25: warning: ignoring #pragma message dcrypt-openssl.c:26:2: error: #error See above dcrypt-openssl.c:118: error: field 'ctx' has incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_ctx_hmac_destroy': dcrypt-openssl.c:452: warning: implicit declaration of function 'HMAC_cleanup' dcrypt-openssl.c: In function 'dcrypt_openssl_generate_ec_key': dcrypt-openssl.c:556: error: dereferencing pointer to incomplete type dcrypt-openssl.c:557: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_ecdh_derive_secret_local': dcrypt-openssl.c:589: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_ecdh_derive_secret_peer': dcrypt-openssl.c:669: error: dereferencing pointer to incomplete type dcrypt-openssl.c:698: error: dereferencing pointer to incomplete type dcrypt-openssl.c:699: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_store_private_key_dovecot': dcrypt-openssl.c:1462: error: dereferencing pointer to incomplete type dcrypt-openssl.c:1483: error: dereferencing pointer to incomplete type dcrypt-openssl.c:1490: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_load_private_key': dcrypt-openssl.c:1616: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_store_public_key': dcrypt-openssl.c:1766: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_private_to_public_key': dcrypt-openssl.c:1802: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_name2oid': dcrypt-openssl.c:2063: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_public_key_id_old': dcrypt-openssl.c:2113: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_private_key_id_old': dcrypt-openssl.c:2136: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_public_key_id_evp': dcrypt-openssl.c:2154: error: dereferencing pointer to incomplete type make[3]: *** [libdcrypt_openssl_la-dcrypt-openssl.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Thanks for your help. James.

1 1

Remove authentication penalty for webmailer
by Andreas Meyer 11 Jul '18

11 Jul '18

Hi all, I want to remove the authentication penalty for specific ip addresses (subnets if possible). I am using Dovecot 2.3.2 (582970113) and figured that this information: https://wiki2.dovecot.org/Authentication/Penalty > If the IP is in login_trusted_networks (e.g. webmail), skip any authentication penalties is not up to date. Instead this information is: https://wiki2.dovecot.org/Upgrading/2.3 --- START --- *Localhost Auth Penalty* Dovecot no longer disables auth penalty waits for clients connecting from localhost (or login_trusted_networks in general). The previous idea was that it would likely be a webmail that would have its own delays, but there are no guarantees about this. If the old behavior is still wanted, it's possible to do nowadays even more generically with e.g.: passdb { driver = passwd-file args = username_format=%{rip} /etc/dovecot/passdb } /etc/dovecot/passdb: 127.0.0.1:::::::nodelay=yes 192.168.10.124:::::::nodelay=yes --- STOP --- Adding the passdb section and creating a passdb file with the respective ip addresses does not have any effect though. Login failures through the webmailer are still being delayed. "dovecot -n" shows that the new passdb section is loaded: --- START --- passdb { args = username_format=%{rip} /etc/dovecot/passdb driver = passwd-file } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } --- STOP --- Changing orders does not make a difference. The passdb file contains these entries: --- START --- 127.0.0.1:::::::nodelay=yes 10.25.1.20:::::::nodelay=yes --- STOP --- The logfile shows the increased delay: --- START --- Jul 10 23:37:16 9fcdf83ee81e dovecot: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<xxx(a)yyy.zzz>, method=PLAIN, rip=10.25.1.20, lip=10.25.1.10, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bit s) Jul 10 23:37:25 9fcdf83ee81e dovecot: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=<xxx(a)yyy.zzz>, method=PLAIN, rip=10.25.1.20, lip=10.25.1.10, TLS, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bit s) --- STOP --- What am I missing?

1 0

Sieve-filter and default postmaster_address -> error?
by Larry Rosenman 11 Jul '18

11 Jul '18

I wanted to re-filter my inbox after adding some filters for my DMARC reports. When I didn’t have postmaster_address in my 15-lda.conf, I got an error from sieve-filter that it was invalid (postmaster@). I added the setting (postmaster_address = ler(a)lerctr.org<mailto:ler@lerctr.org>), and the error went away. Is this expected? Dovecot 2.3.2 Pigeonhole 0.5.2 thebighonker.lerctr.org /home/ler $ pkg info | grep dovecot dovecot-2.3.2 Secure, fast and powerful IMAP and POP3 server dovecot-pigeonhole-0.5.2_2 Sieve plugin for the Dovecot 'deliver' LDA and LMTP thebighonker.lerctr.org /home/ler $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx(a)gmail.com US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106

2 2

Dovecot on CentOS 7
by John Rowan 10 Jul '18

10 Jul '18

I guess I've been lucky. My Red Hat server I built in 2003 finally gave up the ghost yesterday. Fifteen years with almost zero problems running 7x24. Now I'm trying to build a basic server to host my e-mail using CentOS 7, Sendmail and Dovecot. Server is running great as are Sendmail and Dovecot but Dovecot only allows connections from the CentOS 127.0.0.1. I can telnet localhost pop3 and get a +OK Dovecot ready response. Trying to telnet from a different computer on same LAN times out. I've looked at my old Dovecot config files to see how I enabled LAN IP access but the configs have changed a lot since I last installed Dovecot. Googling hasn't helped. Anyone help with a sample config with LAN IPs permitted?

5 4

v2.3.2.1 released
by Timo Sirainen 10 Jul '18

10 Jul '18

https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz.sig v2.3.2 still had a few unexpected bugs: - SSL/TLS servers may have crashed during client disconnection - lmtp: With lmtp_rcpt_check_quota=yes mail deliveries may have sometimes assert-crashed. - v2.3.2: "make check" may have crashed with 32bit systems

2 3

Authentication failure with OpenLDAP
by Anushka Bandara 10 Jul '18

10 Jul '18

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 1

slow mailbox refreshes
by Fabian A. Santiago 09 Jul '18

09 Jul '18

Hello, I am using dovecot 2.3.2 on my private email server in conjunction with: centos 7.5 apache 2.4.6 mariadb 10.2.16 roundcube mail 1.3.6 php 5.6.36 postfix 2.10.1 I have one mailbox with nearly 30k messages in it dispersed across several folders. it's often very slow in refreshing the message list, especially in the one largest 25k+ message folder. is this simply to be expected based on my message count or is there some kind of performance optimization and tuning i can do to improve the response times? The mail server itself is a linode hosted VPS: intel xeon e5-2680 v2 @ 2.80 GHz, 4 cores 8 GB real memory 2 GB virtual memory 200 GB local storage (ext4) KVM hypervisor Thanks everyone for any guidance you can offer. -- Fabian S. OpenPGP: 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) *** 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired, still valid)

2 1

New error message with Dovecot/Pigeonhole
by Jerry 08 Jul '18

08 Jul '18

FreeBSD 11.1 / amd64 dovecot --version 2.3.2 (582970113) Pigeonhole version 0.5.2 (7704de5e) I have run 'sieve-test" many times to check out changes in my "sieve" scripts. This morning, it suddenly started issuing this error message: sieve-test(root): Fatal: Couldn't drop privileges: User is missing UID (see mail_uid setting) I am not sure what is wrong or how to correct it, since it never happened before. -- Jerry "Ainsi sera, groigne qui groigne"

3 2

Re: Question about password field in passwd-file
by J Doe 08 Jul '18

08 Jul '18

> On Jul 7, 2018, at 2:12 AM, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > > you can add nopassword attribute to the end. See https://wiki.dovecot.org/PasswordDatabase/ExtraFields > > > --- > Aki Tuomi > Dovecot oy Hi Aki, Thank you for your reply. I have two questions regarding this: 1. Is the “nopassword” attribute the same as specifying a null password field by itself ? The documentation at [1] seems to suggest that having a null password AND specifying “nopassword” will allow someone to authenticate with _no_ password: “nopasword: if you want to allow all passwords, use an empty password and this field.” Farther down, the page seems to indicate that the “nologin” attribute is what I am looking for: “nologin: User isn’t actually allowed to log in even if the password matches . . .” Or possibly “noauthenticate”: “noauthenticate: Do not perform any authentication . . ." 2. Is “nologin” functionally equivalent to specifying no password in the password field ? I am assuming that setting a null password (even without “nologin”), prevents login with ANY or NO password as a blank field would default to a {CRYPT} scheme and a call to crypt() cannot return a null string. As background to why I want to do this, I have a server with a basic Dovecot setup that provides SMTP SASL AUTH, IMAP and LMTP for Postfix. For the passdb and userdb, I use the same passwd-style file: /etc/dovecot/dovecot.conf userdb { driver = passwd-file args = /etc/dovecot/passwd } passdb { driver = passwd-file args = /etc/dovecot/passwd } I use usernames for SMTP SASL AUTH and IMAP that differ from either: user(a)example.com or user. So for one user, for example, I have: /etc/dovecot/passwd # SMTP SASL AUTH and IMAP user accounts and passwords user_account_1:{PLAIN}password: . . . # LMTP username/e-mail address user(a)example.com:: . . . :/var/mail/vhosts/example.com/user_account_1 So in the LMTP entry I specify no password between the colons to prevent someone trying to logon via IMAP using the LMTP username/e-mail address. Is this correct and: is there a better way to do this ? Thanks, - J Sources: [1] https://wiki.dovecot.org/PasswordDatabase/ExtraFields

1 0

Get rid of the "dbox-Mails"-folder
by Hativ 07 Jul '18

07 Jul '18

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 3

build failure with glibc >= 2.26
by Eray Aslan 07 Jul '18

07 Jul '18

Sun RPC was removed from glibc-2.26 [1] resulting in /bin/sh ../../../libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -std=gnu99 -march=native -O2 -pipe -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -module -avoid-version -Wl,-O1 -Wl,--as-needed -o lib10_doveadm_quota_plugin.la -rpath /usr/lib64/dovecot/doveadm doveadm-quota.lo rquota_xdr.c:4:10: fatal error: rpc/rpc.h: No such file or directory #include <rpc/rpc.h> ^~~~~~~~~~~ compilation terminated. make[4]: *** [Makefile:826: rquota_xdr.lo] Error 1 during build. Apparently, rquota code needs some love. This is dovecot-2.3.2 but 2.2 branch should also result in the same error during make. -- Eray [1] https://fedoraproject.org/wiki/Changes/SunRPCRemoval

1 0

Question about password field in passwd-file
by J Doe 07 Jul '18

07 Jul '18

Hello, I have a question regarding the password field of the passwd-file [1]. According to the wiki, the password field assumes a {SCHEME} of CRYPT when the {SCHEME} is not prefixed to this field. So, a passwd-file like: user:password: . . . … is equivalent to: user:{CRYPT}password: . . . Does that mean an example passwd-file with NEITHER {SCHEME} or password, like: user(a)example.com:: . . . (note no scheme or password specified between colons) …means that the user(a)example.com user does not have any valid crypted password and therefore the user(a)example.com user cannot be authenticated ? For example, if I use doveadm to create a null CRYPT password: $ sudo doveadm pw -s CRYPT -p “” -u user(a)example.com … gives the result: {CRYPT}txR1JRq9140Qk … which differs from the example password field having NEITHER {SCHEME} or password, like: user(a)example.com:: . . . … so if I attempt to logon using a null password for user(a)example.com when nothing is specified in the password field for the passwd-file: /etc/dovecot/passwd user(a)example.com:: . . . $ sudo doveadm auth test user(a)example.com password: passdb: user(a)example.com auth failed … it is impossible to logon as user(a)example.com with ANY PASSWORD and/or a NULL password ? Thanks, - J Sources: [1] https://wiki2.dovecot.org/AuthDatabase/PasswdFile

2 1

Re: support for Blowfish $2y$10$
by Graham S. Jarvis 07 Jul '18

07 Jul '18

Hei Aki! # doveadm pw -t '{BLF-CRYPT}$2y$10$UEm8SR/IuX.ZONebRt40XOKTuZ9bXktYWpGDiLw2h7MTPcnvmuIRK' Enter password to verify: {BLF-CRYPT}$2y$10$UEm8SR/IuX.ZONebRt40XOKTuZ9bXktYWpGDiLw2h7MTPcnvmuIRK (verified) - Great, thanks! -Graham- PS: Sorry I just "posted" to your personal address instead of the list. Aki Tuomi wrote on 06/07/18 23:06: > Hi! > > $2y$ is supported in 2.3, and supported in 2.2 if your bcrypt provider > supports it. > > You can use doveadm pw -t '{BLF-CRYPT}$2y$...' to verify this. > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: "Graham S. Jarvis" <gsjarvis(a)pt.lu> > Date: 07/07/2018 00:03 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: support for Blowfish $2y$10$ > > Hello, > > does dovecot support bcrypt $2y$ version? (BLF-CRYPT - Blowfish crypt) > > > doveadm pw -s BLF-CRYPT > generates a > {BLF-CRYPT}$2a$05$....... > password. > > Does this mean that dovecote will not authenticate against a > $2y$10$....... > password? > > Thanks in advance, > > -Graham-

1 0

support for Blowfish $2y$10$
by Graham S. Jarvis 07 Jul '18

07 Jul '18

Hello, does dovecot support bcrypt $2y$ version? (BLF-CRYPT - Blowfish crypt) doveadm pw -s BLF-CRYPT generates a {BLF-CRYPT}$2a$05$....... password. Does this mean that dovecote will not authenticate against a $2y$10$....... password? Thanks in advance, -Graham-

2 1

Replication fails over SSL
by Vladimir Tiukhtin 06 Jul '18

06 Jul '18

Hi Replication works fine on poor TCP, when I enable SSL it fails Jul 06 17:28:48 mail dovecot[13114]: doveconf: Fatal: execvp(/usr/libexec/dovecot/managesieve) failed: Argument list too long Jul 06 17:28:48 mail dovecot[13114]: config: Error: managesieve-login: dump-capability process returned 89 Jul 06 17:28:48 mail dovecot[13114]: doveadm: Error: Corrupted SSL parameters file in state_dir: ssl-parameters.dat - disabling SSL 360 Jul 06 17:28:48 mail dovecot[13114]: doveadm: Error: Couldn't initialize SSL parameters, disabling SSL I have set: service doveadm { inet_listener { address = {{ dovecot_doveadm_listen_address }} port = {{ dovecot_doveadm_listen_port }} ssl = yes } } ssl_client_ca_file = </etc/ssl/certs/ca-bundle.crt plugin { mail_replica = tcps:{{ dovecot_replica }}:{{ dovecot_doveadm_listen_port }} } I am running native dovecot 2.2.10 on Centos 7. File ssl-parameters.dat exists. I have already removed it and regenerated - does not help Thanks for any advice. Vladimir

1 0

Re: user/password Authentication via Joomla database
by Harald Leithner 06 Jul '18

06 Jul '18

Hi, I think there is no reason to be offlist. Your setup should work, only problem could be the freebsd userid. My setup has only one user for all accounts and no "real" users. I only have a vmail user. Maybe a tutorial for dovecot and mysql only would help you ( I don't have a link here, but google has) hope that helps Harald Am 06.07.2018 um 15:18 schrieb Graham S. Jarvis: > MANY thanks Harald, > > it was the SQL that is my problem ;) > > I don't know whether the detail below belongs in the mailing list - so I > thought I'd pm you with this first. > > Two questions: > A) If I read the dovecot documentation right - it is going to need to > say where the mail is - home directory (and Maildir or mbox ?). > > My setup is fairly small/restricted - I want to give the committee > members of a non-profit a way of changing the IMAP/SMTP passwords for > their Thunderbird/Apple Mail clients by using their Joomla login password. > I'm going to use FreeBSD's adduser command to add any new committee > members and this creates a standard directory structure under > /usr/home/<USERNAME> and I'll (manually) make sure that <USERNAME> is > the same as the Joomla User name that they created. The Virtual Users > Map and Aliases files to point the the actual home (Maildir) directories. > Once it's done it won't change very often. > I'm assuming that Dovecot will first do the SQL lookup and only try > /etc/passwd if it fails - so I can adduser with a locked password, so > that the alias map works and Postfix finds the Maildir. > > B) I didn't yet get my mind around Joomla groups and for example how to > give all committee members a way to change the password for their mail > accounts but only some of the members access to the front-end Mailing > list management (ACYMailer). > I think just creating a new group "committee_mail" is good enough and > this will be the <ID OF THE JOOMLA GROUP> in your SQL. > Otherwise I might want to have the SQL check the existence of various > Joomla groups. > > > What do you think? > > -Graham- > > > >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 5 Jul 2018 17:37:44 +0200 >> From: Harald Leithner <leithner(a)itronic.at> >> To: dovecot(a)dovecot.org >> Subject: Re: user/password Authentication via Joomla database >> Message-ID: <180fd3b8-3369-9102-0216-94e41033f379(a)itronic.at> >> Content-Type: text/plain; charset="windows-1252" >> >> Hi, >> >> this shouldn't be to hard. >> >> Your dovecot-sql.conf.ext could look something like this: >> >> --- >> driver = mysql >> connect = host=<host> dbname=<dbname> user=<username> password=<password> >> >> default_pass_scheme = BLF-CRYPT >> password_query = \ >> SELECT \ >> u.username, \ >> u.password, \ >> FROM <JOOMLA_PREFIX>_users u \ >> LEFT JOIN <JOOMLA_PREFIX>_user_usergroup_map g ON u.id = >> g.user_id \ >> WHERE \ >> u.username = '%u' AND u.block = 0 AND g.group_id = <ID OF THE >> JOOMLA GROUP> >> >> user_query = \ >> SELECT \ >> u.username, \ >> u.password, \ >> FROM <JOOMLA_PREFIX>_users u \ >> LEFT JOIN <JOOMLA_PREFIX>_user_usergroup_map g ON u.id = >> g.user_id \ >> WHERE \ >> u.username = '%u' AND u.block = 0 AND g.group_id = <ID OF THE >> JOOMLA GROUP> >> >> iterate_query = SELECT username AS user FROM <JOOMLA_PREFIX>_users u \ >> LEFT JOIN <JOOMLA_PREFIX>_user_usergroup_map g ON u.id = >> g.user_id \ >> WHERE \ >> u.block = 0 AND g.group_id = <ID OF THE JOOMLA GROUP> >> >> --- >> >> But I'm not sure if dovecot supports Blowfish $2y$ Version used by >> Joomla as default. >> >> Also I didn't tested this configuration, so there maybe someflaws in it. >> >> bye >> Harald >> >> >> Am 05.07.2018 um 16:05 schrieb Graham S. Jarvis: >>> Hello, >>> >>> did anyone ever set up Authentication via lookups to a Joomla (mysql) >>> database? >>> >>> What I'd like to do is lookup Joomla users (who are in specific/multiple >>> groups) in the Joomla database and then fallback to /etc/passwd >>> authentication to let system users authenticate. >>> >>> I'm running : >>> # 2.2.35 (b1cb664): /usr/local/etc/dovecot/dovecot.conf >>> # OS: FreeBSD 11.1-RELEASE-p10 amd64 >>> >>> Thanks in advance, >>> >>> -Graham- >> -- Harald Leithner ITronic Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria Tel: +43-1-545 0 604 Mobil: +43-699-123 78 4 78 Mail: leithner(a)itronic.at | itronic.at

1 0

Benchmarks with imaptest
by João Paulo Sacchetto Ribeiro Bastos 06 Jul '18

06 Jul '18

Hey guys, Has anybody ever used imaptest to benchmark *ONLY* reads? I'm trying to run a battery of tests in my new cluster and apparently no combination of parameters works, because fetch instruction doesn't run. Below is the command I'm using and its partial output imaptest/src/imaptest host=$SERVER_IP port=143 user=teste%d(a)example%d.com pass=$TEST_PASS users=10 domains=10 clients=100 - append=0 select=100 fetch=100 Logi Sele Fetc Logo 100% 100% 100% 100% 166 156 0 156 99/100 223 230 0 230 100/100 206 203 0 203 97/100 Can anybody help me understand why fetch doesn't work and how to fix this? Regards, -- João Paulo Bastos DevOps Engineer at Mav Tecnologia Belo Horizonte - Brazil +55 31 99279-7092

2 2

2.3.2 is still crashing (lmtp)
by Martynas Bendorius 06 Jul '18

06 Jul '18

Dovecot 2.3.2 still has the same issue we reported for 2.3.X: Jul 05 15:10:49 lmtp(2730445): Panic: file lib-event.c: line 182 (event_pop_global): assertion failed: (event != NULL) Jul 05 15:10:49 lmtp(2730445): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xce054) [0x7f7f7c92f054] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f7f7c92f09a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7f7c89e444] -> /usr/lib/dovecot/libdovecot.so.0(+0xe9e42) [0x7f7f7c94ae42] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x4ff88) [0x7f7f7cc2cf88] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_context_deactivate+0x5d) [0x7f7f7c94670d] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x85) [0x7f7f7c946b05] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7f7f7c9483df] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7f7f7c946be2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f7f7c946e08] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f7f7c8c2783] -> dovecot/lmtp [local READY](main+0x229) [0x7f7f7d3634b9] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f7f7c4b63d5] -> dovecot/lmtp [local READY](+0x55e5) [0x7f7f7d3635e5] gdb: Core was generated by `dovecot/lmtp [lo'. Program terminated with signal 6, Aborted. #0 0x00007f6502506207 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); (gdb) bt full #0 0x00007f6502506207 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 resultvar = 0 pid = 2826461 selftid = 2826461 #1 0x00007f65025078f8 in __GI_abort () at abort.c:90 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0x1, sa_sigaction = 0x1}, sa_mask = {__val = { 520, 173, 140071844479056, 513, 140071811839987, 257, 140071844479056, 513, 7749847442339820800, 140071844479056, 140071812055443, 140071844479056, 140727678224992, 140071844567296, 140071812055801, 140071844479056}}, sa_flags = 43400170, sa_restorer = 0x7ffdb7454a01} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x00007f650296b01b in default_fatal_finish (type=<optimized out>, status=status@entry=0) at failures.c:247 backtrace = 0x7f6504888088 "/usr/lib/dovecot/libdovecot.so.0(+0xce054) [0x7f650296b054] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f650296b09a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f65028da"... recursed = 0 #3 0x00007f650296b09a in default_fatal_handler (ctx=0x7ffdb7454ad0, format=<optimized out>, args=<optimized out>) at failures.c:261 status = 0 #4 0x00007f65028da444 in i_panic ( format=format@entry=0x7f65029a6fa8 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:325 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0, timestamp_usecs = 0, log_prefix = 0x0} args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7ffdb7454bc0, reg_save_area = 0x7ffdb7454b00}} #5 0x00007f6502986e42 in event_pop_global (event=<optimized out>) at lib-event.c:182 __func__ = "event_pop_global" #6 0x00007f6502c68f88 in mail_storage_service_io_deactivate_user_cb (user=0x7f65048e4708) at mail-storage-service.c:823 ---Type <return> to continue, or q <return> to quit--- event = 0x0 __func__ = "mail_storage_service_io_deactivate_user_cb" #7 0x00007f650298270d in io_loop_context_deactivate (ctx=0x7f65048df850) at ioloop.c:1054 cb_end = 0x7f65048e78f0 cb = 0x7f65048e78d0 __func__ = "io_loop_context_deactivate" #8 0x00007f6502982b05 in io_loop_call_io (io=0x7f650489d8c0) at ioloop.c:680 ioloop = 0x7f6504890c60 t_id = 0 __func__ = "io_loop_call_io" #9 0x00007f65029843df in io_loop_handler_run_internal (ioloop=ioloop@entry=0x7f6504890c60) at ioloop-epoll.c:222 ctx = 0x7f650489c200 list = 0x7f650489d920 io = <optimized out> tv = {tv_sec = 2147483, tv_usec = 0} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 call = <optimized out> __func__ = "io_loop_handler_run_internal" #10 0x00007f6502982be2 in io_loop_handler_run (ioloop=ioloop@entry=0x7f6504890c60) at ioloop.c:726 __func__ = "io_loop_handler_run" #11 0x00007f6502982e08 in io_loop_run (ioloop=0x7f6504890c60) at ioloop.c:699 __func__ = "io_loop_run" #12 0x00007f65028fe783 in master_service_run (service=0x7f6504890af0, callback=callback@entry=0x7f650339f6e0 <client_connected>) at master-service.c:767 No locals. #13 0x00007f650339f4b9 in main (argc=2, argv=0x7f6504890890) at main.c:158 set_roots = {0x7f6502c0dea0 <smtp_submit_setting_parser_info>, 0x7f6503173ba0 <lda_setting_parser_info>, 0x7f65035a5500 <lmtp_setting_parser_info>, 0x0} ---Type <return> to continue, or q <return> to quit--- service_flags = <optimized out> storage_service_flags = <optimized out> tmp_base_dir = 0x7f6504888040 "\003" c = <optimized out> error = 0x0 -- Best regards, Martynas Bendorius

2 2

2.3.2 director imap-login segfaults
by Tom Sommer 06 Jul '18

06 Jul '18

My director has started segfaulting since upgradeing to 2.3.2: # gdb /usr/libexec/dovecot/imap-login ./core.9757 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/libexec/dovecot/imap-login...(no debugging symbols found)...done. [New Thread 9757] Reading symbols from /usr/lib64/dovecot/libdovecot-login.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/dovecot/libdovecot-login.so.0 Reading symbols from /usr/lib64/dovecot/libdovecot.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /usr/lib64/dovecot/libssl_iostream_openssl.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/dovecot/libssl_iostream_openssl.so Core was generated by `dovecot/imap-login [26 pre-l'. Program terminated with signal 11, Segmentation fault. #0 0x00007fa19b3ec6ed in i_stream_get_root_io () from /usr/lib64/dovecot/libdovecot.so.0 Missing separate debuginfos, use: debuginfo-install dovecot-2.3.2-3.x86_64 (gdb) bt full #0 0x00007fa19b3ec6ed in i_stream_get_root_io () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #1 0x00007fa19b3ec9b5 in i_stream_set_input_pending () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #2 0x00007fa198d48b35 in openssl_iostream_bio_sync () from /usr/lib64/dovecot/libssl_iostream_openssl.so No symbol table info available. #3 0x00007fa198d4920a in openssl_iostream_more () from /usr/lib64/dovecot/libssl_iostream_openssl.so No symbol table info available. #4 0x00007fa198d49247 in ?? () from /usr/lib64/dovecot/libssl_iostream_openssl.so No symbol table info available. #5 0x00007fa19b694862 in client_unref () from /usr/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #6 0x00007fa19b698adc in ?? () from /usr/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #7 0x00007fa19b699aca in ?? () from /usr/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #8 0x00007fa19b3f76d5 in io_loop_call_io () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #9 0x00007fa19b3f96af in io_loop_handler_run_internal () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #10 0x00007fa19b3f77c5 in io_loop_handler_run () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #11 0x00007fa19b3f79e8 in io_loop_run () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #12 0x00007fa19b374963 in master_service_run () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #13 0x00007fa19b69b1b3 in login_binary_run () from /usr/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #14 0x00007fa19af9ed1d in __libc_start_main () from /lib64/libc.so.6 No symbol table info available. #15 0x00007fa19bac8599 in _start () No symbol table info available. -- Tom

2 2

user/password Authentication via Joomla database
by Graham S. Jarvis 05 Jul '18

05 Jul '18

Hello, did anyone ever set up Authentication via lookups to a Joomla (mysql) database? What I'd like to do is lookup Joomla users (who are in specific/multiple groups) in the Joomla database and then fallback to /etc/passwd authentication to let system users authenticate. I'm running : # 2.2.35 (b1cb664): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 11.1-RELEASE-p10 amd64 Thanks in advance, -Graham-

2 1

Re: 2.3.2 director imap-login segfaults
by Aki Tuomi 05 Jul '18

05 Jul '18

Thanks. We'll take a look at this. ---Aki TuomiDovecot oy -------- Original message --------From: Tom Sommer <mail(a)tomsommer.dk> Date: 05/07/2018 16:01 (GMT+01:00) To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Cc: Dovecot <dovecot(a)dovecot.org> Subject: Re: 2.3.2 director imap-login segfaults # gdb /usr/libexec/dovecot/imap-login ./core.34022 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/libexec/dovecot/imap-login...Reading symbols from /usr/lib/debug/usr/libexec/dovecot/imap-login.debug...done. done. [New Thread 34022] Reading symbols from /usr/lib64/dovecot/libdovecot-login.so.0...Reading symbols from /usr/lib/debug/usr/lib64/dovecot/libdovecot-login.so.0.0.0.debug...done. done. Loaded symbols for /usr/lib64/dovecot/libdovecot-login.so.0 Reading symbols from /usr/lib64/dovecot/libdovecot.so.0...Reading symbols from /usr/lib/debug/usr/lib64/dovecot/libdovecot.so.0.0.0.debug...done. done. Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /usr/lib64/dovecot/libssl_iostream_openssl.so...Reading symbols from /usr/lib/debug/usr/lib64/dovecot/libssl_iostream_openssl.so.debug...done. done. Loaded symbols for /usr/lib64/dovecot/libssl_iostream_openssl.so Core was generated by `dovecot/imap-login [4 pre-lo'. Program terminated with signal 11, Segmentation fault. #0 i_stream_get_root_io (stream=0x0) at istream.c:919 919 while (stream->real_stream->parent != NULL) { Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.209.el6_9.2.x86_64 keyutils-libs-1.4-5.el6.x86_64 krb5-libs-1.10.3-65.el6.x86_64 libcom_err-1.41.12-23.el6.x86_64 libselinux-2.0.94-7.el6.x86_64 openssl-1.0.1e-57.el6.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt full #0 i_stream_get_root_io (stream=0x0) at istream.c:919 __func__ = "i_stream_get_root_io" #1 0x00007f697d6249b5 in i_stream_set_input_pending (stream=<value optimized out>, pending=<value optimized out>) at istream.c:931 No locals. #2 0x00007f697af80b35 in openssl_iostream_bio_input (ssl_io=0x7f6980852320, type=OPENSSL_IOSTREAM_SYNC_TYPE_WRITE) at iostream-openssl.c:500 data = 0x7f697d6784e0 "" bytes = 17371 ret = <value optimized out> bytes_read = true size = 0 #3 openssl_iostream_bio_sync (ssl_io=0x7f6980852320, type=OPENSSL_IOSTREAM_SYNC_TYPE_WRITE) at iostream-openssl.c:512 ret = true #4 0x00007f697af8120a in openssl_iostream_more (ssl_io=0x7f6980852320, type=<value optimized out>) at iostream-openssl.c:526 ret = <value optimized out> #5 0x00007f697af81247 in openssl_iostream_destroy (ssl_io=0x7f6980852320) at iostream-openssl.c:354 No locals. #6 0x00007f697d8cc862 in client_unref (_client=<value optimized out>) at client-common.c:365 client = 0x7f6982b5a840 __func__ = "client_unref" #7 0x00007f697d8d0adc in login_proxy_free_full (_proxy=<value optimized out>, reason=0x7f697f6ae0a0 "Disconnected by server(0s idle, in=307, out=1038)", delayed=<value optimized out>) at login-proxy.c:529 proxy = 0x7f6983ff8990 client = 0x0 ipstr = <value optimized out> delay_ms = <value optimized out> __func__ = "login_proxy_free_full" #8 0x00007f697d8d1aca in login_proxy_free_delayed (side=<value optimized out>, status=<value optimized out>, proxy=0x0) at login-proxy.c:541 No locals. #9 login_proxy_free_errstr (side=<value optimized out>, status=<value optimized out>, proxy=0x0) at login-proxy.c:129 proxy = 0x7f6983ff8990 reason = 0x7f697f6ae068 #10 login_proxy_finished (side=<value optimized out>, status=<value optimized out>, proxy=0x0) at login-proxy.c:619 errstr = <value optimized out> server_side = true #11 0x00007f697d62f6d5 in io_loop_call_io (io=0x7f6981019440) at ioloop.c:674 ioloop = 0x7f697f6b6d00 t_id = 2 __func__ = "io_loop_call_io" #12 0x00007f697d6316af in io_loop_handler_run_internal (ioloop=<value optimized out>) at ioloop-epoll.c:222 ctx = 0x7f697f6e5de0 events = <value optimized out> event = 0x7f6982f5f4e0 list = 0x7f6980b980e0 io = <value optimized out> tv = {tv_sec = 0, tv_usec = 369635} events_count = <value optimized out> msecs = <value optimized out> ret = 1 i = <value optimized out> call = <value optimized out> __func__ = "io_loop_handler_run_internal" #13 0x00007f697d62f7c5 in io_loop_handler_run (ioloop=0x7f697f6b6d00) at ioloop.c:726 __func__ = "io_loop_handler_run" #14 0x00007f697d62f9e8 in io_loop_run (ioloop=0x7f697f6b6d00) at ioloop.c:699 __func__ = "io_loop_run" #15 0x00007f697d5ac963 in master_service_run (service=0x7f697f6b6b90, callback=<value optimized out>) at master-service.c:767 No locals. #16 0x00007f697d8d31b3 in login_binary_run (binary=<value optimized out>, argc=2, argv=0x7f697f6b68a0) at main.c:549 set_pool = 0x7f697f6b7e80 login_socket = <value optimized out> c = <value optimized out> #17 0x00007f697d1d6d1d in __libc_start_main () from /lib64/libc.so.6 No symbol table info available. #18 0x00007f697dd00599 in _start () No symbol table info available. --- Tom On 2018-07-05 15:43, Aki Tuomi wrote: Can you install debuginfo and try again? --- Aki Tuomi Dovecot oy -------- Original message -------- From: Tom Sommer <mail(a)tomsommer.dk> Date: 05/07/2018 14:12 (GMT+01:00) To: Dovecot <dovecot(a)dovecot.org> Subject: 2.3.2 director imap-login segfaults My director has started segfaulting since upgradeing to 2.3.2: # gdb /usr/libexec/dovecot/imap-login ./core.9757 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/libexec/dovecot/imap-login...(no debugging symbols found)...done. [New Thread 9757] Reading symbols from /usr/lib64/dovecot/libdovecot-login.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/dovecot/libdovecot-login.so.0 Reading symbols from /usr/lib64/dovecot/libdovecot.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /usr/lib64/dovecot/libssl_iostream_openssl.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/dovecot/libssl_iostream_openssl.so Core was generated by `dovecot/imap-login [26 pre-l'. Program terminated with signal 11, Segmentation fault. #0 0x00007fa19b3ec6ed in i_stream_get_root_io () from /usr/lib64/dovecot/libdovecot.so.0 Missing separate debuginfos, use: debuginfo-install dovecot-2.3.2-3.x86_64 (gdb) bt full #0 0x00007fa19b3ec6ed in i_stream_get_root_io () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #1 0x00007fa19b3ec9b5 in i_stream_set_input_pending () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #2 0x00007fa198d48b35 in openssl_iostream_bio_sync () from /usr/lib64/dovecot/libssl_iostream_openssl.so No symbol table info available. #3 0x00007fa198d4920a in openssl_iostream_more () from /usr/lib64/dovecot/libssl_iostream_openssl.so No symbol table info available. #4 0x00007fa198d49247 in ?? () from /usr/lib64/dovecot/libssl_iostream_openssl.so No symbol table info available. #5 0x00007fa19b694862 in client_unref () from /usr/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #6 0x00007fa19b698adc in ?? () from /usr/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #7 0x00007fa19b699aca in ?? () from /usr/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #8 0x00007fa19b3f76d5 in io_loop_call_io () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #9 0x00007fa19b3f96af in io_loop_handler_run_internal () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #10 0x00007fa19b3f77c5 in io_loop_handler_run () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #11 0x00007fa19b3f79e8 in io_loop_run () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #12 0x00007fa19b374963 in master_service_run () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #13 0x00007fa19b69b1b3 in login_binary_run () from /usr/lib64/dovecot/libdovecot-login.so.0 No symbol table info available. #14 0x00007fa19af9ed1d in __libc_start_main () from /lib64/libc.so.6 No symbol table info available. #15 0x00007fa19bac8599 in _start () No symbol table info available. -- Tom

1 0

Re: 2.3.2 director imap-login segfaults
by Tom Sommer 05 Jul '18

05 Jul '18

# gdb /usr/libexec/dovecot/imap-login ./core.34022 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/libexec/dovecot/imap-login...Reading symbols from /usr/lib/debug/usr/libexec/dovecot/imap-login.debug...done. done. [New Thread 34022] Reading symbols from /usr/lib64/dovecot/libdovecot-login.so.0...Reading symbols from /usr/lib/debug/usr/lib64/dovecot/libdovecot-login.so.0.0.0.debug...done. done. Loaded symbols for /usr/lib64/dovecot/libdovecot-login.so.0 Reading symbols from /usr/lib64/dovecot/libdovecot.so.0...Reading symbols from /usr/lib/debug/usr/lib64/dovecot/libdovecot.so.0.0.0.debug...done. done. Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /usr/lib64/dovecot/libssl_iostream_openssl.so...Reading symbols from /usr/lib/debug/usr/lib64/dovecot/libssl_iostream_openssl.so.debug...done. done. Loaded symbols for /usr/lib64/dovecot/libssl_iostream_openssl.so Core was generated by `dovecot/imap-login [4 pre-lo'. Program terminated with signal 11, Segmentation fault. #0 i_stream_get_root_io (stream=0x0) at istream.c:919 919 while (stream->real_stream->parent != NULL) { Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.209.el6_9.2.x86_64 keyutils-libs-1.4-5.el6.x86_64 krb5-libs-1.10.3-65.el6.x86_64 libcom_err-1.41.12-23.el6.x86_64 libselinux-2.0.94-7.el6.x86_64 openssl-1.0.1e-57.el6.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt full #0 i_stream_get_root_io (stream=0x0) at istream.c:919 __func__ = "i_stream_get_root_io" #1 0x00007f697d6249b5 in i_stream_set_input_pending (stream=<value optimized out>, pending=<value optimized out>) at istream.c:931 No locals. #2 0x00007f697af80b35 in openssl_iostream_bio_input (ssl_io=0x7f6980852320, type=OPENSSL_IOSTREAM_SYNC_TYPE_WRITE) at iostream-openssl.c:500 data = 0x7f697d6784e0 "" bytes = 17371 ret = <value optimized out> bytes_read = true size = 0 #3 openssl_iostream_bio_sync (ssl_io=0x7f6980852320, type=OPENSSL_IOSTREAM_SYNC_TYPE_WRITE) at iostream-openssl.c:512 ret = true #4 0x00007f697af8120a in openssl_iostream_more (ssl_io=0x7f6980852320, type=<value optimized out>) at iostream-openssl.c:526 ret = <value optimized out> #5 0x00007f697af81247 in openssl_iostream_destroy (ssl_io=0x7f6980852320) at iostream-openssl.c:354 No locals. #6 0x00007f697d8cc862 in client_unref (_client=<value optimized out>) at client-common.c:365 client = 0x7f6982b5a840 __func__ = "client_unref" #7 0x00007f697d8d0adc in login_proxy_free_full (_proxy=<value optimized out>, reason=0x7f697f6ae0a0 "Disconnected by server(0s idle, in=307, out=1038)", delayed=<value optimized out>) at login-proxy.c:529 proxy = 0x7f6983ff8990 client = 0x0 ipstr = <value optimized out> delay_ms = <value optimized out> __func__ = "login_proxy_free_full" #8 0x00007f697d8d1aca in login_proxy_free_delayed (side=<value optimized out>, status=<value optimized out>, proxy=0x0) at login-proxy.c:541 No locals. #9 login_proxy_free_errstr (side=<value optimized out>, status=<value optimized out>, proxy=0x0) at login-proxy.c:129 proxy = 0x7f6983ff8990 reason = 0x7f697f6ae068 #10 login_proxy_finished (side=<value optimized out>, status=<value optimized out>, proxy=0x0) at login-proxy.c:619 errstr = <value optimized out> server_side = true #11 0x00007f697d62f6d5 in io_loop_call_io (io=0x7f6981019440) at ioloop.c:674 ioloop = 0x7f697f6b6d00 t_id = 2 __func__ = "io_loop_call_io" #12 0x00007f697d6316af in io_loop_handler_run_internal (ioloop=<value optimized out>) at ioloop-epoll.c:222 ctx = 0x7f697f6e5de0 events = <value optimized out> event = 0x7f6982f5f4e0 list = 0x7f6980b980e0 io = <value optimized out> tv = {tv_sec = 0, tv_usec = 369635} events_count = <value optimized out> msecs = <value optimized out> ret = 1 i = <value optimized out> call = <value optimized out> __func__ = "io_loop_handler_run_internal" #13 0x00007f697d62f7c5 in io_loop_handler_run (ioloop=0x7f697f6b6d00) at ioloop.c:726 __func__ = "io_loop_handler_run" #14 0x00007f697d62f9e8 in io_loop_run (ioloop=0x7f697f6b6d00) at ioloop.c:699 __func__ = "io_loop_run" #15 0x00007f697d5ac963 in master_service_run (service=0x7f697f6b6b90, callback=<value optimized out>) at master-service.c:767 No locals. #16 0x00007f697d8d31b3 in login_binary_run (binary=<value optimized out>, argc=2, argv=0x7f697f6b68a0) at main.c:549 set_pool = 0x7f697f6b7e80 login_socket = <value optimized out> c = <value optimized out> #17 0x00007f697d1d6d1d in __libc_start_main () from /lib64/libc.so.6 No symbol table info available. #18 0x00007f697dd00599 in _start () No symbol table info available. --- Tom On 2018-07-05 15:43, Aki Tuomi wrote: > Can you install debuginfo and try again? > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Tom Sommer <mail(a)tomsommer.dk> > Date: 05/07/2018 14:12 (GMT+01:00) > To: Dovecot <dovecot(a)dovecot.org> > Subject: 2.3.2 director imap-login segfaults > My director has started segfaulting since upgradeing to 2.3.2: > > # gdb /usr/libexec/dovecot/imap-login ./core.9757 > GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) > Copyright (C) 2010 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show > copying" > and "show warranty" for details. > This GDB was configured as "x86_64-redhat-linux-gnu". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from /usr/libexec/dovecot/imap-login...(no debugging > symbols found)...done. > [New Thread 9757] > Reading symbols from /usr/lib64/dovecot/libdovecot-login.so.0...(no > debugging symbols found)...done. > Loaded symbols for /usr/lib64/dovecot/libdovecot-login.so.0 > Reading symbols from /usr/lib64/dovecot/libdovecot.so.0...(no debugging > symbols found)...done. > Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0 > Reading symbols from /lib64/libc.so.6...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libc.so.6 > Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols > found)...done. > Loaded symbols for /usr/lib64/libssl.so.10 > Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols > found)...done. > Loaded symbols for /usr/lib64/libcrypto.so.10 > Reading symbols from /lib64/librt.so.1...(no debugging symbols > found)...done. > Loaded symbols for /lib64/librt.so.1 > Reading symbols from /lib64/libdl.so.2...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libdl.so.2 > Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols > found)...done. > Loaded symbols for /lib64/ld-linux-x86-64.so.2 > Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libgssapi_krb5.so.2 > Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libkrb5.so.3 > Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libcom_err.so.2 > Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libk5crypto.so.3 > Reading symbols from /lib64/libz.so.1...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libz.so.1 > Reading symbols from /lib64/libpthread.so.0...(no debugging symbols > found)...done. > [Thread debugging using libthread_db enabled] > Loaded symbols for /lib64/libpthread.so.0 > Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libkrb5support.so.0 > Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libkeyutils.so.1 > Reading symbols from /lib64/libresolv.so.2...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libresolv.so.2 > Reading symbols from /lib64/libselinux.so.1...(no debugging symbols > found)...done. > Loaded symbols for /lib64/libselinux.so.1 > Reading symbols from /usr/lib64/dovecot/libssl_iostream_openssl.so...(no > debugging symbols found)...done. > Loaded symbols for /usr/lib64/dovecot/libssl_iostream_openssl.so > Core was generated by `dovecot/imap-login [26 pre-l'. > Program terminated with signal 11, Segmentation fault. > #0 0x00007fa19b3ec6ed in i_stream_get_root_io () from > /usr/lib64/dovecot/libdovecot.so.0 > Missing separate debuginfos, use: debuginfo-install > dovecot-2.3.2-3.x86_64 > (gdb) bt full > #0 0x00007fa19b3ec6ed in i_stream_get_root_io () from > /usr/lib64/dovecot/libdovecot.so.0 > No symbol table info available. > #1 0x00007fa19b3ec9b5 in i_stream_set_input_pending () from > /usr/lib64/dovecot/libdovecot.so.0 > No symbol table info available. > #2 0x00007fa198d48b35 in openssl_iostream_bio_sync () from > /usr/lib64/dovecot/libssl_iostream_openssl.so > No symbol table info available. > #3 0x00007fa198d4920a in openssl_iostream_more () from > /usr/lib64/dovecot/libssl_iostream_openssl.so > No symbol table info available. > #4 0x00007fa198d49247 in ?? () from > /usr/lib64/dovecot/libssl_iostream_openssl.so > No symbol table info available. > #5 0x00007fa19b694862 in client_unref () from > /usr/lib64/dovecot/libdovecot-login.so.0 > No symbol table info available. > #6 0x00007fa19b698adc in ?? () from > /usr/lib64/dovecot/libdovecot-login.so.0 > No symbol table info available. > #7 0x00007fa19b699aca in ?? () from > /usr/lib64/dovecot/libdovecot-login.so.0 > No symbol table info available. > #8 0x00007fa19b3f76d5 in io_loop_call_io () from > /usr/lib64/dovecot/libdovecot.so.0 > No symbol table info available. > #9 0x00007fa19b3f96af in io_loop_handler_run_internal () from > /usr/lib64/dovecot/libdovecot.so.0 > No symbol table info available. > #10 0x00007fa19b3f77c5 in io_loop_handler_run () from > /usr/lib64/dovecot/libdovecot.so.0 > No symbol table info available. > #11 0x00007fa19b3f79e8 in io_loop_run () from > /usr/lib64/dovecot/libdovecot.so.0 > No symbol table info available. > #12 0x00007fa19b374963 in master_service_run () from > /usr/lib64/dovecot/libdovecot.so.0 > No symbol table info available. > #13 0x00007fa19b69b1b3 in login_binary_run () from > /usr/lib64/dovecot/libdovecot-login.so.0 > No symbol table info available. > #14 0x00007fa19af9ed1d in __libc_start_main () from /lib64/libc.so.6 > No symbol table info available. > #15 0x00007fa19bac8599 in _start () > No symbol table info available. > > -- > Tom

1 0