MAIL transaction in progress

[Mark Martinec]

(was: Re: amavisd-new-2.7.0-rc1 release candidate is available)

Ralf,

503 5.5.1 Error: MAIL transaction in progress
and
503 5.5.1 Error: nested MAIL command

Please search the log for a task immediately preceeding the failed one,
e.g. the 28025-01 and the 25000-18 in your case. Anything strange there?
Mark

Ralf, can you provide any further information on that?

Mark

[Ralf Hildebrandt]

Post by Mark Martinec
(was: Re: amavisd-new-2.7.0-rc1 release candidate is available)
Ralf,

503 5.5.1 Error: MAIL transaction in progress
and
503 5.5.1 Error: nested MAIL command

Please search the log for a task immediately preceeding the failed one,
e.g. the 28025-01 and the 25000-18 in your case. Anything strange there?
Mark

Ralf, can you provide any further information on that?

No, it was a one time event, and must have been related to some other
problem with the machine...

[Mark Martinec]

503 5.5.1 Error: MAIL transaction in progress
503 5.5.1 Error: nested MAIL command

For the archive:

Ralf has provided the logs of a previous transaction
leading to this error and tested the fix, thanks!
Fixed in the released 2.7.0:


BUG FIXES SINCE 2.6.6

- take a more cautious approach on keeping evidence on an SMTP session
transaction state when feeding a message back to MTA. Under certain
abnormal circumstances an MTA could respond to end-of-data with a temporary
failure but retain an active transaction state, while amavisd would assume
the transaction was closed, leading to a 'MAIL transaction in progress'
failure on the next message using the same cached SMTP session.
Now amavisd considers a transaction state to be unknown when there is any
doubt and closes a session instead of caching it, unless the transaction
is reliably known to be closed.


Mark

[Ralf Hildebrandt]

Post by Mark Martinec

503 5.5.1 Error: MAIL transaction in progress
503 5.5.1 Error: nested MAIL command

Ralf has provided the logs of a previous transaction
leading to this error and tested the fix, thanks!

And thanks to Mark from Italy for fixing this :)