LMTP-Process stays in RCPT TO state

[Pascal Christen]

Hi Stephan

We tried it again last week with the latest dovecot version and still having the same issue. The whole setup works perfectly fine with the latest version of dovecot 2.2

The problem only exists if the quota of the user is full, every other message gets delivered without a problem, and the lmtp process change back to READY state. But in this case, it stays in the "RCPT TO” forever. I’ve talked to ‘cmouse’ today on the IRC and he recommended continue here.

kdump and lmtp debug logs: https://pastebin.com/raw/MSVcj6qN <https://pastebin.com/raw/MSVcj6qN> & And from the backend I only have a tcpdump from another process but it's always the same behaviour: https://pastebin.com/tVj842Dq <https://pastebin.com/tVj842Dq>

If it doesn’t help, please let me know which logfiles exactly would help and would make the difference ;)

Greetings Pascal



> On 6 Dec 2019, at 21:26, Stephan Bosch via dovecot <dovecot at dovecot.org> wrote:
> 
> 
> 
> On 06/12/2019 11:08, Pascal Christen via dovecot wrote:
>> Hi
>> 
>> I tried to get some logs: https://pastebin.com/Z8xVzpzW
>> 
>> As you can see the process isn't shutdown and still in transaction as
>> long dovecot is running. It destroyed the transaction when I stopped
>> Dovecot. And this behavior only happens when the mailbox of user is full...
>> 
>> Any Ideas how to debug this correctly?
> 
> The provided logs look incomplete. The reception of the RCPT command by the server-side is not in the log, only the generation of the response. Also much of the client-side activity is not in the logs.
> 
> Also, a raw log of the TCP protocol exchange between Dovecot and Exim and also between proxy and backend can be useful. If  the connections are plaintext you can use wireshark or - if not - you can use the Dovecot rawlog facilities.
> 
> Regards,
> 
> Stephan.
>>> So far, I haven't been able to reproduce anything weird at this end.
>>> Can you provide:
>>> 
>>> - Output from `dovecot -n'
>>> - Protocol logs from the connections between Exim and Dovecot
>>> director/proxy and between Dovecot director/proxy and Dovecot backend
>>> (e.g. using ngrep when connections are plaintext or using the rawlog
>>> facility).
>>> - Dovecot debug logs produced with `log_debug=category:lmtp' for both
>>> director/proxy and backend
>>> 
>>> Regards,
>>> 
>>> Stephan.
>>> 
>>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/attachments/20200623/c55ef6e2/attachment.html>