LMTP error in newest Dovecot

D

ditto

Verified User
Joined
Apr 27, 2009
Messages
1,980
After upgrading from Dovecot 2.2.29.1 to 2.2.30.1, one of my users email account have this error in the log (I have masked the email address and user):

Code: 
2017-06-05 17:23:20 Received from [email protected] U=user-removed P=local S=3314 [email protected] T="subject-removed"

2017-06-05 17:23:20 [email protected] R=virtual_user T=dovecot_lmtp_udp defer (-44): LMTP error after RCPT TO:<[email protected]>: 451 4.3.0 <[email protected]> Internal error occurred. Refer to server log for more information.

The email is sent from a contact form on the site, and the email address is local on the same server. When it have this error, it just stays in email queue, however as soon as I manually hit "Retry", then it works and is sent.

So far this only happen to this one user. I have not seen it on any other email addresses. Have anybody else seen this happen? I don't find anything else in the logs.

By the way I am running the newest exim.conf and dovecot.conf.
 
Now I am also getting the same error on a different user on a different server. Considering to downgrade to Dovecot 2.2.29.1. Nobody else that have seen this?
 
I have been noticing the same issue after upgrading Dovecot to 2.2.30.1. The messages end up in the queue and throw the same LMTP error as you mentioned, they are however successfully reprocessed automatically after 30 min. I'll try to downgrade to 2.2.29.1 later today to see if that solves it.
 
Must indeed be a bug, having the same issue and going to try to downgrade to dovecot 2.2.29.1.
What is the exact procedure to downgrade to 2.2.29.1?
I found this post but I don't know hashes of 2.2.29.1 or how to do this exactly.
 
You don't really need the hashes. What I did was just changed this line in /usr/local/directadmin/custombuild/versions.txt:

Code: 
dovecot:2.2.30.1:d5927c2a00440df40208b6bd415a92c1
to be like this:
Code: 
dovecot:2.2.29.1

Then I did ./build dovecot - it is important to remember not to do ./build update before you have done ./build dovecot, so that versions.txt is not overwritten before you have downgraded.

Edit: You need to have set autover=no in options.conf, if not custombuild will download new versions.txt every time with every ./build command and overwrite versions.txt before you have downgraded. Remember to change it back to autover=yes after you have downgraded, or else you will have to run ./build update manually every time you use custombuild (that is what I prefer, but most would not prefer that).

By the way, the problem disappeared after I downgraded Dovecot, so it is for sure a bug in the newest version.
 
Last edited:
A better way to specify a specific version would be to use /usr/local/directadmin/custombuild/custom_version.txt that way the regular versions.txt is still updated and you don't have to change autover. Or if you have the GUI plugin you can just go to the Customize Versions tab, select dovecot and enter the version number without any MD5 hash. Afterwards (or when the issue is solved) you can just remove custom_version.txt

I can, by the way, also confirm that the issue is solved when downgraded to 2.2.29.1
 
Thank you for your explanations Ditto and Vaporizer.
But luckily there is already a fix so I upgraded to 2.2.30.2 now.
 
I hope you did a ./build update before you did the ./build dovecot because we're at 2.2.32 already which is a couple of versions further.

Is it the same error as above or is it another one?
Because I also still get LMTP errors, but only when the users mailbox is full, so no internal error anymore, it's like this:
Code: 
T=dovecot_lmtp_udp: LMTP error after RCPT TO:<[email protected]>: 552 5.2.2 <[email protected]> Quota exceeded (mailbox for user is full)
No other lmtp errors in the log, this one can be ignored.

It's also better not to post multiple messages (doublepost) on the same issue. ;)
 
You must log in or register to reply here.
Back
Top