[Mimedefang] Greylisting post-data (was Re: [PATCH] filter_data implementation)
Jeff Rife
mimedefang at nabs.net
Thu May 28 10:21:21 EDT 2009
On 28 May 2009 at 9:40, David F. Skoll wrote:
> Jeff Rife wrote:
>
> > Based on the full text of the RFCs and not just the examples, "450"
> > seems to be a perfectly acceptable temporary failure.
>
> I read them differently. I see 450, 451 and 452 as acceptable after
> the final dot, but only 421 in direct response to DATA. (I'm basing
> my interpretation on RFC 5321.)
What text, exactly, leads you to that conclusion?
To be honest, based on the text, the only acceptable responses to
"DATA" are "354", "503", or "554", since there is never an example of
any temporary fail code being valid. Even the "421...may be a reply to
any command if the service knows it must shut down" is only a slight
"out", since you aren't really "shutting down".
But all of the following make sense after "DATA", even though they
aren't specifically listed:
450 Requested mail action not taken: mailbox unavailable (e.g.,
mailbox busy or temporarily blocked for policy reasons)
451 Requested action aborted: local error in processing
452 Requested action not taken: insufficient system storage
All are acceptable on the premise that although the "RCPT TO:" all had
acceptable values, now that we know that a real e-mail is coming
through, we can't complete the action at this time.
--
Jeff Rife | "I have a question that could affect our entire
| relationship...did you kill Coach Mattay?"
| "No!"
| "But, you did dress him up like a woman...?"
| "Yeah."
| "Just checking."
| -- Alex Lambert and Brian Hackett, "Wings"
More information about the MIMEDefang
mailing list