[AMaViS-user] nested MAIL command
Richard Smits
Does anyone know what causes this error ? I have multiple a day.
Sep 2 06:16:17 mx3-b amavis[8425]: (08425-19) smtp resp to MAIL (pip):
503 5.5.1 Error: nested MAIL command
Sep 2 06:16:17 mx3-b amavis[8425]: (08425-19) (!)SEND via SMTP: <> ->
<edit...@ebook-engineering.org>,ENVID=AM..20080902T041617Z@company.com
503 5.5.1 Failed, id=08425-19, from MTA([127.0.0.1]:10027): 503 5.5.1
Error: nested MAIL command
Sep 2 06:16:17 mx3-b amavis[8425]: (08425-19) (!)NOTICE: UNABLE TO SEND
DSN to <edit...@ebook-engineering.org>: 503 5.5.1 Failed, id=08425-19,
from MTA([127.0.0.1]:10027): 503 5.5.1 Error: nested MAIL command
I suspect that it's an amavis issue, because these errors started the
day I upgraded to 2.6.1 from 2.5.3.
I have multiple servers, but this problem only occurs on one server. It
is the only one with Redhat 5 , postfix 2.3.3, perl 5.8.8.
Could this be a configuration issue ?
Greetings... Richard Smits
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
AMaViS-user mailing list
AMaVi...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
Mark Martinec
> Does anyone know what causes this error ? I have multiple a day.
>
> Sep 2 06:16:17 mx3-b amavis[8425]: (08425-19) smtp resp to MAIL (pip):
> 503 5.5.1 Error: nested MAIL command
> Sep 2 06:16:17 mx3-b amavis[8425]: (08425-19) (!)SEND via SMTP: <> ->
> <edit...@ebook-engineering.org>,ENVID=AM..20080902T041617Z@company.com
> 503 5.5.1 Failed, id=08425-19, from MTA([127.0.0.1]:10027): 503 5.5.1
> Error: nested MAIL command
> Sep 2 06:16:17 mx3-b amavis[8425]: (08425-19) (!)NOTICE: UNABLE TO SEND
> DSN to <edit...@ebook-engineering.org>: 503 5.5.1 Failed, id=08425-19,
> from MTA([127.0.0.1]:10027): 503 5.5.1 Error: nested MAIL command
>
> I suspect that it's an amavis issue, because these errors started the
> day I upgraded to 2.6.1 from 2.5.3.
>
> I have multiple servers, but this problem only occurs on one server.
> It is the only one with Redhat 5 , postfix 2.3.3, perl 5.8.8.
> Could this be a configuration issue ?
Strange. Looks like a programming error (not a configuration issue),
although it's the first time I've heard of such issue.
I would appreciate a log at level 5 of the entire failing session.
(especially the 'rw_loop:' log entries and around).
Mark
Mark Martinec
Thanks for the log (sent offline). It turns out there is indeed
a bug in amavisd, triggered in your setup. Fortunately it only
happenes at rare sites where incoming MTA does not verify validity
of recipients, which is then validated later on a re-entry port (10025),
sometimes causing amavisd session management to go out-of-step,
thinking the smtp transaction is over where in reality it is not,
which is why you see first:
(!)FWD via SMTP: <...> -> <...>,BODY=7BIT 550 5.1.1 Failed, id=01189-11,
from MTA([127.0.0.1]:10027): 550 5.1.1 <...>: Recipient address rejected:
User unknown in virtual alias table
and then in the following transaction:
(01189-12) <...> -> <...>,BODY=7BIT 503 5.5.1 Failed, id=01189-12,
from MTA([127.0.0.1]:10027): 503 5.5.1 Error: nested MAIL command
Here is a patch to amavisd-new-2.6.1 :
--- amavisd.orig 2008-06-29 02:37:58.000000000 +0200
+++ amavisd 2008-09-04 19:58:00.000000000 +0200
@@ -16879,11 +16879,16 @@
if (!$data_command_accepted) {
do_log(0,"Negative SMTP resp. to DATA: %s", $smtp_resp);
+ $in_datasend_mode = 0;
+ $smtp_session->timeout($smtp_rset_timeout);
+ $what_cmd = 'RSET'; $smtp_handle->rset; # send a RSET
} elsif (!$any_valid_recips) { # pipelining
do_log(2,"Too late, DATA accepted but no valid recips, send dummy");
$which_section = 'fwd-data-contents';
$smtp_session->timeout(
- max(60,min($smtp_data_xfer_timeout,$deadline-time)));
+ max(60,min($smtp_data_done_timeout,$deadline-time)));
+ $what_cmd = 'data-dot';
$smtp_handle->dataend; # as required by rfc2920: if the DATA command
# was accepted the SMTP client should send a single dot
+ $in_datasend_mode = 0;
} elsif ($any_tempfail_recips && !$dsn_per_recip_capable) { # pipelining
# we must not proceed if mail did not came in as LMTP,
Richard Smits
Thank you for the patch. I will apply it next monday. I will let you
know if the problem is solved.
Greetings... Richard
Mark Martinec
> Thank you for the patch. I will apply it next monday.
> I will let you know if the problem is solved.
Btw, a workaround is to turn off smtp session caching:
$smtp_connection_cache_enable = 0;
R.Smits
The patch is working great...
Will this patch be included in the new release ?
Greetings... Richard
Mark Martinec
> Ah ok...
> The patch is working great...
>
> Will this patch be included in the new release ?
Certainly. Thanks for the bug report!