Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Piper Andreas]

Hi Jake,

thanks for fixing this. I have installed now the newly built package on
my production system and will report, if any more core dumps occur.

Regards,
Andreas

Am 31.08.2016 um 20:19 schrieb Jake Goerzen:
> Hi Andreas & Timo,
> 
> 
>   I've found out what is causing the incorrect hash in the built
> packages.  Our build system use here at OpenCSW has internal git
> patching capability.  I disabled it and rebuild again.  This time all
> architectures and memory model's are reporting the correct git-commit
> hash 7be1766.  Thank you Andreas for noticing and reporting this.
> 
> 
> regards,
> 
> Jake
> 
> 
> On 08/31/2016 06:17 AM, Piper Andreas wrote:
>> Hello Timo,
>>
>> from the maintainer of the OpenCSW package I got the below answer.
>>
>> As the newly build package yields another different commit hash (which I
>> cannot find on GitHub too), I would ask, if you are sure that the commit
>> hash-output in 'doveconf -n' is generated correctly?
>>
>> The headline of 'doveconf -n' with the newly build package is
>> # 2.2.25 (68082dc): /etc/opt/csw/dovecot/dovecot.conf
>>
>> Many thanks for your help,
>> Andreas
>>
>>  Weitergeleitete Nachricht 
>> Betreff: Re: OpenCSW question about package CSWdovecot
>> Datum: Tue, 30 Aug 2016 08:56:44 -0700
>> Von: jgoerzen 
>> An: pi...@hrz.uni-marburg.de
>>
>> Hello Andreas,
>>
>>
>> The OpenCSW dovecot package was built using the 2.2.25 version
>> release tarball.  No code changes or patches have been applied. I'm not
>> sure what happened.  I will respin new packages and then check to see if
>> the git-commit hash is correct.  When the packages are done building
>> I'll put them in the experimental catalog:
>>
>>
>> http://buildfarm.opencsw.org/experimental.html#jgoerzen
>>
>>
>> Thanks,
>>
>> Jake
>>
>>
>>
>>
>>
>>
>>
>> On 08/29/2016 11:59 PM, pi...@hrz.uni-marburg.de wrote:
>>> Hello,
>>>
>>> with your newest dovecot-package 2.2.25,REV=2016.07.01, I sometimes
>>> get core-dumps as documented in my bug-report at the
>>> dovecot-mailing-list:
>>> http://dovecot.org/list/dovecot/2016-August/105321.html
>>> In reaction to my bug-report, Timo Sirainen asks, which git-commit of
>>> the dovecot-sources was used for this package:
>>> http://dovecot.org/list/dovecot/2016-August/105332.html
>>>
>>> Could you shed some light on this?
>>>
>>> Thanks a lot,
>>> Andreas
>>
> 






smime.p7s
Description: S/MIME Cryptographic Signature

Use of obox2 and AWS S3

[Raymond Sellars]

Hi

Has anyone used or is using dovecot obox and S3 storage? I see very little 
chatter or documentation on it.

Interested in how mature it is and technical items such as high availability 
and region replication.

I'm guessing that multiple updates to a S3 mailbox is mitigated via the 
standard dovecot pattern of Director pointing multiple user sessions to a 
single/common dovecot node.

And for disaster recovery - that's out of scope of dovecot and more reliant on 
S3 replication?


Any one running a dovecot solution within AWS in general? Interested in best 
practice for the storage layer. Although NFS is possible its not really 
optimised for elastic cloud type hosting.

Thanks
Raymond

Re: Dsync config help

[Jean-Luc Wasmer]

I was able to workaround the “Error: sync: /var/run/dovecot/auth-userdb: 
Configured passdbs don’t support credentials lookups (to see if user is 
proxied, because doveadm_port is set)” problem: 

=> I simply disabled “doveadm_port” and added the port number at the end of the 
remote URL in “mail_replica”


Replication seems to work although I have regular errors (idk if they are 
related to each other or not).
I’ve attached excerpts from the log files but here are the different errors:


- out of memory errors:
Aug 31 21:37:10 serverA dovecot: replicator: Panic: data stack: Out of memory 
when allocating 268435496 bytes



- timeout errors:

Aug 31 21:36:41 serverA dovecot: dsync-server(user1): Warning: 
replication(user1): Sync failure: Timeout in 2 secs

Aug 31 21:37:09 serverA dovecot: dsync-local(user1): Error: Couldn't lock 
/home/user1/.dovecot-sync.lock: Timed out after 30 seconds

Aug 31 21:38:34 serverA dovecot: imap(user2): Warning: replication(user2): Sync 
failure: Timeout in 2 secs



- permission denied errors:

Aug 31 21:37:14 serverA dovecot: dsync-server(user2): Error: 
net_connect_unix(/var/run/dovecot/replicator-doveadm) failed: Permission denied





I also get errors for user “nobody” with uid 65534. To avoid them I added 
10-mail.conf:first_valid_uid = 2000
10-mail.conf:last_valid_uid = 3000



but I still get some errors, different ones now:


Sep  1 00:13:42 shaun dovecot: doveadm(a.b.c.d,nobody): Error: Mail access for 
users with UID 65534 not permitted (see first_valid_uid in config file, uid 
from userdb lookup).
Sep  1 00:13:42 shaun dovecot: doveadm(a.b.c.d,nobody): Error: dsync-server: 
User init failed
Sep  1 00:14:00 shaun dovecot: doveadm(nobody): Error: sync: Failed to start 
remote dsync-server command: Remote exit_code=75





Jean-Luc



> On Aug 31, 2016, at 12:02 AM, Jean-Luc Wasmer  wrote:
> 
> 
> Hi,
> 
> 
> I'm trying to sync emails between server A and B.
> A has replicator, aggregator and doveadm.
> B only has doveadm for now.
> 
> 
> I'm getting the following error:
> 
> 
> Error: sync: /var/run/dovecot/auth-userdb: Configured passdbs don't 
> support credentials lookups (to see if user is proxied, because 
> doveadm_port is set)
> 
> 
> I'm not sure why I'm getting this error because I authenticate using PAM 
> and when I run
> I do have a "service auth" enabled though... it's used for Postfix SASL 
> to authenticate SMTP.
> 
> 
> I'm running
> 
> 
> # dovecot --version
> 2.2.24 (a82c823)
> 
> 
> 
> 
> 
> Cheers,
> Jean-Luc
> 
> 
> 
> 
> 
> PS: "replication_sync_timeout = 2s" doesn't work, I had to drop the 's'
> 
> 
> 
> 
> 
> On 2016-08-28 17:43, Jean-Luc Wasmer wrote:
>> 
>> 
>> Hi,
>> 
>> 
>> 
>> 
>> 
>> I’m having a hard time with the http://wiki2.dovecot.org/Replication
>>  page.
>> 
>> 
>> 
>> 
>> 
>> - for a master-master setup, does the configuration need to be
>> mirrored on both masters?
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> - after aggregating unrelated sections of the wiki page, there seems
>> to be 3 different values for “mail_replica":
>> - "remote”: for SSH
>> - “remoteprefix": for SSH wrapper
>> - “tcp”: for TCP connection using the Doveadm protocol
>> Is this correct?
>> 
>> 
>> 
>> 
>> 
>> - what’s the purpose of the replicator VS aggregator VS doveadm 
>> services?
>> Who talks to who? Where can I find documentation about their
>> configuration (i.e. not examples)
>> 
>> 
>> 
>> 
>> 
>> - most examples are for a single vmail user setup… what should be done
>> when using system accounts?
>> 
>> 
>> 
>> 
>> 
>> Thanks,
>> Jean-Luc
>> 
Aug 31 21:36:41 serverA dovecot: dsync-server(user1): Warning: 
replication(user1): Sync failure: Timeout in 2 secs
Aug 31 21:37:09 serverA dovecot: dsync-local(user1): Error: Couldn't lock 
/home/user1/.dovecot-sync.lock: Timed out after 30 seconds
Aug 31 21:37:10 serverA dovecot: replicator: Panic: data stack: Out of memory 
when allocating 268435496 bytes
Aug 31 21:37:10 serverA dovecot: replicator: Fatal: master: 
service(replicator): child 76676 killed with signal 6 (core not dumped - set 
service replicator { drop_priv_before_exec=yes })
Aug 31 21:37:14 serverA dovecot: dsync-server(user2): Error: 
net_connect_unix(/var/run/dovecot/replicator-doveadm) failed: Permission denied
Aug 31 21:37:18 serverA dovecot: dsync-server(user1): Error: 
net_connect_unix(/var/run/dovecot/replicator-doveadm) failed: Permission denied
Aug 31 21:38:34 serverA dovecot: imap(user2): Warning: replication(user2): Sync 
failure: Timeout in 2 secs
Aug 31 21:38:46 serverA dovecot: replicator: Panic: data stack: Out of memory 
when allocating 268435496 bytes
Aug 31 21:38:46 serverA dovecot: replicator: Fatal: master: 
service(replicator): child 76734 killed with signal 6 (core not dumped - set 
service replicator { drop_priv_before_exec=yes })
Aug 31 21:38:58 serverA dovecot: dsync-server(user2): Error: 
net_connect_unix(/var/run/dovecot/replicator-doveadm) failed: Permission denied
Aug 31 21:39:21 serverA 

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Jake Goerzen]

Hi Andreas & Timo,


  I've found out what is causing the incorrect hash in the built 
packages.  Our build system use here at OpenCSW has internal git 
patching capability.  I disabled it and rebuild again.  This time all 
architectures and memory model's are reporting the correct git-commit 
hash 7be1766.  Thank you Andreas for noticing and reporting this.



regards,

Jake


On 08/31/2016 06:17 AM, Piper Andreas wrote:

Hello Timo,

from the maintainer of the OpenCSW package I got the below answer.

As the newly build package yields another different commit hash (which I
cannot find on GitHub too), I would ask, if you are sure that the commit
hash-output in 'doveconf -n' is generated correctly?

The headline of 'doveconf -n' with the newly build package is
# 2.2.25 (68082dc): /etc/opt/csw/dovecot/dovecot.conf

Many thanks for your help,
Andreas

 Weitergeleitete Nachricht 
Betreff: Re: OpenCSW question about package CSWdovecot
Datum: Tue, 30 Aug 2016 08:56:44 -0700
Von: jgoerzen 
An: pi...@hrz.uni-marburg.de

Hello Andreas,


The OpenCSW dovecot package was built using the 2.2.25 version
release tarball.  No code changes or patches have been applied. I'm not
sure what happened.  I will respin new packages and then check to see if
the git-commit hash is correct.  When the packages are done building
I'll put them in the experimental catalog:


http://buildfarm.opencsw.org/experimental.html#jgoerzen


Thanks,

Jake







On 08/29/2016 11:59 PM, pi...@hrz.uni-marburg.de wrote:

Hello,

with your newest dovecot-package 2.2.25,REV=2016.07.01, I sometimes get 
core-dumps as documented in my bug-report at the dovecot-mailing-list: 
http://dovecot.org/list/dovecot/2016-August/105321.html
In reaction to my bug-report, Timo Sirainen asks, which git-commit of the 
dovecot-sources was used for this package: 
http://dovecot.org/list/dovecot/2016-August/105332.html

Could you shed some light on this?

Thanks a lot,
Andreas

dovecot and ldap with problem on userdb

[in Gründung]

Hi,
I have setup a new ubuntu on 16.04..
I have already a running system on 14.04 but wanted to migrate.

I get an error when checking user in ldap.

+++
Aug 31 18:14:16 auth: Error: ldap_bind
Aug 31 18:14:16 auth: Error: ldap_simple_bind
Aug 31 18:14:16 auth: Error: ldap_sasl_bind
Aug 31 18:14:16 auth: Error: ldap_send_initial_request
Aug 31 18:14:16 auth: Error: ldap_new_connection 1 1 0
Aug 31 18:14:16 auth: Error: ldap_int_open_connection
Aug 31 18:14:16 auth: Error: ldap_connect_to_host: TCP localhost:389
Aug 31 18:14:16 auth: Error: ldap_new_socket: 20
Aug 31 18:14:16 auth: Error: ldap_prepare_socket: 20
Aug 31 18:14:16 auth: Error: ldap_connect_to_host: Trying ::1 389
Aug 31 18:14:16 auth: Error: ldap_pvt_connect: fd: 20 tm: 5 async: 0
Aug 31 18:14:16 auth: Error: ldap_ndelay_on: 20
Aug 31 18:14:16 auth: Error: attempting to connect:
Aug 31 18:14:16 auth: Error: connect errno: 115
Aug 31 18:14:16 auth: Error: ldap_int_poll: fd: 20 tm: 5
Aug 31 18:14:16 auth: Error: ldap_is_sock_ready: 20
Aug 31 18:14:16 auth: Error: ldap_ndelay_off: 20
Aug 31 18:14:16 auth: Error: ldap_pvt_connect: 0
Aug 31 18:14:16 auth: Error: ldap_open_defconn: successful
Aug 31 18:14:16 auth: Error: ldap_send_server_request
Aug 31 18:14:16 auth: Error: ldap_result ld 0x55b624137680 msgid -1
Aug 31 18:14:16 auth: Error: wait4msg ld 0x55b624137680 msgid -1 (timeout 0
usec)
Aug 31 18:14:16 auth: Error: wait4msg continue ld 0x55b624137680 msgid -1
all 0
Aug 31 18:14:16 auth: Error: ** ld 0x55b624137680 Connections:
Aug 31 18:14:16 auth: Error: * host: localhost  port: 389  (default)
Aug 31 18:14:16 auth: Error:   refcnt: 2  status: Connected
Aug 31 18:14:16 auth: Error:   last used: Wed Aug 31 18:14:16 2016
Aug 31 18:14:16 auth: Error:
Aug 31 18:14:16 auth: Error:
Aug 31 18:14:16 auth: Error: ** ld 0x55b624137680 Outstanding Requests:
Aug 31 18:14:16 auth: Error:  * msgid 1,  origid 1, status InProgress
Aug 31 18:14:16 auth: Error:outstanding referrals 0, parent count 0
Aug 31 18:14:16 auth: Error:   ld 0x55b624137680 request count 1 (abandoned
0)
Aug 31 18:14:16 auth: Error: ** ld 0x55b624137680 Response Queue:
Aug 31 18:14:16 auth: Error:Empty
Aug 31 18:14:16 auth: Error:   ld 0x55b624137680 response count 0
Aug 31 18:14:16 auth: Error: ldap_chkResponseList ld 0x55b624137680 msgid -1
all 0
Aug 31 18:14:16 auth: Error: ldap_chkResponseList returns ld 0x55b624137680
NULL
Aug 31 18:14:16 auth: Error: ldap_int_select
Aug 31 18:14:16 auth: Error: read1msg: ld 0x55b624137680 msgid -1 all 0
Aug 31 18:14:16 auth: Error: read1msg: ld 0x55b624137680 msgid 1 message
type bind
Aug 31 18:14:16 auth: Error: read1msg: ld 0x55b624137680 0 new referrals
Aug 31 18:14:16 auth: Error: read1msg:  mark request completed, ld
0x55b624137680 msgid 1
Aug 31 18:14:16 auth: Error: request done: ld 0x55b624137680 msgid 1
Aug 31 18:14:16 auth: Error: res_errno: 0, res_error: <>, res_matched: <>
Aug 31 18:14:16 auth: Error: ldap_free_request (origid 1, msgid 1)
Aug 31 18:14:16 auth: Error: ldap_parse_result
Aug 31 18:14:16 auth: Error: ldap_search
Aug 31 18:14:16 auth: Error: put_filter:
"(&(objectClass=posixAccount)(mail=info))"
Aug 31 18:14:16 auth: Error: put_filter: AND
Aug 31 18:14:16 auth: Error: put_filter_list
"(objectClass=posixAccount)(mail=info)"
Aug 31 18:14:16 auth: Error: put_filter: "(objectClass=posixAccount)"
Aug 31 18:14:16 auth: Error: put_filter: simple
Aug 31 18:14:16 auth: Error: put_simple_filter: "objectClass=posixAccount"
Aug 31 18:14:16 auth: Error: put_filter: "(mail=info)"
Aug 31 18:14:16 auth: Error: put_filter: simple
Aug 31 18:14:16 auth: Error: put_simple_filter: "mail=info"
Aug 31 18:14:16 auth: Error: ldap_send_initial_request
Aug 31 18:14:16 auth: Error: ldap_send_server_request
Aug 31 18:14:16 auth: Error: ldap_msgfree
Aug 31 18:14:16 auth: Error: ldap_result ld 0x55b624137680 msgid -1
Aug 31 18:14:16 auth: Error: wait4msg ld 0x55b624137680 msgid -1 (timeout 0
usec)
Aug 31 18:14:16 auth: Error: wait4msg continue ld 0x55b624137680 msgid -1
all 0
Aug 31 18:14:16 auth: Error: ** ld 0x55b624137680 Connections:
Aug 31 18:14:16 auth: Error: * host: localhost  port: 389  (default)
Aug 31 18:14:16 auth: Error:   refcnt: 2  status: Connected
Aug 31 18:14:16 auth: Error:   last used: Wed Aug 31 18:14:16 2016
Aug 31 18:14:16 auth: Error:
Aug 31 18:14:16 auth: Error:
Aug 31 18:14:16 auth: Error: ** ld 0x55b624137680 Outstanding Requests:
Aug 31 18:14:16 auth: Error:  * msgid 2,  origid 2, status InProgress
Aug 31 18:14:16 auth: Error:outstanding referrals 0, parent count 0
Aug 31 18:14:16 auth: Error:   ld 0x55b624137680 request count 1 (abandoned
0)
Aug 31 18:14:16 auth: Error: ** ld 0x55b624137680 Response Queue:
Aug 31 18:14:16 auth: Error:Empty
Aug 31 18:14:16 auth: Error:   ld 0x55b624137680 response count 0
Aug 31 18:14:16 auth: Error: ldap_chkResponseList ld 0x55b624137680 msgid -1
all 0
Aug 31 18:14:16 auth: Error: ldap_chkResponseList returns ld 0x55b624137680
NULL
Aug 31 18:14:16 auth: Error: ldap_int_select

RE: autoexpunge clarification

[Michael Fox]

Thanks Philon,

I did read the extra bullets, as indicated in my email below.  But your "When 
the user quits and thus closes his mailbox/connection" is more clear than 
"after the client is already disconnected", since the latter is really anytime, 
rather than at the time they quit.

I can guess that the bulletin about LMTP similarly means at the end of each 
time LMTP delivers mail to the mailbox.

Assuming that is true, then the problem I see with autoexpunge is that it 
doesn't address the case of a user that has not logged in nor received mail in 
that mailbox for the specified time.  Those messages would apparently stay 
forever.  Correct?

And, if that's true, then the cron job seems like the only way to expunge all 
old messages.  Correct?

Thanks,
Michael


 

> -Original Message-
> From: dovecot [mailto:dovecot-boun...@dovecot.org] On Behalf Of Philon
> Sent: Wednesday, August 31, 2016 12:41 AM
> To: Michael Fox 
> Cc: Dovecot Mailing List 
> Subject: Re: autoexpunge clarification
> 
> Hi Micheal,
> 
> the article is fine if you continue reading it to the next bullet points
> about IMAP, POP3 and LMTP. In short words…
> 
> When the user quits and thus closes his mailbox/connection, Dovecot
> quickly looks through the folders to clean up mails which are older then
> configured days.
> 
> In the past there was a cron job which could do this every n hours, days,
> … but this setting does this automatically. Still I prefer using cron
> which gives me more control over when this lookup happens.
> 
> User deinitialization is simply developer „slang" for user closes
> connection/quits his program.
> 
> 
> Philon
> 
> > Am 30.08.2016 um 14:41 schrieb Michael Fox :
> >
> > I'm trying to understand autoexpunge, but the documentation is just not
> > clear.  Hopefully, someone can clear up a few questions.
> >
> >
> >
> > http://wiki.dovecot.org/MailboxSettings says the following:
> >
> >
> >
> > autoexpunge=: (v2.2.20+) Automatically at user deinitialization
> > expunge all mails in this mailbox whose saved-timestamp is older than
> 
> > (e.g. autoexpunge=30d). This removes the need for expire plugin
> >   if you don't care that the
> > expunging may not always happen in time.
> >
> >
> >
> > What does "at user deinitialization" mean?
> >
> >
> >
> > What does "if you don't care that the expunging may not always happen in
> > time" mean?
> >
> >
> >
> > I read the sub-bullets but they just aren't clear.  When exactly does
> > autoexpunge occur?
> >
> >
> >
> > Thanks,
> >
> > Michael
> >
> >

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

[Piper Andreas]

Hello Timo,

from the maintainer of the OpenCSW package I got the below answer.

As the newly build package yields another different commit hash (which I
cannot find on GitHub too), I would ask, if you are sure that the commit
hash-output in 'doveconf -n' is generated correctly?

The headline of 'doveconf -n' with the newly build package is
# 2.2.25 (68082dc): /etc/opt/csw/dovecot/dovecot.conf

Many thanks for your help,
Andreas

 Weitergeleitete Nachricht 
Betreff: Re: OpenCSW question about package CSWdovecot
Datum: Tue, 30 Aug 2016 08:56:44 -0700
Von: jgoerzen 
An: pi...@hrz.uni-marburg.de

Hello Andreas,


   The OpenCSW dovecot package was built using the 2.2.25 version
release tarball.  No code changes or patches have been applied. I'm not
sure what happened.  I will respin new packages and then check to see if
the git-commit hash is correct.  When the packages are done building
I'll put them in the experimental catalog:


http://buildfarm.opencsw.org/experimental.html#jgoerzen


Thanks,

Jake







On 08/29/2016 11:59 PM, pi...@hrz.uni-marburg.de wrote:
> Hello,
>
> with your newest dovecot-package 2.2.25,REV=2016.07.01, I sometimes get 
> core-dumps as documented in my bug-report at the dovecot-mailing-list: 
> http://dovecot.org/list/dovecot/2016-August/105321.html
> In reaction to my bug-report, Timo Sirainen asks, which git-commit of the 
> dovecot-sources was used for this package: 
> http://dovecot.org/list/dovecot/2016-August/105332.html
>
> Could you shed some light on this?
>
> Thanks a lot,
> Andreas




smime.p7s
Description: S/MIME Cryptographic Signature

Re: autoexpunge clarification

[Philon]

Hi Micheal,

the article is fine if you continue reading it to the next bullet points about 
IMAP, POP3 and LMTP. In short words…

When the user quits and thus closes his mailbox/connection, Dovecot quickly 
looks through the folders to clean up mails which are older then configured 
days.

In the past there was a cron job which could do this every n hours, days, … but 
this setting does this automatically. Still I prefer using cron which gives me 
more control over when this lookup happens.

User deinitialization is simply developer „slang" for user closes 
connection/quits his program.


Philon

> Am 30.08.2016 um 14:41 schrieb Michael Fox :
> 
> I'm trying to understand autoexpunge, but the documentation is just not
> clear.  Hopefully, someone can clear up a few questions.
> 
> 
> 
> http://wiki.dovecot.org/MailboxSettings says the following:
> 
> 
> 
> autoexpunge=: (v2.2.20+) Automatically at user deinitialization
> expunge all mails in this mailbox whose saved-timestamp is older than 
> (e.g. autoexpunge=30d). This removes the need for expire plugin
>   if you don't care that the
> expunging may not always happen in time.
> 
> 
> 
> What does "at user deinitialization" mean?
> 
> 
> 
> What does "if you don't care that the expunging may not always happen in
> time" mean?
> 
> 
> 
> I read the sub-bullets but they just aren't clear.  When exactly does
> autoexpunge occur?
> 
> 
> 
> Thanks,
> 
> Michael
> 
> 

Re: ACL List uses wrong namespace for permissions

[Aki Tuomi]

On 26.04.2016 18:03, Harald Leithner wrote:
> Hi,
>
> I'm using dovecot 2.2.devel (11c704a) with lazyexpunge and shared
> Mailboxes, this seams to work since the latest patch.
>
> There is only one problem creating the correct dovecot-acl-list, if I
> login as the normal user that has set permissions for another user
> everything is ok.
>
> If I login with the same user but with a modified roundcube that uses
> the #EXPUNGED Namespace as root, dovecot overrides the correct
> dovecot-acl-list with an empty version.
>
> I think this is the most interesting part of the log:
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: fs: root=/srv/storage1/vmail/company/628, index=, indexpvt=,
> control=, inbox=, alt=
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl: initializing backend with data: vfile
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl: acl username = u...@company.at
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl: owner = 1
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl vfile: Global ACLs disabled
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: Namespace : type=private, prefix=#EXPUNGED/, sep=, inbox=no,
> hidden=yes, list=no, subscriptions=no
> location=mdbox:/srv/storage1/vmail/company/628:MAILBOXDIR=expunged
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: fs: root=/srv/storage1/vmail/company/628, index=, indexpvt=,
> control=, inbox=, alt=
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl: initializing backend with data: vfile
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl: acl username = u...@company.at
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl: owner = 1
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl vfile: Global ACLs disabled
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: Namespace : type=shared, prefix=#Users/%u/, sep=/, inbox=no,
> hidden=no, list=children, subscriptions=yes
> location=mdbox:/srv/storage1/vmail%h
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=,
> inbox=, alt=
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl vfile: file
> /srv/storage1/vmail/company/628/mailboxes/dovecot-acl not found
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: Namespace : Using permissions from
> /srv/storage1/vmail/company/628: mode=0700 gid=default
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl vfile: file
> /srv/storage1/vmail/company/628/mailboxes/Drafts/dbox-Mails/dovecot-acl
> not found
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl vfile: file
> /srv/storage1/vmail/company/628/expunged/dovecot-acl not found
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: Namespace #EXPUNGED/: Using permissions from
> /srv/storage1/vmail/company/628: mode=0700 gid=default
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl vfile: file
> /srv/storage1/vmail/company/628/expunged/INBOX/dbox-Mails/dovecot-acl
> not found
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl vfile: file
> /srv/storage1/vmail/company/628/expunged/INBOX/test/dbox-Mails/dovecot-acl
> not found
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Debug: acl vfile: reading file
> /srv/storage1/vmail/company/628/mailboxes/INBOX/dbox-Mails/dovecot-acl
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Logged out in=178 out=870
> 2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
> Logged out in=315 out=27172
>
>
> regards,
>
>
>
>

Hi!


2016-04-26T16:49:26+02:00 mailstore1 dovecot: imap(u...@company.at):
Debug: acl vfile: reading file
/srv/storage1/vmail/company/628/mailboxes/INBOX/dbox-Mails/dovecot-acl

Is this file the correct one? I am assuming this log is when your
modified roundcube tries to access it?

Aki

Re: Panic on cleanup

[Aki Tuomi]

On 12.07.2016 22:25, Harald Leithner wrote:
> Hi,
>
> I got a doveadm panic while running purge -A with 2.2.25
>
>
> doveadm(x...@itronic.at): Panic: file mdbox-map.c: line 1359: unreached
> doveadm(x...@itronic.at): Error: Raw backtrace:
> /usr/lib/dovecot/libdovecot.so.0(+0x8dc6e) [0x7f2fe2022c6e] ->
> /usr/lib/dovecot/libdovecot.so.0(+0x8dce8) [0x7f2fe2022ce8] ->
> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f2fe1fc102e] ->
> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_map_append_move+0x1ed)
> [0x7f2fe2301c0d] ->
> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_purge+0xfe3)
> [0x7f2fe2303103] -> doveadm(+0x29458) [0x7f2fe2c7e458] ->
> doveadm(+0x2910f) [0x7f2fe2c7e10f] -> doveadm(+0x29db4)
> [0x7f2fe2c7edb4] ->
> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x278) [0x7f2fe2c7fae8]
> -> doveadm(doveadm_cmd_run_ver2+0x560) [0x7f2fe2c8dfd0] ->
> doveadm(doveadm_cmd_try_run_ver2+0x37) [0x7f2fe2c8e027] ->
> doveadm(main+0x1e4) [0x7f2fe2c6f414] ->
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
> [0x7f2fe1c0bb45] -> doveadm(+0x1a7ee) [0x7f2fe2c6f7ee]
>
> The command was run in a cleanup script that expunge old mails from
> the lazy-plugin.
> 
> #!/bin/sh
>
> # Permanently expunge old Trash
> doveadm expunge -A -d mailbox '#EXPUNGED/*' savedbefore 2w
>
> # Optimize mdbox storage and sis storage
> doveadm purge -A
> 
>
> After rerunning the command it fails again.
>
> stace could be found after config.
>
>
> config:
> # 2.2.devel (6d2fa6b): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.4.devel (3f51b82)
> # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.5
> auth_cache_negative_ttl = 1 secs
> auth_cache_size = 10 M
> auth_cache_ttl = 1 secs
> auth_mechanisms = PLAIN LOGIN DIGEST-MD5 SCRAM-SHA-1 CRAM-MD5 APOP
> auth_verbose = yes
> default_client_limit = 600
> default_vsz_limit = 512 M
> dict {
>   lastlogin = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
>   sqlacl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
>   sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
> }
> disable_plaintext_auth = no
> first_valid_gid = 1001
> first_valid_uid = 1001
> hostname = mailsto...@itronic.at
> imap_hibernate_timeout = 1 mins
> imap_id_log = *
> imap_id_send = *
> imap_idle_notify_interval = 10 mins
> instance_name = mailstore1
> last_valid_gid = 1001
> last_valid_uid = 1001
> lda_original_recipient_header = X-LDA-Original-To
> lmtp_rcpt_check_quota = yes
> login_greeting = ITronic Mail Store
> login_trusted_networks = 172.22.14.0/24
> mail_attachment_dir = /srv/storage1/vmail_sis
> mail_attachment_hash = %{sha512}
> mail_attachment_min_size = 64 k
> mail_cache_min_mail_count = 5
> mail_gid = vmail
> mail_location = mdbox:~/mdbox
> mail_plugins = zlib lazy_expunge stats acl quota
> mail_prefetch_count = 100
> mail_server_admin = mailto:postmas...@itronic.at
> mail_server_comment = ITronic Mail System
> mail_shared_explicit_inbox = yes
> mail_uid = vmail
> mailbox_list_index = yes
> managesieve_notify_capability = mailto
> managesieve_sieve_capability = fileinto reject envelope
> encoded-character vacation subaddress comparator-i;ascii-numeric
> relational regex imap4flags copy include variables body enotify
> environment mailbox date index ihave duplicate mime foreverypart
> extracttext
> mdbox_preallocate_space = yes
> namespace {
>   hidden = yes
>   list = no
>   location = mdbox:~/mdbox:MAILBOXDIR=expunged
>   prefix = "#EXPUNGED/"
>   subscriptions = no
>   type = private
> }
> namespace {
>   list = children
>   location = mdbox:%%h/mdbox
>   prefix = "#Users/%%u/"
>   separator = /
>   subscriptions = yes
>   type = shared
> }
> namespace inbox {
>   hidden = no
>   inbox = yes
>   location =
>   mailbox Archvie {
> special_use = \Archive
>   }
>   mailbox Drafts {
> special_use = \Drafts
>   }
>   mailbox Sent {
> special_use = \Sent
>   }
>   mailbox Spam {
> special_use = \Junk
>   }
>   mailbox Trash {
> special_use = \Trash
>   }
>   prefix =
>   separator = /
>   subscriptions = yes
>   type = private
> }
> passdb {
>   args = /etc/dovecot/dovecot-sql.conf.ext
>   driver = sql
> }
> plugin {
>   acl = vfile
>   acl_shared_dict = proxy::sqlacl
>   last_login_dict = proxy::lastlogin
>   last_login_key = last-login/%u
>   lazy_expunge = "#EXPUNGED/"
>   lazy_expunge_only_last_instance = no
>   quota = dict:User quota::proxy::sqlquota
>   quota_grace = 10%%
>   quota_rule = *:storage=1024M
>   quota_rule2 = "#EXPUNGED:storage=+100M"
>   quota_warning = storage=100%% quota-warning 100 %u
>   quota_warning2 = storage=95%% quota-warning 95 %u
>   quota_warning3 = storage=80%% quota-warning 80 %u
>   recipient_delimiter = +
>   sieve = file:~/sieve;active=~/.dovecot.sieve
>   sieve_global = /etc/dovecot/sieve
>   sieve_max_actions = 64
>   sieve_max_redirects = 8
>   sieve_max_script_size = 2M
>   sieve_quota_max_scripts = 0
>   sieve_quota_max_storage = 64M
>   stats_refresh = 30 secs
>   stats_track_cmds = yes
>   zlib_save = gz
>   zlib_save_level = 6
> }
>