- dovecot - dovecot.org

Field Return-Path contains twice the domain
by Quaquaraquà 22 Aug '16

22 Aug '16

Dear exim & dovecot users, posting on both mailing lists as I am not sure who has the ultimate responsability for this field. I am trying to set up a mail server for multiple domains in my VPS. So I managed to set up the authentication through a dovecot authenticator, which relies to a sqlite database. I would like that, from the database perspective, a query has, as input parameters, both the username and the domain to check the password. For this purpose, I am requesting that the SMTP account is in the full form username(a)domain.com. When forwarded to the dovecot authenticator, I can extract the user with %n and %d. This works, but it has a utter drawback: emails are sent repeating twice the domain in the Return-Path field, e.g. : Return-Path: <"user(a)domain.net"@domain.net> Subject: Re: Hello To: nuquaquaraqua(a)gmail.com From: user <user(a)domain.net> How do I properly fix the field Return-Path now? dovecot --version: 2.2.25 (7be1766) Exim version 4.87 #1 built 28-Jul-2016 18:38:04 Kind regards, Quaquaraqua

1 0

Port 143 is no SSL; no client auth; plain password auth. But port 993 is SSL; client cert auth.
by UK Universal Support Limited 21 Aug '16

21 Aug '16

I am experiencing the error "Error: BUG: Authentication client sent unknown handshake command:" My goal is Port 143: no SSL; no client auth; plain password auth. Port 993: SSL; client cert auth. I found the archive http://www.dovecot.org/list/dovecot/2016-February/103067.html and followed it, but does not work, I see the following log in /var/log/maillog Aug 21 15:36:42 vps0 dovecot: master: Dovecot v2.2.25 (7be1766) starting up for imap (core dumps disabled) Aug 21 15:37:51 vps0 dovecot: auth: Error: BUG: Authentication client sent unknown handshake command: REQUEST?1997012993?3734?1?e067999d43eebcecf0c9d44a1c108d75?session_pid=3741?r... Aug 21 15:37:51 vps0 dovecot: imap: Error: Authentication server didn't send valid SPID as expected: MECH#011PLAIN#011plaintext Aug 21 15:37:51 vps0 dovecot: imap: Error: Disconnected from auth server, aborting (client-pid=3734 client-id=1) Aug 21 15:37:51 vps0 dovecot: imap-login: Internal login failure (pid=3734 id=1) (internal failure, 1 successful auths): user=<contact>, method=PLAIN, rip=212.104.147.161, lip=46.30.14.36, mpid=3741, TLS, session=<UkXhtpY6W8XUaJOh> Aug 21 15:37:51 vps0 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=212.104.147.161, lip=46.30.14.36, TLS handshaking: SSL_accept() failed: error:140D9115:SSL routines:SSL_GET_PREV_SESSION:session id context uninitialized, session=<nkrktpY6XMXUaJOh> Can anyone advice any solution? Dovecot version: 2.2.25 (7be1766) Operating system:CentOS 7, 64bit, selinux is off. CPU architecture: Intel x86 64bit. Filesystem: xfs # /usr/local/bin/doveconf -n # 2.2.25 (7be1766): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.10.0-327.28.2.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_mechanisms = plain login auth_ssl_username_from_cert = yes disable_plaintext_auth = no mail_location = maildir:~/Maildir 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 = imap service auth-ssl { executable = auth -o auth_ssl_require_client_cert=yes unix_listener auth-master-ssl { mode = 0666 } unix_listener login/login-ssl { mode = 0666 } } service imap-login-ssl { chroot = login executable = imap-login -l imap-ssl login-ssl inet_listener imaps { port = 993 ssl = yes } user = $default_login_user } service imap-login { inet_listener imaps { port = 0 } } service imap-ssl { executable = imap -a auth-master-ssl unix_listener login/imap-ssl { user = $default_login_user } } ssl_ca = </etc/SslCert/dovecot/2016080505CAcert.WithCrl.pem ssl_cert = </etc/SslCert/dovecot/2016080506cert.pem ssl_key = </etc/SslCert/dovecot/2016080506PrivateKey.NoPassPhrase.pem userdb { driver = passwd } protocol imap { auth_ssl_require_client_cert = no ssl_require_crl = no ssl_verify_client_cert = no } protocol imaps { auth_ssl_require_client_cert = yes ssl_require_crl = yes ssl_verify_client_cert = yes } #

1 0

Re: Crash on opening mailbox
by Aki Tuomi 21 Aug '16

21 Aug '16

So it seems. Sorry must've missed them. ---Aki TuomiDovecot oy -------- Original message --------From: Ladislav Laska <laska(a)kam.mff.cuni.cz> Date: 21/08/2016 13:59 (GMT+02:00) To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Cc: dovecot(a)dovecot.org Subject: Re: Crash on opening mailbox Hi! dovecot -n and backtrace are both attached in my original email, due to their size. Did the attachments not arrive? The relevant log does not contain much more than the trace, but here it is: Aug 21 12:58:28 ibex dovecot: imap-login: Login: user=<krakonos>, method=PLAIN, rip=77.48.73.189, lip=78.108.107.19, mpid=17785, TLS, session=<Q5igz5I66sxNMEm9> Aug 21 12:58:28 ibex dovecot: imap(krakonos): Debug: Effective uid=1000, gid=100, home=/home/krakonos Aug 21 12:58:28 ibex dovecot: imap(krakonos): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/.mbox Aug 21 12:58:28 ibex dovecot: imap(krakonos): Debug: mbox: INBOX defaulted to /home/krakonos/.mbox/inbox Aug 21 12:58:28 ibex dovecot: imap(krakonos): Debug: fs: root=/home/krakonos/.mbox, index=, indexpvt=, control=, inbox=/home/krakonos/.mbox/inbox, alt= Aug 21 12:58:29 ibex dovecot: imap(krakonos): Panic: file ../../../src/lib/array.h: line 219 (array_idx_i): assertion failed: (idx * array->element_size < array->buffer->used) Aug 21 12:58:29 ibex dovecot: imap(krakonos): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x8d91e) [0x7fa68fb6a91e] -> /usr/lib64/dovecot/libdovecot.so.0(+0x8da0a) [0x7fa68fb6aa0a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa68fb08fce] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x79e56) [0x7fa68fe6ae56] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0xd6) [0x7fa68fe6b2a6] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x3d) [0x7fa68fe1e93d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x8de70) [0x7fa68fe7ee70] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x8e062) [0x7fa68fe7f062] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fa68fb74e03] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fa68fb7583d] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7fa68fb56042] -> /usr/lib64/dovecot/libdovecot.so.0(+0x736c1) [0x7fa68fb506c1] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fa68fb74e03] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fa68fb7583d] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7fa68fb56042] -> /usr/lib64/dovecot/libdovecot.so.0(+0x736c1) [0x7fa68fb506c1] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fa68fb74e03] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fa68fb7583d] -> /usr/lib64/dovecot/libdovecot.so.0(message_get_header_size+0x74) [0x7fa68fb59d64] -> /usr/lib64/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x317) [0x7fa68fea7ff7] -> dovecot/imap() [0x41d4ae] -> dovecot/imap() [0x41b9fc] -> dovecot/imap(imap_fetch_more+0x3a) [0x41ca0a] -> dovecot/imap(cmd_fetch+0x32c) [0x40f57c] -> dovecot/imap(command_exec+0x9c) [0x41a29c] -> dovecot/imap() [0x418772] -> dovecot/imap() [0x418800] -> dovecot/imap(client_handle_input+0x175) [0x418b95] Aug 21 12:58:29 ibex dovecot: imap(krakonos): Fatal: master: service(imap): child 17785 killed with signal 6 (core dumped) On Sat, Aug 20, 2016 at 01:25:01AM +0300, Aki Tuomi wrote: > > > On August 19, 2016 at 10:00 PM Ladislav Laska <laska(a)kam.mff.cuni.cz> wrote: > > > > > > Hi! > > > > I'm currently experiencing a crash of dovecot 2.2.25 on Gentoo, upon opening > > mailbox. The crash only triggers on opening inbox, other mailboxes seem to > > work fine. It happens every time, and can be reproduced on request. I also > > briefly tried 2.2.19, and it behaves the same. > > > > The bug seems to be triggered by some mail, as I encountered it previously > > and fixed by removing some spam. I guess it might be malformed header of > > some kind. I can open the mailbox locally using mutt, but fail to do so > > remotely (using mutt or K-9 mail on android). Unforunately, I haven't been > > able to isolate the specific mail, as when I create a new mailbox, dovecot > > refuses to open it: > > > > [CANNOT] Mailbox isn't a valid mbox file (0.000 + 0.000 secs). > > > > I'm not really sure what's going on and will investigate further once I find > > some time to do so. > > > > I also experienced a similar problem on opening a specific mail, but it's > > much harder to reproduce and I currently don't have an example. The crash > > looks very similar, and only happens on first attempt to open a specific > > mail, it always works later on. > > > > I'm attaching a stack trace and dovecot -n. I'm also willing to send the > > binary and core dump, but not publicly, as I'm not eager to share whatever's > > inside with the whole world. > > > > Other than what I mentioned, I'm running pretty standard setup, with postfix > > on Gentoo x86_64, ext4 fs, quota and disk space is plentiful. The delivery > > agent is dovecot itself, in postfix/main.cf I have: > > > > mailbox_command = /usr/libexec/dovecot/deliver > > > > I'm using sieve script to file my mail, but the problem manifested even > > before when I was still using procmail to deliver my mail (I migrated > > because I had doubts about procmail and dovecot lock cooperation) > > > > I'll keep my mailbox corrupted for a few more days, and access the mail only > > locally, hoping to test a potential fix. Let me know if you need any more > > info/experimentation. Also, if you know a good way to find the mail that > > causes the trouble out of the core, let me know, I'd be glad to forward it > > for testing. > > > > Thanks and I hope we can find (and fix) the problem! > > > > -- S pozdravem Ladislav Láska > > <laska(a)kam.mff.cuni.cz> > > Katedra Aplikované Matematiky, MFF UK tel.: +420 739 464 167 > > Hi! > > Please provide > > doveconf -n > > relevant log files (or at least anything you care to share) > > gdb /path/to/binary /path/to/core > bt full > > --- > Aki Tuomi > Dovecot Oy -- S pozdravem Ladislav Láska <laska(a)kam.mff.cuni.cz> Katedra Aplikované Matematiky, MFF UK tel.: +420 739 464 167

1 0

Dovecot & Thunderbird on shared mbox
by Ruga 19 Aug '16

19 Aug '16

Occasional error from TB when selecting a dovecot's shared mbox: "Unable to open the summary file for [shared]" "Perhaps there was an error on disk, or the full path is too long." The server's disk is clear, and the longest full path is [a-zA-Z\/\.]{46}. The error occurs occasionally.

2 2

POP3 strange logging behavior after upgrade from 2.2.13 to 2.2.25
by Iavor Stoev 19 Aug '16

19 Aug '16

Hello, I've tested the patch and can confirm that the issue is resolved. Thank you for your assistance! Iavor Stoev Project Manager // Head of System & Network Administration Department ICDSoft Ltd - http://icdsoft.com On 18.8.2016 г. 18:14 ч., dovecot-request(a)dovecot.org wrote: > Hi! > > This has been now fixed in > https://github.com/dovecot/core/commit/7424d35ff1b7d17c0caf7b426c0ef3c2b822… > > Aki Tuomi > Dovecot Oy

1 0

What might cause messages delivered with dovecot-lda to be "invisible" to IMAP clients?
by Ben Johnson 19 Aug '16

19 Aug '16

Hello! I'm attempting to use dovecot-lda, and for whatever reason, messages that I send with it are not visible in my IMAP client. $ dovecot --version 2.2.22 (fe789d2) (Full "doveconf -n" output is at the bottom of this message!) Here's the the sequence of commands that I'm using: # su vmail $ echo 'This is a test message.' > /tmp/test.txt $ stat /tmp/test.txt File: '/tmp/test.txt' Size: 24 Blocks: 8 IO Block: 4096 regular file Device: fd01h/64769d Inode: 783925 Links: 2 Access: (0664/-rw-rw-r--) Uid: ( 5000/ vmail) Gid: ( 5000/ vmail) Access: 2016-08-18 20:49:38.419011552 -0400 Modify: 2016-08-18 20:49:07.178995015 -0400 Change: 2016-08-18 20:49:38.191011425 -0400 Birth: - $ /usr/lib/dovecot/dovecot-lda -d "test(a)example.com" -p "/tmp/test.txt" When I do this, the destination mailbox acts like there's a new message (I'm using Thunderbird, and the mailbox is highlighted in blue and bolded, which is the "new mail" behavior in this client). But when I "check my inbox", i.e., click on the Inbox, I don't see the new message. With regard to the filesystem, the message is present and contains the intended contents. Here's the "stat" output: $ stat /var/vmail/example.com/ben/Maildir/cur/1471567777.M685753P32257.example.com,S=24:2, File: '/var/vmail/example.com/ben/Maildir/cur/1471567777.M685753P32257.example.com,S=24:2,' Size: 24 Blocks: 8 IO Block: 4096 regular file Device: fd01h/64769d Inode: 783925 Links: 2 Access: (0664/-rw-rw-r--) Uid: ( 5000/ vmail) Gid: ( 5000/ vmail) Access: 2016-08-18 20:51:05.647059340 -0400 Modify: 2016-08-18 20:50:58.543055378 -0400 Change: 2016-08-18 20:50:58.543055378 -0400 Birth: - Might anyone know why I'm not "seeing" this message in my IMAP client? Interestingly, I tried another IMAP client (Blue Mail for Android), and I can actually see the messages there, but they appear in the Inbox as: (No subject) <Empty Message> When I click on the messages, Blue Mail simply displays "No text", without the quotes. Surely, I'm overlooking something simple... Thank you for any help here! -Ben Full "doveconf -n" output: $ doveconf -n # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-34-generic x86_64 Ubuntu 16.04.1 LTS auth_mechanisms = plain login disable_plaintext_auth = no listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_max_userip_connections = 100 mail_plugins = " quota" mail_privileged_group = vmail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /bin/bash antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = SPAM;JUNK antispam_trash_pattern_ignorecase = trash;Deleted * antispam_verbose_debug = 1 quota = dict:user::file:/var/vmail/%d/%n/.quotausage quota_rule2 = Trash:storage=+100M quota_rule3 = Junk:ignore quota_rule4 = INBOX:storage=+100M quota_warning = storage=100%% quota-reached 100 %u %d quota_warning2 = storage=95%% quota-warning 95 %u %d quota_warning3 = storage=80%% quota-warning 80 %u %d quota_warning4 = -storage=100%% quota-below below %u %d sieve = /var/vmail/%d/%n/.sieve sieve_max_redirects = 25 } postmaster_address = postmaster(a)example.com protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service imap-login { client_limit = 1000 process_limit = 512 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service quota-below { executable = script /usr/local/bin/quota-below.sh unix_listener quota-below { group = vmail mode = 0666 user = vmail } user = vmail } service quota-reached { executable = script /usr/local/bin/quota-reached.sh unix_listener quota-reached { group = vmail mode = 0666 user = vmail } user = vmail } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0666 user = vmail } user = vmail } ssl_cert = </etc/postfix/smtpd.cert ssl_key = </etc/postfix/smtpd.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota antispam } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota } protocol lmtp { mail_plugins = quota sieve postmaster_address = webmaster@localhost }

1 1

Quota issue: enforced, but reporting issue
by dovecot＠avv.solutions 18 Aug '16

18 Aug '16

Hello everyone, I face the following challenge: - dovecot 2.2.13 - userdb: passwd-file - quota enabled: -- default 1GB -- changed for some users thru users file: user@domain:passwd::::::userdb_quota_rule=*:storage=15M - when sending a message to this user while near quota, warnings are correctly triggered => *OK* - when sending a message to this user while over quota, message is refused => *OK* - when checking quota from mail client (eg Thunderbird 45.2), reported quota is.. 1GB => *NOK* - some config: mail_plugins = quota notify acl plugin { acl_shared_dict = file:/sd/MAIL_IMAP_POP/%d/shared-mailboxes quota = maildir:User quota:ns= quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_rule = *:storage=1G quota_rule2 = Trash:storage=+10%% quota_rule3 = Spam:storage=+20%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=90%% quota-warning 90 %u %d quota_warning2 = storage=75%% quota-warning 75 %u %d } protocol imap { mail_plugins = quota notify acl imap_quota imap_acl service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } - 90-quota: passdb { driver = passwd-file args = scheme=CRYPT username_format=%u /etc/dovecot/users } userdb { driver = passwd-file args = username_format=%u /etc/dovecot/users # Default fields that can be overridden by passwd-file #default_fields = quota_rule=*:storage=1G # Override fields from passwd-file #override_fields = home=/home/virtual/%u } Any idea? Already spent hours on this. Thank you in advance for the help. Cheers A.

1 0

Reporting on CephFS being ready to use with Dovecot
by Daniel van Ham Colchete 18 Aug '16

18 Aug '16

I would like to report that from version 10.2.3 on (next release), Ceph FS is working really well with Dovecot systems. For those that don't know, Ceph is a "distributed object store and file system designed to provide excellent performance, reliability and scalability.". We have used it here since 2013 very successfully, but never with our Dovecot setup. For more information go on http://ceph.com/. Since Ceph Jewel (the current version), Ceph FS is considered production ready by their team. With Ceph FS you have a cache-coherent POSIX-compliant [1] clustered file system, without most of the NFS shortcomings. Ceph have very nice features like online upgrades, online maintenance, constant deep scrubbing of replicated data, cache tiering (HD -> SSD -> etc), erasure coding (clustered RAID6 for really old email - I'm not using), etc. Ceph is very complex to operate but very flexible and robust. This year we moved our Dovecot servers to a Ceph based system, found one bug there (http://tracker.ceph.com/issues/15920) when Dovecot's LMTP was delivery an email, and the fix is about to be released on version 10.2.3. I have been using a fix-build here for a couple of months without issue. So, now I'm glad to share with you guys that it works really well! My setup involves two clusters, each with about 30k-40k users. Each cluster will have two HD storages (with 6TB HDs), two SSD storages (with Intel 480GB SSDs) and two frontends. In a few months will add a third server of each type. Clusters work better with 3's. Here we used mdbox as it is better performant on Ceph for maintenance tasks, since each file is an object on Ceph and maintenance costs increase with the number of objects. We created two base directories: - /srv/dovecot/mail/%d/%n - stored on HDs with the most recent files cached on SSDs, thanks to Ceph Cache Tiering. Also, the directory structure itself is stored on SSDs, so dir listings are very fast (Ceph FS Metadata). - /srv/dovecot/index/%d/%n - stored only on SSDs, thanks for Ceph FS file layout. On our setup about 17% of the IOPs are going to HDs, the rest will go to SSDs, even though SSDs are less than 5% of the space. This is a matter of tuning the cache tiering parameters, but we didn't look at that yet. That setup is working like a charm, performance is about 53% better than when we were using NFS on the same hardware. Our previous DRBD+Heartbeat setup didn't allow for online maintenance and had a few problems. Now we can do 100% online maintenance on storage without users noticing, and on frontends with just a reconnect but without any downtime. Ceph is hard to learn at first but those with bigger setups and stronger SLAs will want to take a look at that. I really recommend that the Dovecot community take at look at that setup. Good luck! Best, Daniel Colchete [1] http://docs.ceph.com/docs/hammer/dev/differences-from-posix/

3 2

POP3 strange logging behavior after upgrade from 2.2.13 to 2.2.25
by Iavor Stoev 18 Aug '16

18 Aug '16

Hello, After the upgrade from Dovecot version 2.2.13 to 2.2.25, we experience the following strange behavior with POP3 logging. When a connection is closed with reason "Connection closed" & "Disconnected for inactivity", the number of deleted mails is missing. Like del=/1166 & del=/4138 from the example bellow. With Dovecot 2.2.13: Feb 14 03:35:20 serverXYZ dovecot: pop3(user(a)domain.com): Connection closed top=0/0, retr=0/0, del=0/946, size=39500197 Feb 15 16:49:18 serverXYZ dovecot: pop3(user(a)domain.com): Disconnected for inactivity top=0/0, retr=0/0, del=0/739, size=52319632 With Dovecot 2.2.25: Jul 31 02:56:03 serverXYZ dovecot: pop3(user(a)domain.com): Connection closed top=1/1380, retr=0/0, del=/4138, size=284167741 Jul 31 02:34:47 serverXYZ dovecot: pop3(user(a)domain.com): Disconnected for inactivity top=0/0, retr=0/0, del=/1166, size=111425436 For sessions completed normally, everything works fine with both Dovecot versions: Jul 31 06:55:48 serverXYZ dovecot: pop3(user(a)domain.com): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Jul 31 02:36:59 serverXYZ dovecot: pop3(user(a)domain.com): Disconnected: Logged out top=0/0, retr=1/18821, del=1/1, size=18803 Please advise if this behavior is normal and if yes how should we read entries like "del=/4138"? Thank you Iavor Stoev Project Manager // Head of System & Network Administration Department ICDSoft Ltd - http://icdsoft.com

2 1

2.3.0~alpha0-1~auto+197: Crash when openening a message via IMAP
by Ralf Hildebrandt 18 Aug '16

18 Aug '16

>From the log: Jul 11 13:12:42 mproxy dovecot: imap-login: Login: user=<hildeb>, method=PLAIN, rip=141.42.206.36, lip=141.42.206.11, mpid=27254, TLS, session=<TGwoO1o3id+NKs4k> Jul 11 13:12:44 mproxy dovecot: imap(hildeb)<TGwoO1o3id+NKs4k>: Panic: file imap-client.c: line 854 (client_check_command_hangs): assertion failed: ((io_loop_find_fd_conditions(current_ioloop, client->fd_out) & IO_WRITE) != 0) Jul 11 13:12:44 mproxy dovecot: imap(hildeb)<TGwoO1o3id+NKs4k>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x8e09e) [0x7efd1d3a309e] -> /usr/lib/dovecot/libdovecot.so.0(+0x8e18c) [0x7efd1d3a318c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7efd1d34169e] -> dovecot/imap [hildeb 141.42.206.36 UID FETCH - 8192 bytes waiting corked](+0x1ad42) [0x55649b35cd42] -> dovecot/imap [hildeb 141.42.206.36 UID FETCH - 8192 bytes waiting corked](client_output+0x118) [0x55649b35ce68] -> /usr/lib/dovecot/libdovecot.so.0(+0xaf370) [0x7efd1d3c4370] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7efd1d3b715c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7efd1d3b85b1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7efd1d3b71e5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x30) [0x7efd1d3b7380] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7efd1d347c13] -> dovecot/imap [hildeb 141.42.206.36 UID FETCH - 8192 bytes waiting corked](main+0x322) [0x55649b34faf2] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7efd1cf6c830] -> dovecot/imap [hildeb 141.42.206.36 UID FETCH - 8192 bytes waiting corked](+0xdc6f) [0x55649b34fc6f] Jul 11 13:12:44 mproxy dovecot: imap(hildeb)<TGwoO1o3id+NKs4k>: Fatal: master: service(imap): child 27254 killed with signal 6 (core dumped) # 2.3.0.alpha0 (3aae884) [XI:2:2.3.0~alpha0-1~auto+197]: /etc/dovecot/dovecot.conf -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

3 5