dovecot - Jun 2017 - 2nd try: Thunderbird "Empty Trash" causes inconsistent IMAP session state?

Yes, that would help too.

Aki


On 05.06.2017 14:35, awl1 wrote:
> Hello Aki,
>
> sorry, but I am still a newbie to Dovecot:
>
> Hmm - I don't seem to have IMAP session IDs in every line of my
> dovecot-info.log. that could be used to extract IMAP session-related
> info.
>
> I assume that I have to set up logging in a specific way to add and
> then find the IMAP session ID in my logs. Could you please point me to
> the docs about how to configure this for the future?
>
> What I can offer now from my old logs is to provide log file excerpts
> from some minutes/seconds before the "Empty Trash" action caused
the
> "inconsistent IMPA state" message until shortly after - would
that
> help as well!?
>
> Best regards & apologies
> Andreas
>
>
> Am 05.06.2017 um 13:13 schrieb Aki Tuomi:
>> Can you provide full logs for the imap session? Basically you can do
>> grep session-id logfile.
>>
>> Aki

Hello again,

here you are (log excerpt from May 29 00:06:02 until May 29 01:17:49):

May 29 00:12:05 imap(xxx at xxx.org): Info: IMAP session state is 
inconsistent, please relogin. in=1369 out=222662
May 29 00:12:05 imap(xxx at xxx.org): Info: IMAP session state is 
inconsistent, please relogin. in=204 out=1504
May 29 00:40:29 imap(xxx at xxx.org): Info: IMAP session state is 
inconsistent, please relogin. in=1213 out=6414
May 29 00:40:30 imap(xxx at xxx.org): Info: IMAP session state is 
inconsistent, please relogin. in=227 out=1430


I'd still be interested anyway in what I'd have t do in order to add the
session ID to my future log files. Is this documented anywhere?

https://wiki.dovecot.org/Variables does not help enough with regards to 
how to apply it to logfile settings in dovecot.conf... :-(


Thanks again & best regards
Andreas


Am 05.06.2017 um 13:50 schrieb Aki Tuomi:
> Yes, that would help too.
>
> Aki
>
>
> On 05.06.2017 14:35, awl1 wrote:
>> Hello Aki,
>>
>> sorry, but I am still a newbie to Dovecot:
>>
>> Hmm - I don't seem to have IMAP session IDs in every line of my
>> dovecot-info.log. that could be used to extract IMAP session-related
>> info.
>>
>> I assume that I have to set up logging in a specific way to add and
>> then find the IMAP session ID in my logs. Could you please point me to
>> the docs about how to configure this for the future?
>>
>> What I can offer now from my old logs is to provide log file excerpts
>> from some minutes/seconds before the "Empty Trash" action
caused the
>> "inconsistent IMPA state" message until shortly after - would
that
>> help as well!?
>>
>> Best regards & apologies
>> Andreas
>>
>>
>> Am 05.06.2017 um 13:13 schrieb Aki Tuomi:
>>> Can you provide full logs for the imap session? Basically you can
do
>>> grep session-id logfile.
>>>
>>> Aki

-------------- next part --------------
A non-text attachment was scrubbed...
Name: dovecot-info.log.tar.xz
Type: application/x-xz
Size: 14552 bytes
Desc: not available
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20170605/3a7d3910/attachment-0001.xz>

Am 05.06.2017 um 14:13 schrieb awl1:
> Hello again,
> 
> here you are (log excerpt from May 29 00:06:02 until May 29 01:17:49):
> 
> May 29 00:12:05 imap(xxx at xxx.org): Info: IMAP session state is 
> inconsistent, please relogin. in=1369 out=222662
> May 29 00:12:05 imap(xxx at xxx.org): Info: IMAP session state is 
> inconsistent, please relogin. in=204 out=1504
> May 29 00:40:29 imap(xxx at xxx.org): Info: IMAP session state is 
> inconsistent, please relogin. in=1213 out=6414
> May 29 00:40:30 imap(xxx at xxx.org): Info: IMAP session state is 
> inconsistent, please relogin. in=227 out=1430
> 
> 
> I'd still be interested anyway in what I'd have t do in order to
add the
> session ID to my future log files. Is this documented anywhere?
> 
> https://wiki.dovecot.org/Variables does not help enough with regards to 
> how to apply it to logfile settings in dovecot.conf... :-(
Something like this should log the session.

/etc/dovecot/conf.d/10-logging.conf:
   mail_log_prefix = "%s(%u,%{session}): "

-- 
Alex JOST

That log didn't do much help, can you try enabling mail_debug=yes for a
moment and see if it gives any more insight?

Aki


On 05.06.2017 15:13, awl1 wrote:
> Hello again,
>
> here you are (log excerpt from May 29 00:06:02 until May 29 01:17:49):
>
> May 29 00:12:05 imap(xxx at xxx.org): Info: IMAP session state is
> inconsistent, please relogin. in=1369 out=222662
> May 29 00:12:05 imap(xxx at xxx.org): Info: IMAP session state is
> inconsistent, please relogin. in=204 out=1504
> May 29 00:40:29 imap(xxx at xxx.org): Info: IMAP session state is
> inconsistent, please relogin. in=1213 out=6414
> May 29 00:40:30 imap(xxx at xxx.org): Info: IMAP session state is
> inconsistent, please relogin. in=227 out=1430
>
>
> I'd still be interested anyway in what I'd have t do in order to
add
> the session ID to my future log files. Is this documented anywhere?
>
> https://wiki.dovecot.org/Variables does not help enough with regards
> to how to apply it to logfile settings in dovecot.conf... :-(
>
>
> Thanks again & best regards
> Andreas
>
>
> Am 05.06.2017 um 13:50 schrieb Aki Tuomi:
>> Yes, that would help too.
>>
>> Aki
>>
>>
>> On 05.06.2017 14:35, awl1 wrote:
>>> Hello Aki,
>>>
>>> sorry, but I am still a newbie to Dovecot:
>>>
>>> Hmm - I don't seem to have IMAP session IDs in every line of my
>>> dovecot-info.log. that could be used to extract IMAP
session-related
>>> info.
>>>
>>> I assume that I have to set up logging in a specific way to add and
>>> then find the IMAP session ID in my logs. Could you please point me
to
>>> the docs about how to configure this for the future?
>>>
>>> What I can offer now from my old logs is to provide log file
excerpts
>>> from some minutes/seconds before the "Empty Trash" action
caused the
>>> "inconsistent IMPA state" message until shortly after -
would that
>>> help as well!?
>>>
>>> Best regards & apologies
>>> Andreas
>>>
>>>
>>> Am 05.06.2017 um 13:13 schrieb Aki Tuomi:
>>>> Can you provide full logs for the imap session? Basically you
can do
>>>> grep session-id logfile.
>>>>
>>>> Aki
>
>