On 22.12.15 2:06, Stephan Bosch wrote:
I am quite confident that this fixes it:
http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/37ddc42c007c
Regards,
Stephan.
Yes, that change fixed the issue. Thanks!
Op 12/16/2015 om 11:00 AM schreef Alexander Moisseev:
> On 16.12.15 12:32, Stephan Bosch wrote:
>>
>> That means that LTMP performed that delivery. That would normally only
>> happen when an error occurs.
>>
> No errors. All mail is delivering as expected.
>
>> Do you see anything strange in the us
Op 16-12-2015 om 11:00 schreef Alexander Moisseev:
What is your configuration?
Attached.
I can't make much sense of it yet. It probably relates to this change:
http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/d23225e408af
and the fact that you use a sieve_after script.
So, what do you
On 16.12.15 12:32, Stephan Bosch wrote:
That means that LTMP performed that delivery. That would normally only
happen when an error occurs.
No errors. All mail is delivering as expected.
Do you see anything strange in the user log? Does system log show
anything more when mail_debug=yes is ac
Op 12/16/2015 om 10:32 AM schreef Stephan Bosch:
> Op 12/16/2015 om 8:31 AM schreef Alexander Moisseev:
>> Pigeonhole 0.4.10 doesn't log msgid for some messages.
>>
>> Dec 16 09:57:57 mx dovecot: lmtp(us...@example.com):
>> EbLlL2gLcVYCBgEAPZa6/Q: sieve:
>> msgid=<20151216065756.be1df1f...@cp.bitri
Op 12/16/2015 om 8:31 AM schreef Alexander Moisseev:
> Pigeonhole 0.4.10 doesn't log msgid for some messages.
>
> Dec 16 09:57:57 mx dovecot: lmtp(us...@example.com):
> EbLlL2gLcVYCBgEAPZa6/Q: sieve:
> msgid=<20151216065756.be1df1f...@cp.bitrix24.com>: forwarded to
>
> Dec 16 09:57:57 mx dovecot:
Pigeonhole 0.4.10 doesn't log msgid for some messages.
Dec 16 09:57:57 mx dovecot: lmtp(us...@example.com): EbLlL2gLcVYCBgEAPZa6/Q: sieve:
msgid=<20151216065756.be1df1f...@cp.bitrix24.com>: forwarded to
Dec 16 09:57:57 mx dovecot: lmtp(us...@example.com): EbLlL2gLcVYCBgEAPZa6/Q:
sieve: stored
