Re: v2.2.26.0 released

2016-11-01 Thread Michael A. Peters 

I can confirm that LibreSSL 2.4.3 works just fine for building 2.2.26.0

On 11/01/2016 09:25 PM, Reuben Farrelly wrote:

I don't believe that is the case.

I have 2.2.26.0 and -git building and running on multiple systems now
(two of which are Gentoo boxes) with LibreSSL-2.5 - and these systems do
not have OpenSSL installed.  Are you running an old version of LibreSSL
perhaps?

I *think* LibreSSL-2.4 was OK as well.

Reuben


On 2/11/2016 4:46 AM, Ruga wrote:

Hello,

We cannot upgrade from 2.2.24, because we use libressl and the newer
dovecot versions demand openssl v1.1.

Please add the new library requirement to the INSTALL file.

All the best.

Re: v2.2.26.0 released

2016-11-01 Thread Reuben Farrelly 

I don't believe that is the case.

I have 2.2.26.0 and -git building and running on multiple systems now 
(two of which are Gentoo boxes) with LibreSSL-2.5 - and these systems do 
not have OpenSSL installed.  Are you running an old version of LibreSSL 
perhaps?


I *think* LibreSSL-2.4 was OK as well.

Reuben


On 2/11/2016 4:46 AM, Ruga wrote:

Hello,

We cannot upgrade from 2.2.24, because we use libressl and the newer
dovecot versions demand openssl v1.1.

Please add the new library requirement to the INSTALL file.

All the best.

Re: Repeat e-mail syndrome shows up in 2.2.26+

2016-11-01 Thread The Doctor 
On Tue, Nov 01, 2016 at 02:01:28PM -0300, Juan Bernhard wrote:
> 
> El 01/11/2016 a las 01:26 p.m., The Doctor escribi?:
> > Getting complaints from people about pop/imap
> >
> > issues.
> >
> > some people are getting repaeted e-mail.
> >
> > Other are not able to delete their e-mails from an IMAP lcient.

> Did you try to delete the dovecots cache? I had the same problem once, 
> when I restored a backup of some mails. I deleted all dovecot.index* on 
> home directories of the user

Tried that no dice.

This is affecting POP3/IMAP clients such as Thunderbird, Entourage, 
Outlook, OE, and MS Live Mail.

I ran the rc1 and the problem was not there.

As soon as the release hit the problem started to crop up.

Using FreeBSD 11.0 - p2

> >
> > Current configuration
> >
> > /usr/dovecot2/sbin/dovecot -n
> > # 2.2.26.0 (23d1de6): /usr/dovecot2/etc/dovecot/dovecot.conf
> > # OS: FreeBSD 11.0-RELEASE-p2 amd64
> > base_dir = /var/run/dovecot/
> > disable_plaintext_auth = no
> > first_valid_uid = 100
> > info_log_path = /var/log/dovecot-info.log
> > listen = [::]
> > log_path = /var/log/dovecot.log
> > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c
> > mail_debug = yes
> > mail_location = mbox:~/mail:INBOX=/var/mail/%u
> > mail_log_prefix = %Us(%u):
> > mdbox_rotate_size = 2 k
> > passdb {
> >args = /etc/master.passwd
> >  driver = passwd-file
> >  }
> >  plugin {
> >home = /usr/dovecot2
> >}
> >service auth {
> > executable = /usr/dovecot2/libexec/dovecot/auth
> >   user = root
> >   }
> >   service imap-login {
> > chroot = login
> >   client_limit = 256
> > executable = /usr/dovecot2/libexec/dovecot/imap-login
> >   inet_listener imap {
> >   address = 204.209.81.1, 127.0.0.1
> >   port = 143
> > }
> >   inet_listener imaps {
> >   address = 204.209.81.1, 127.0.0.1
> >   port = 993
> >   ssl = yes
> > }
> >   process_limit = 128
> > process_min_avail = 3
> >   service_count = 1
> > user = dovecot
> > }
> > service imap {
> >   executable = 
> > /usr/dovecot2/libexec/dovecot/imap
> > process_limit = 512
> > }
> > service lmtp {
> >   executable = lmtp -L
> > inet_listener lmtp {
> > address = 
> > 204.209.81.1 127.0.0.1 ::1
> > port = 24
> >   }
> > 
> > process_min_avail = 5
> > }
> > service 
> > pop3-login {
> >   
> > chroot = login
> > 
> > client_limit = 256
> >   
> > executable = /usr/dovecot2/libexec/dovecot/pop3-login
> > 
> > inet_listener pop3 {
> > 
> > address = 204.209.81.1
> > 
> > port = 110
> > 
> >   }
> > 
> > inet_listener pop3s {
> > 
> > address = 204.209.81.1
> > 
> > port = 995
> > 
> > ssl = yes
> > 
> >   }
> > 
> >

Re: Outlook 2010 woes

2016-11-01 Thread Bryan Holloway 

On 11/1/16 6:20 PM, Bryan Holloway wrote:

In case anyone is interested, we finally found the problem:

The new (2.2) server had "auth_mechanisms" of "digest-md5" enabled along
with "plain". This is what was causing the four-second delay, but only
with Outlook clients.

Everything is working great now across the board.

Thanks again to everyone's suggestions.

- bryan



Sorry -- that wasn't very clear, was it:

Removing "digest-md5" fixed the issue.



On 10/27/16 7:09 PM, Bryan Holloway wrote:

So after several days of more troubleshooting, I have some things to
report to the list.

First and foremost, I have discovered that the issue has nothing to do
with SSL/TLS, which was my earlier suspicion because after doing some
PCAPs I discovered that the transactions were negotiating TLS 1.2 on the
new server, as opposed to 1.0 on the old.

Also thank you for the rawlog suggestion: that helped a lot in
determining what was happening on the IMAP level.

That all said, this is what I've discovered:

There is a very curious and reproducible four-second delay during the
negotiation between server and client which is not present in Dovecot
2.1. This is what our customer is complaining about using Outlook 2010.

During a plaintext TCP stream, I'm seeing this:

1. Client connects (SYN) to server.

2. Server ACKs and throws back CAPABILITIES.

3. User attempts to auth with DIGEST-MD5.

4. Server says, "no thanks." (Not sure why, but I don't believe this is
relevant.)

5. User attempts to auth with plaintext.

6. Server says, "Yup. You are you. You're logged in."

7. Client sends the following: ID ("name" "Microsoft Outlook" "version"
"14.0")

8. Server sends an ACK

... and then there's this very curious four-second delay.

9. Server then sends out new CAPABILITIES, and everything proceeds
thereafter as normal and zippy and fast.

Does this shed any light on the subject?


On 10/13/16 11:21 AM, Bryan Holloway wrote:

On 10/13/16 11:01 AM, Aki Tuomi wrote:



On October 13, 2016 at 6:52 PM Konstantin Khomoutov
 wrote:


On Thu, 13 Oct 2016 10:35:14 -0500
Bryan Holloway  wrote:


[...]

Is there a way to see the IMAP commands coming from the client?
I've tried looking at PCAPs, but of course they're encrypted so I
can't see the actual dialog going on between the server and
client. I didn't see an obvious way to do this in the docs.


If you have access to the SSL/TLS key (IOW, the private part of the
cert) the server uses to secure IMAP connections you can dump the
IMAP traffic using the `ssldump` utility (which builds on
`tcpdump`).


I do, but the client is using a DH key exchange so I only have the
server-side private key.

Tried that using Wireshark's decoder features and ran into this
problem. I'm assuming I'd run into the same using ssldump, but I'll
give it a shot!


I think DH is not the culprit: just to be able to actually decode SSL
traffic, you must have the server private key when you're decoding the
SSL handshake phase -- to be able to recover the session keys, which
you then use to decode the actual tunneled data.


You can also enable only non DH algorithms in ssl settings if rawlog
isn't working for you.

Aki



Ah -- interesting tip. I hadn't thought of that. Thank you! I'll report
my findings to the list.

Re: Outlook 2010 woes

2016-11-01 Thread Bryan Holloway 

In case anyone is interested, we finally found the problem:

The new (2.2) server had "auth_mechanisms" of "digest-md5" enabled along 
with "plain". This is what was causing the four-second delay, but only 
with Outlook clients.


Everything is working great now across the board.

Thanks again to everyone's suggestions.

- bryan


On 10/27/16 7:09 PM, Bryan Holloway wrote:

So after several days of more troubleshooting, I have some things to
report to the list.

First and foremost, I have discovered that the issue has nothing to do
with SSL/TLS, which was my earlier suspicion because after doing some
PCAPs I discovered that the transactions were negotiating TLS 1.2 on the
new server, as opposed to 1.0 on the old.

Also thank you for the rawlog suggestion: that helped a lot in
determining what was happening on the IMAP level.

That all said, this is what I've discovered:

There is a very curious and reproducible four-second delay during the
negotiation between server and client which is not present in Dovecot
2.1. This is what our customer is complaining about using Outlook 2010.

During a plaintext TCP stream, I'm seeing this:

1. Client connects (SYN) to server.

2. Server ACKs and throws back CAPABILITIES.

3. User attempts to auth with DIGEST-MD5.

4. Server says, "no thanks." (Not sure why, but I don't believe this is
relevant.)

5. User attempts to auth with plaintext.

6. Server says, "Yup. You are you. You're logged in."

7. Client sends the following: ID ("name" "Microsoft Outlook" "version"
"14.0")

8. Server sends an ACK

... and then there's this very curious four-second delay.

9. Server then sends out new CAPABILITIES, and everything proceeds
thereafter as normal and zippy and fast.

Does this shed any light on the subject?


On 10/13/16 11:21 AM, Bryan Holloway wrote:

On 10/13/16 11:01 AM, Aki Tuomi wrote:



On October 13, 2016 at 6:52 PM Konstantin Khomoutov
 wrote:


On Thu, 13 Oct 2016 10:35:14 -0500
Bryan Holloway  wrote:


[...]

Is there a way to see the IMAP commands coming from the client?
I've tried looking at PCAPs, but of course they're encrypted so I
can't see the actual dialog going on between the server and
client. I didn't see an obvious way to do this in the docs.


If you have access to the SSL/TLS key (IOW, the private part of the
cert) the server uses to secure IMAP connections you can dump the
IMAP traffic using the `ssldump` utility (which builds on
`tcpdump`).


I do, but the client is using a DH key exchange so I only have the
server-side private key.

Tried that using Wireshark's decoder features and ran into this
problem. I'm assuming I'd run into the same using ssldump, but I'll
give it a shot!


I think DH is not the culprit: just to be able to actually decode SSL
traffic, you must have the server private key when you're decoding the
SSL handshake phase -- to be able to recover the session keys, which
you then use to decode the actual tunneled data.


You can also enable only non DH algorithms in ssl settings if rawlog
isn't working for you.

Aki



Ah -- interesting tip. I hadn't thought of that. Thank you! I'll report
my findings to the list.

No stats under FreeBSD 10.3

2016-11-01 Thread Ruud Boon 
HI,

I’m currently testing the stats module of Dovecot (2.2.26.0 (23d1de6))
Looks like there no statistics under FreeBSD.
Server isn’t busy yet but got at least a few connection open.

Added

mail_plugins = $mail_plugins stats

plugin {
   stats_refresh = 30 secs
   stats_track_cmds = yes
}


doveadm stats dump global

reset_timestamp last_update num_logins  num_cmds
num_connected_sessions  auth_successes  auth_master_successes   auth_failures   
auth_db_tempfails   auth_cache_hits auth_cache_misses   user_cpu
sys_cpu clock_time  min_faults  maj_faults  vol_cs  invol_cs
disk_input  disk_output read_count  read_bytes  write_count 
write_bytes mail_lookup_pathmail_lookup_attrmail_read_count 
mail_read_bytes mail_cache_hits
1478031539  0.000   0   0   0   0   0   
0   0   0   0.0 0.0 0.0 0   0   0   0   
0   0   0   0   0   0   0   0   0   0   0

Cheers,
Ruud

Dovecot 2 LDAP "unknown user"

2016-11-01 Thread Peter Fraser 
Hi All
I am using Dovecot dovecot2-2.2.25_6 on FreeBSD 11. I am trying to set up
LDAP authentication to Active Director as I had it in version 1 of Dovecot.
My settings are at bottom. When I run doveadm auth test username, I get
back
root@BSD-11:/usr/local/etc/dovecot # doveadm auth test username
Password:
passdb: user auth succeeded
extra fields:
  user=username
root@BSD-11:/usr/local/etc/dovecot #

But when I run telnet 127.0.0.1 110 and try to log in it says unknown user.
Error below in maillog.
BSD-11 dovecot: pop3: Error: Authenticated user not found from userdb, auth
lookup id=2262958081 (client-pid=2273 client-id=1)
Nov  1 15:15:41 BSD-11 dovecot: pop3-login: Internal login failure
(pid=2273 id=1) (internal failure, 1 successful auths): user=



root@BSD-11:/usr/local/etc/dovecot # doveconf -n
# 2.2.25 (7be1766): /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 11.0-RELEASE-p1 i386
auth_debug = yes
auth_verbose = yes
listen = *
login_greeting = Mail Server ready.
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 {
  args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
ssl_cert =

Re: doveadm index: can't index a different namespace?

2016-11-01 Thread Larry Rosenman 
Nothing in them from what I can see.

Nov  1 13:25:14 thebighonker dovecot: indexer-worker(mrm): Debug: fs:
root=/home/mrm/mail, index=, indexpvt=, control=,
inbox=/home/mrm/mail/INBOX, alt=
Nov  1 13:25:14 thebighonker dovecot: indexer-worker(mrm): Debug: Namespace
archive: type=private, prefix=#ARCHIVE/, sep=/, inbox=no, hidden=no,
list=no, subscriptions=yes location=mbox:~/MAILARCHIVE
Nov  1 13:25:14 thebighonker dovecot: indexer-worker(mrm): Debug: mbox:
INBOX defaulted to /home/mrm/MAILARCHIVE/inbox
Nov  1 13:25:14 thebighonker dovecot: indexer-worker(mrm): Debug: fs:
root=/home/mrm/MAILARCHIVE, index=, indexpvt=, control=,
inbox=/home/mrm/MAILARCHIVE/inbox, alt=
Nov  1 13:25:14 thebighonker exim[6544]: 1c1dkI-0001gw-B7 => mrm <
m...@lerctr.org> R=localuser T=dovecot_lmtp S=11532 C="250 2.0.0 <
m...@lerctr.org> pfbVHwreGFhQFgAAu+mOrA Saved" QT=0s DT=0s
Nov  1 13:25:14 thebighonker exim[6544]: 1c1dkI-0001gw-B7 Completed QT=0s
Nov  1 13:25:15 thebighonker dovecot: indexer-worker(mrm): Debug: Mailbox
INBOX: Opened mail UID=447860 because: fts indexing
Nov  1 13:25:15 thebighonker dovecot: indexer-worker(mrm): Indexed 1
messages in INBOX
Nov  1 13:25:19 thebighonker exim[6519]: H=(ylmf-pc) [69.64.78.83]:57747
I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc
Nov  1 13:25:27 thebighonker dovecot: imap-login: Login: user=,
method=PLAIN, rip=2001:470:1f0f:3ad:223:7dff:fe9e:6e8a,
lip=2001:470:1f0f:3ad:223:7dff:fe9e:6e8a, mpid=6583, TLS,
session=
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: Loading modules
from directory: /usr/local/lib/dovecot
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: Module loaded:
/usr/local/lib/dovecot/lib15_notify_plugin.so
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: Module loaded:
/usr/local/lib/dovecot/lib20_fts_plugin.so
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: Module loaded:
/usr/local/lib/dovecot/lib20_mail_log_plugin.so
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: Module loaded:
/usr/local/lib/dovecot/lib21_fts_lucene_plugin.so
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: Module loaded:
/usr/local/lib/dovecot/lib90_stats_plugin.so
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: Module loaded:
/usr/local/lib/dovecot/lib95_imap_stats_plugin.so
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: Effective uid=1001,
gid=1001, home=/home/ler
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: Namespace inbox:
type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes,
subscriptions=yes location=mbox:~/mail:INBOX=~/mail/INBOX
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: fs:
root=/home/ler/mail, index=, indexpvt=, control=,
inbox=/home/ler/mail/INBOX, alt=
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: Namespace archive:
type=private, prefix=#ARCHIVE/, sep=/, inbox=no, hidden=no, list=no,
subscriptions=yes location=mbox:~/MAILARCHIVE
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: mbox: INBOX
defaulted to /home/ler/MAILARCHIVE/inbox
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Debug: fs:
root=/home/ler/MAILARCHIVE, index=, indexpvt=, control=,
inbox=/home/ler/MAILARCHIVE/inbox, alt=
Nov  1 13:25:27 thebighonker dovecot: imap(ler): Logged out in=6049
out=63372 fhc=50 fhb=22424 fbc=0 fbb=0 del=0 exp=0 trash=0
Nov  1 13:25:29 thebighonker exim[6561]: H=(ylmf-pc) [69.64.78.83]:63376
I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc
Nov  1 13:25:39 thebighonker exim[6585]: H=(ylmf-pc) [69.64.78.83]:60216
I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc
Nov  1 13:25:46 thebighonker exim[6588]: no host name found for IP address
125.123.158.215
Nov  1 13:25:47 thebighonker exim[6588]: H=(qrhx) [125.123.158.215]:60710
I=[192.147.25.65]:25 F= rejected RCPT <3371453...@qq.com>:
RBL: found in zen.spamhaus.org (127.0.0.11) (https://ww
w.spamhaus.org/query/ip/125.123.158.215)
Nov  1 13:25:48 thebighonker exim[6588]: unexpected disconnection while
reading SMTP command from (qrhx) [125.123.158.215]:60710
I=[192.147.25.65]:25
Nov  1 13:25:49 thebighonker exim[6590]: H=(ylmf-pc) [69.64.78.83]:60073
I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc
Nov  1 13:25:59 thebighonker exim[6608]: H=(ylmf-pc) [69.64.78.83]:60168
I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc
Nov  1 13:26:09 thebighonker exim[6613]: H=(ylmf-pc) [69.64.78.83]:55031
I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc
Nov  1 13:26:15 thebighonker dovecot: imap-login: Login: user=,
method=PLAIN, rip=2600:1:d613:48fb:b5da:4a31:b4b6:7ff8,
lip=2001:470:1f0f:3ad:223:7dff:fe9e:6e8a, mpid=6645, TLS,
session=
Nov  1 13:26:15 thebighonker dovecot: imap(ler): Debug: Loading modules
from directory: /usr/local/lib/dovecot
Nov  1 13:26:15 thebighonker dovecot: imap(ler): Debug: Module loaded:
/usr/local/lib/dovecot/lib15_notify_plugin.so
Nov  1 13:26:15 thebighonker dovecot:

Re: doveadm index: can't index a different namespace?

2016-11-01 Thread Aki Tuomi 
Server logs would be appreciated. 

Aki

> On November 1, 2016 at 8:30 PM Larry Rosenman  wrote:
> 
> 
> doveadm -D  -vv index  \#ARCHIVE/\* garners the below for ALL mailboxes
> in the
> namespace:
> doveadm(ler): Error: Mailbox #ARCHIVE/2013/04/clamav-rules: Status lookup
> failed: Internal error occurred. Refer to server log for more information.
> [2016-11-01 13:25:21]
> doveadm(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't
> selectable
> doveadm(ler): Error: Mailbox #ARCHIVE/2013/04/SA/FN: Status lookup failed:
> Internal error occurred. Refer to server log for more information.
> [2016-11-01 13:25:21]
> thebighonker.lerctr.org ~ $
> 
> doveconf -n attached.
> 
> 2.2.26.0, pigeonhole 0.4.16, clucene from FreeBSD ports.
> 
> What else do we need here?
> 
> 
> 
> -- 
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com
> US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

doveadm index: can't index a different namespace?

2016-11-01 Thread Larry Rosenman 
doveadm -D  -vv index  \#ARCHIVE/\* garners the below for ALL mailboxes
in the
namespace:
doveadm(ler): Error: Mailbox #ARCHIVE/2013/04/clamav-rules: Status lookup
failed: Internal error occurred. Refer to server log for more information.
[2016-11-01 13:25:21]
doveadm(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't
selectable
doveadm(ler): Error: Mailbox #ARCHIVE/2013/04/SA/FN: Status lookup failed:
Internal error occurred. Refer to server log for more information.
[2016-11-01 13:25:21]
thebighonker.lerctr.org ~ $

doveconf -n attached.

2.2.26.0, pigeonhole 0.4.16, clucene from FreeBSD ports.

What else do we need here?



-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281
# 2.2.26.0 (23d1de6): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.16 (fed8554)
# OS: FreeBSD 10.3-STABLE amd64  
auth_default_realm = lerctr.org
auth_mechanisms = plain login
auth_realms = lerctr.org thebighonker.lerctr.org tbh.lerctr.org
auth_username_format = %Ln
default_vsz_limit = 1 G
deliver_log_format = msgid=%m: %$ (subject=%s from=%f size=%w)
lda_mailbox_autocreate = yes
listen = 192.147.25.65, ::
lmtp_save_to_detail_mailbox = yes
login_access_sockets = tcpwrap
mail_attribute_dict = file:~/mail/.imap/dovecot-mail-attributes
mail_debug = yes
mail_location = mbox:~/mail:INBOX=~/mail/INBOX
mail_plugins = fts fts_lucene notify stats
mail_privileged_group = mail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character 
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy 
include variables body enotify environment mailbox date index ihave duplicate 
mime foreverypart extracttext vacation-seconds editheader
namespace archive {
  hidden = no
  list = no
  location = mbox:~/MAILARCHIVE
  prefix = "#ARCHIVE/"
  separator = /
}
namespace inbox {
  inbox = yes
  location = 
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox INBOX {
auto = create
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox SA/FN {
special_use = \Junk
  }
  mailbox SENT {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
}
passdb {
  args = failure_show_msg=yes session=yes max_requests=20
  driver = pam
}
plugin {
  fts = lucene
  fts_autoindex = yes
  fts_lucene = whitespace_chars=@. normalize no_snowball
  fts_tika = http://localhost:9998/tika/
  mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename 
flag_change append
  mail_log_fields = uid box msgid size from subject vsize flags
  recipient_delimiter = +
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
  sieve_extensions = +editheader +vacation-seconds
  stats_command_min_time = 1 mins
  stats_domain_min_time = 12 hours
  stats_ip_min_time = 12 hours
  stats_memory_limit = 16 M
  stats_refresh = 5s
  stats_session_min_time = 15 mins
  stats_track_cmds = yes
  stats_user_min_time = 1 hours
}
protocols = imap pop3 lmtp sieve
service auth {
  unix_listener auth-client {
mode = 0666
  }
  unix_listener auth-master {
mode = 0666
  }
}
service stats {
  chroot = empty
  client_limit = 0
  drop_priv_before_exec = no
  executable = stats
  extra_groups = 
  fifo_listener stats-mail {
group = 
mode = 0666
user = 
  }
  group = 
  idle_kill = 4294967295 secs
  privileged_group = 
  process_limit = 1
  process_min_avail = 0
  protocol = 
  service_count = 0
  type = 
  unix_listener stats {
group = 
mode = 0666
user = 
  }
  user = $default_internal_user
  vsz_limit = 18446744073709551615 B
}
service tcpwrap {
  unix_listener login/tcpwrap {
group = $default_login_user
mode = 0600
user = $default_login_user
  }
}
ssl_cert =

Re: v2.2.26.0 released

2016-11-01 Thread Aki Tuomi 
OpenSSL v1.0.1 is enough.

Aki

> On November 1, 2016 at 7:46 PM Ruga  wrote:
> 
> 
> Hello,
> 
> We cannot upgrade from 2.2.24, because we use libressl and the newer
> dovecot versions demand openssl v1.1.
> 
> Please add the new library requirement to the INSTALL file.
> 
> All the best.
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  Original Message 
> Subject: v2.2.26.0 released
> Local Time: 28 October 2016 6:51 PM
> UTC Time: 28 October 2016 16:51
> From: t...@iki.fi
> To: dovecot-n...@dovecot.org, Dovecot Mailing List 
> 
> http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz
> http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz.sig
> 
> v2.2.26 had a couple of nasty bugs left in it, so here's a fixup release. The 
> version number is also a little bit weird, but had to be done this way 
> (although 2.2.26.0.1 could have been another possibility).
> 
> - Fixed some compiling issues.
> - auth: Fixed assert-crash when using NTLM or SKEY mechanisms and
> multiple passdbs.
> - auth: Fixed crash when exporting to auth-worker passdb extra fields
> that had empty values.
> - dsync: Fixed assert-crash in dsync_brain_sync_mailbox_deinit

Re: v2.2.26.0 released

2016-11-01 Thread Ruga 
Hello,

We cannot upgrade from 2.2.24, because we use libressl and the newer
dovecot versions demand openssl v1.1.

Please add the new library requirement to the INSTALL file.

All the best.









 Original Message 
Subject: v2.2.26.0 released
Local Time: 28 October 2016 6:51 PM
UTC Time: 28 October 2016 16:51
From: t...@iki.fi
To: dovecot-n...@dovecot.org, Dovecot Mailing List 

http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.26.0.tar.gz.sig

v2.2.26 had a couple of nasty bugs left in it, so here's a fixup release. The 
version number is also a little bit weird, but had to be done this way 
(although 2.2.26.0.1 could have been another possibility).

- Fixed some compiling issues.
- auth: Fixed assert-crash when using NTLM or SKEY mechanisms and
multiple passdbs.
- auth: Fixed crash when exporting to auth-worker passdb extra fields
that had empty values.
- dsync: Fixed assert-crash in dsync_brain_sync_mailbox_deinit

Re: Repeat e-mail syndrome shows up in 2.2.26+

2016-11-01 Thread Juan Bernhard 


El 01/11/2016 a las 01:26 p.m., The Doctor escribió:

Getting complaints from people about pop/imap

issues.

some people are getting repaeted e-mail.

Other are not able to delete their e-mails from an IMAP lcient.
Did you try to delete the dovecots cache? I had the same problem once, 
when I restored a backup of some mails. I deleted all dovecot.index* on 
home directories of the user


Current configuration

/usr/dovecot2/sbin/dovecot -n
# 2.2.26.0 (23d1de6): /usr/dovecot2/etc/dovecot/dovecot.conf
# OS: FreeBSD 11.0-RELEASE-p2 amd64
base_dir = /var/run/dovecot/
disable_plaintext_auth = no
first_valid_uid = 100
info_log_path = /var/log/dovecot-info.log
listen = [::]
log_path = /var/log/dovecot.log
login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c
mail_debug = yes
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_log_prefix = %Us(%u):
mdbox_rotate_size = 2 k
passdb {
   args = /etc/master.passwd
 driver = passwd-file
 }
 plugin {
   home = /usr/dovecot2
   }
   service auth {
executable = /usr/dovecot2/libexec/dovecot/auth
  user = root
  }
  service imap-login {
chroot = login
  client_limit = 256
executable = /usr/dovecot2/libexec/dovecot/imap-login
  inet_listener imap {
  address = 204.209.81.1, 127.0.0.1
  port = 143
}
  inet_listener imaps {
  address = 204.209.81.1, 127.0.0.1
  port = 993
  ssl = yes
}
  process_limit = 128
process_min_avail = 3
  service_count = 1
user = dovecot
}
service imap {
  executable = 
/usr/dovecot2/libexec/dovecot/imap
process_limit = 512
}
service lmtp {
  executable = lmtp -L
inet_listener lmtp {
address = 
204.209.81.1 127.0.0.1 ::1
port = 24
  }

process_min_avail = 5
}
service 
pop3-login {
  
chroot = login

client_limit = 256
  
executable = /usr/dovecot2/libexec/dovecot/pop3-login

inet_listener pop3 {

address = 204.209.81.1

port = 110

  }

inet_listener pop3s {

address = 204.209.81.1

port = 995

ssl = yes

  }

process_limit = 128

  process_min_avail = 3

service_count = 1

  user = dovecot

Repeat e-mail syndrome shows up in 2.2.26+

2016-11-01 Thread The Doctor 
Getting complaints from people about pop/imap

issues.

some people are getting repaeted e-mail.

Other are not able to delete their e-mails from an IMAP lcient.

Current configuration

/usr/dovecot2/sbin/dovecot -n
# 2.2.26.0 (23d1de6): /usr/dovecot2/etc/dovecot/dovecot.conf
# OS: FreeBSD 11.0-RELEASE-p2 amd64
base_dir = /var/run/dovecot/
disable_plaintext_auth = no
first_valid_uid = 100
info_log_path = /var/log/dovecot-info.log
listen = [::]
log_path = /var/log/dovecot.log
login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c
mail_debug = yes
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_log_prefix = %Us(%u):
mdbox_rotate_size = 2 k
passdb {
  args = /etc/master.passwd
driver = passwd-file
}
plugin {
  home = /usr/dovecot2
  }
  service auth {
executable = /usr/dovecot2/libexec/dovecot/auth
  user = root
  }
  service imap-login {
chroot = login
  client_limit = 256
executable = /usr/dovecot2/libexec/dovecot/imap-login
  inet_listener imap {
  address = 204.209.81.1, 127.0.0.1
  port = 143
}
  inet_listener imaps {
  address = 204.209.81.1, 127.0.0.1
  port = 993
  ssl = yes
}
  process_limit = 128
process_min_avail = 3
  service_count = 1
user = dovecot
}
service imap {
  executable = 
/usr/dovecot2/libexec/dovecot/imap
process_limit = 512
}
service lmtp {
  executable = lmtp -L
inet_listener lmtp {
address = 
204.209.81.1 127.0.0.1 ::1
port = 24
  }

process_min_avail = 5
}
service 
pop3-login {
  
chroot = login

client_limit = 256
  
executable = /usr/dovecot2/libexec/dovecot/pop3-login

inet_listener pop3 {

address = 204.209.81.1

port = 110

  }

inet_listener pop3s {

address = 204.209.81.1

port = 995

ssl = yes

  }

process_limit = 128

  process_min_avail = 3

service_count = 1

  user = dovecot

  }

  service pop3 {

Re: Server migration

2016-11-01 Thread Sami Ketola 

> On 1 Nov 2016, at 14.10, Tanstaafl  wrote:
> 
> On 11/1/2016 3:58 AM, Sami Ketola  wrote:
>> On 31 Oct 2016, at 13.11, Tanstaafl  wrote:
>>> Ok, interesting. So... how does dsync do it? Or would it only work
>>> between two dovecot servers?
>>> 
>>> I'm interested in migrating from other servers (Office 365 in one case).
> 
>> Dsync does not use IMAP protocol to store the mails to storage but instead 
>> uses the 
>> dovecot storage API to do that. Internally we can set what ever properties 
>> we want to
>> including IMAP UIDs and POP3 UIDLs. 
>> 
>> Migrating from legacy system should then be done by pulling the mails from 
>> the
>> legacy platform by using the imapc connector and storing them by using the 
>> internal apis.
>> 
>> We can also store mails to imapc: location but in that case there is many 
>> properties that
>> will be lost due to limitations of the IMAP protocol.
> 
> Thanks Sami, but I don't see a definitive answer top my question in the
> above...
> 
> So, when migrating from legacy system (legacy = non-dovecot) using
> imapc, is dovecot able to preserver the UIDs?


If you fetch emails over imapc and store to dovecot dsync will preserve IMAP 
UIDs.

Sami

Re: Server migration

2016-11-01 Thread Tanstaafl 
On 11/1/2016 3:58 AM, Sami Ketola  wrote:
> On 31 Oct 2016, at 13.11, Tanstaafl  wrote:
>> Ok, interesting. So... how does dsync do it? Or would it only work
>> between two dovecot servers?
>>
>> I'm interested in migrating from other servers (Office 365 in one case).

> Dsync does not use IMAP protocol to store the mails to storage but instead 
> uses the 
> dovecot storage API to do that. Internally we can set what ever properties we 
> want to
> including IMAP UIDs and POP3 UIDLs. 
> 
> Migrating from legacy system should then be done by pulling the mails from the
> legacy platform by using the imapc connector and storing them by using the 
> internal apis.
> 
> We can also store mails to imapc: location but in that case there is many 
> properties that
> will be lost due to limitations of the IMAP protocol.

Thanks Sami, but I don't see a definitive answer top my question in the
above...

So, when migrating from legacy system (legacy = non-dovecot) using
imapc, is dovecot able to preserver the UIDs?

Thanks, and my apologies for being a bit dense...

Re: Released Pigeonhole v0.4.16 for Dovecot v2.2.26.0.

2016-11-01 Thread Stephan Bosch 

Hello Dovecot users,

It has come to our attention that older Pigeonhole releases will not 
work properly anymore with Dovecot v2.2.26.0, while there were no known 
issues with 2.2.26. So, make sure you use the new Pigeonhole v0.4.16 
release if you upgrade Dovecot to v2.2.26.0.


Regards,

Stephan.


Op 30-10-2016 om 23:46 schreef Stephan Bosch:

Hello Dovecot users,

Here's the definitive 0.4.16 release. There were no changes since the
release candidate.

The reported replication issues are still open, since we haven't been
able to reproduce them so far.

Changelog v0.4.16:

* Part of the Sieve extprograms implementation was moved to Dovecot,
   which means that this release depends on Dovecot v2.2.26+.
* ManageSieve: The PUTSCRIPT command now allows uploading empty Sieve
   scripts. There was really no good reason to disallow doing that.
+ Sieve vnd.dovecot.report extension:
   + Added a Dovecot-Reporting-User field to the report body, which
 contains the e-mail address of the user sending the report.
   + Added support for configuring the "From:" address used in the
 report.
+ LDA sieve plugin: Implemented support for a "discard script" that is
   run when the message is going to be discarded. This allows doing
   something other than throwing the message away for good.
+ Sieve vnd.dovecot.environment extension: Added vnd.dovecot.config.*
   environment items. These environment items map to sieve_env_*
   settings from the plugin {} section in the configuration. Such values
   can of course also  be returned from userdb.
+ Sieve vacation extension: Use the Microsoft X-Auto-Response-Suppress
   header to prevent unwanted responses from and to (older) Microsoft
   products.
+ ManageSieve: Added rawlog_dir setting to store ManageSieve traffic
   logs. This replaces at least partially the rawlog plugin (mimics
   similar IMAP/POP3 change).
- doveadm sieve plugin: synchronization: Prevent setting file
   timestamps to unix epoch time. This occurred when Dovecot passed the
   timestamp as 'unknown' during synchronization.
- Sieve exprograms plugin: Fixed spurious '+' sometimes returned at the
   end of socket-based program output.
- imapsieve plugin: Fixed crash occurring in specific situations.
- Performed various fixes based on static analysis and Clang warnings.

The release is available as follows:

http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.16.tar.gz
http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.16.tar.gz.sig

Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for
more information. Have fun testing this release and don't
hesitate to notify me when there are any problems.

Regards,

2.2.26.0: Error: redis: Unexpected input (state=0): -ERR max number of clients reached

2016-11-01 Thread Tom Sommer 

I use redis as quota backend (currently).

After upgrading to 2.2.26.0 I see a ton of "Error: redis: Unexpected 
input (state=0): -ERR max number of clients reached" errors.


It looks like either more Redis connections are being made, or Redis 
connections don't time out/are reused correctly anymore.


No such errors were seen in 2.2.24.

--
Tom

Re: Panic: file mail-transaction-log-file.c: line 104 (mail_transaction_log_file_free): assertion failed: (!file->locked)

2016-11-01 Thread Arkadiusz Miśkiewicz 
On Tuesday 01 of November 2016, Aki Tuomi wrote:
> On 25.08.2016 10:29, Aki Tuomi wrote:
> > On 14.07.2016 10:56, Arkadiusz Miśkiewicz wrote:
> >> 2.2.25 (also happens on 2.2.24). Happens every time I try to make
> >> deliver and only for this user:
> >> 
> >> Jul 14 09:52:02 mbox dovecot: lmtp(25601): Connect from local
> >> Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia):
> >> session=, Error: Index
> >> /var/mail/powiadomienia/dovecot.index: Lost log for seq=1009 offset=40:
> >> Missing middle file seq=1009 (between 1009..4294967295)
> >> Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia):
> >> session=, Warning: fscking index file
> >> /var/mail/powiadomienia/dovecot.index Jul 14 09:52:02 mbox dovecot:
> >> lmtp(powiadomienia): session=, Error: Fixed
> >> index file /var/mail/powiadomienia/dovecot.index: log_file_seq 1009 ->
> >> 1011 Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia):
> >> session=, Panic: file
> >> mail-transaction-log-file.c: line 104 (mail_transaction_log_file_free):
> >> assertion failed: (!file->locked) Jul 14 09:52:02 mbox dovecot:
> >> lmtp(powiadomienia): session=, Error: Raw
> >> backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x8d7d2)
> >> [0x7feb89fc97d2] -> /usr/lib64/dovecot/libdovecot.so.0(+0x8d8bd)
> >> [0x7feb89fc98bd] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0)
> >> [0x7feb89f67e31] ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_transaction_log_file_fr
> >> ee+0x160) [0x7feb8a331fa0] -> /usr/lib64/dovecot/libdovecot-
> >> storage.so.0(mail_transaction_logs_clean+0x4d) [0x7feb8a3360ed] ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_transaction_log_close+0
> >> x30) [0x7feb8a336230] -> /usr/lib64/dovecot/libdovecot-
> >> storage.so.0(mail_transaction_log_move_to_memory+0xd5) [0x7feb8a3363e5]
> >> ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_move_to_memory+0x
> >> a0) [0x7feb8a330440] -> /usr/lib64/dovecot/libdovecot-
> >> storage.so.0(mail_index_write+0x183) [0x7feb8a32e9d3] ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_fsck+0xc1f)
> >> [0x7feb8a3186ff] ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x49b)
> >> [0x7feb8a322eab] ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x71)
> >> [0x7feb8a31a231] ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xe0fed) [0x7feb8a32ffed]
> >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xe15f3)
> >> [0x7feb8a3305f3] ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_open+0x78)
> >> [0x7feb8a3306d8] ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_mailbox_open+0
> >> x92) [0x7feb8a309202] ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x6c0e2) [0x7feb8a2bb0e2]
> >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x6c1c8)
> >> [0x7feb8a2bb1c8] ->
> >> /usr/lib64/dovecot/plugins/lib20_zlib_plugin.so(+0x2fdc)
> >> [0x7feb85697fdc] ->
> >> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x450c6) [0x7feb8a2940c6]
> >> -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_open+0x20)
> >> [0x7feb8a294240] ->
> >> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_save_open+0xad)
> >> [0x7feb8a58d1ad] ->
> >> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_save+0xbb)
> >> [0x7feb8a58d48b] ->
> >> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver+0x123)
> >> [0x7feb8a58d9e3] -> dovecot/lmtp [DATA powiadomienia]() [0x406bc8] ->
> >> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x4c)
> >> [0x7feb89fdd67c] ->
> >> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101)
> >> [0x7feb89fdeb01] ->
> >> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x25)
> >> [0x7feb89fdd705]
> >> Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia):
> >> session=, Fatal: master: service(lmtp): child
> >> 25601 killed with signal 6 (core dumps disabled)
> > 
> > Hi!
> > 
> > Are you still able to reproduce this? Any hope for backtrace with gdb?
> > 
> > gdb /path/to/binary /path/to/core
> > bt full
> > 
> > Aki
> 
> Ping

Sorry, I deleted index for that login and things started to work again, so 
have no way to reproduce anymore.

Also no core dump for that issue.

When it happens again I'll check backtrace.

> Aki

-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

Re: Errors with count:User quota and NFS

2016-11-01 Thread Tom Sommer 

On 2016-10-31 22:04, Timo Sirainen wrote:

Oct 31 10:52:37 imap(x...@.xx): Warning: Locking transaction log 
file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 
seconds (syncing)
Oct 31 10:52:37 imap(x...@xxx.xx): Warning: Locking transaction log 
file /mnt/nfs/xxx.xx/xxx/indexes/dovecot.list.index.log took 31 
seconds (syncing)


This just means something is being slow. Not necessarily a problem.
Although it could also indicate a deadlock. Is this Maildir? Did you
say you were using lock_method=dotlock?


I removed dotlock some time ago (using director) and switched to:

lock_method = fcntl
mail_fsync = always

With "count" as quota backend I get a lot of these errors on the 
director:


imap-login: Error: proxy(x...@.xxx): Login for xxx.xxx.xxx.xxx:143 
timed out in state=2 (after 30 secs, local=x:58478): 
user=, method=CRAM-MD5, rip=, lip=x, TLS, 
session=


on the server:

imap(x...@.xxx): Warning: Locking transaction log file 
/mnt/nfs/.dk/x/indexes/.INBOX/dovecot.index.log took 32 seconds 
(appending)

Re: Server migration

2016-11-01 Thread Sami Ketola 

> On 31 Oct 2016, at 13.11, Tanstaafl  wrote:
> 
> On 10/30/2016 5:32 AM, Sami Ketola  wrote:
>> On 28 Oct 2016, at 16.54, Tanstaafl  wrote:
>>> Oh... I thought the --useuid option eliminated this problem?
>>> 
>>> https://imapsync.lamiral.info/FAQ.d/FAQ.Duplicates.txt
> 
>> It does not. There is no option at IMAP level to set the UID.
>> 
>> In this case —useuid seems to keep track on source:uid -> dest:uid
>> pairs on multiple syncs and uses uid numbers to avoid syncing mails
>> as duplicates instead of using headers to do that.
> 
> Ok, interesting. So... how does dsync do it? Or would it only work
> between two dovecot servers?
> 
> I'm interested in migrating from other servers (Office 365 in one case).

Dsync does not use IMAP protocol to store the mails to storage but instead uses 
the 
dovecot storage API to do that. Internally we can set what ever properties we 
want to
including IMAP UIDs and POP3 UIDLs. 

Migrating from legacy system should then be done by pulling the mails from the
legacy platform by using the imapc connector and storing them by using the 
internal apis.

We can also store mails to imapc: location but in that case there is many 
properties that
will be lost due to limitations of the IMAP protocol.

Sami

Re: Panic: file mail-transaction-log-file.c: line 104 (mail_transaction_log_file_free): assertion failed: (!file->locked)

2016-11-01 Thread Aki Tuomi 


On 25.08.2016 10:29, Aki Tuomi wrote:
>
> On 14.07.2016 10:56, Arkadiusz Miśkiewicz wrote:
>> 2.2.25 (also happens on 2.2.24). Happens every time I try to make deliver
>> and only for this user:
>>
>> Jul 14 09:52:02 mbox dovecot: lmtp(25601): Connect from local
>> Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia): 
>> session=, Error: Index 
>> /var/mail/powiadomienia/dovecot.index: Lost log for seq=1009 offset=40: 
>> Missing middle file seq=1009 (between 
>> 1009..4294967295)
>> Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia): 
>> session=, Warning: fscking index file 
>> /var/mail/powiadomienia/dovecot.index
>> Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia): 
>> session=, Error: Fixed index file 
>> /var/mail/powiadomienia/dovecot.index: log_file_seq 1009 -> 1011
>> Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia): 
>> session=, Panic: file mail-transaction-log-file.c: 
>> line 104 (mail_transaction_log_file_free): assertion failed: (!file->locked)
>> Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia): 
>> session=, Error: Raw backtrace: 
>> /usr/lib64/dovecot/libdovecot.so.0(+0x8d7d2) [0x7feb89fc97d2] -> 
>> /usr/lib64/dovecot/libdovecot.so.0(+0x8d8bd) 
>> [0x7feb89fc98bd] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) 
>> [0x7feb89f67e31] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_transaction_log_file_free+0x160)
>>  [0x7feb8a331fa0] -> /usr/lib64/dovecot/libdovecot-
>> storage.so.0(mail_transaction_logs_clean+0x4d) [0x7feb8a3360ed] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_transaction_log_close+0x30) 
>> [0x7feb8a336230] -> /usr/lib64/dovecot/libdovecot-
>> storage.so.0(mail_transaction_log_move_to_memory+0xd5) [0x7feb8a3363e5] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_move_to_memory+0xa0) 
>> [0x7feb8a330440] -> /usr/lib64/dovecot/libdovecot-
>> storage.so.0(mail_index_write+0x183) [0x7feb8a32e9d3] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_fsck+0xc1f) 
>> [0x7feb8a3186ff] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x49b) 
>> [0x7feb8a322eab] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x71) 
>> [0x7feb8a31a231] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xe0fed) 
>> [0x7feb8a32ffed] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xe15f3) 
>> [0x7feb8a3305f3] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_open+0x78) 
>> [0x7feb8a3306d8] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_mailbox_open+0x92) 
>> [0x7feb8a309202] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x6c0e2) [0x7feb8a2bb0e2] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x6c1c8) [0x7feb8a2bb1c8] -> 
>> /usr/lib64/dovecot/plugins/lib20_zlib_plugin.so(+0x2fdc) [0x7feb85697fdc] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x450c6) [0x7feb8a2940c6] -> 
>> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_open+0x20) 
>> [0x7feb8a294240] -> 
>> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_save_open+0xad) 
>> [0x7feb8a58d1ad] -> 
>> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_save+0xbb) 
>> [0x7feb8a58d48b] -> 
>> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver+0x123) [0x7feb8a58d9e3] 
>> -> dovecot/lmtp [DATA powiadomienia]() [0x406bc8] 
>> -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7feb89fdd67c] 
>> -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) 
>> [0x7feb89fdeb01] -> 
>> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) 
>> [0x7feb89fdd705]
>> Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia): 
>> session=, Fatal: master: service(lmtp): child 25601 
>> killed with signal 6 (core dumps disabled)
>>
>>
> Hi!
>
> Are you still able to reproduce this? Any hope for backtrace with gdb?
>
> gdb /path/to/binary /path/to/core
> bt full
>
> Aki

Ping

Aki