On 10/23/2004 6:29, "Marc Perkel" <marc@???> wrote:
> Venting my frustrations - but this could be done.
>
> As you know there are moron sys admins wh reject all standard bounce
> messages. So when to do callout verification you get:
>
> HELO ctyme.com
> 250 helo MRLRY
> mail from: <>
> 501 bogus mail from
Well, that IS a bogus mail from. You should play by the rules if you want
the other side to. It contains a spurious space between the : and the <
By Example in RFC 821:
A MAIL command with a null reverse-path appears as follows:
MAIL FROM:<>
From RFC 2821:
MAIL FROM:<reverse-path> [SP <mail-parameters> ] <CRLF>
(I've never encountered an SMTP server which dislikes that space, but again,
if you want the other guy to play by the rules, you should.)
>
> So - first - I want to be able to detect this condition where the from
> <> is considered bogus immediately before any rcpt to:.
That's what the MAIL acl is for. You could write to a log for later
processing, or use ${run or the socket variation of that (probably better).
>
> Then - I'd like a script to auto report them to rfc_ignorant.org
Well, I dislike automated reporting in general. But I suppose if your
script takes care to report a given server once only, and only if it's not
already in the RFC Ignorant list (do I mean server or IP address?...which
opens the door to discussion of running servers on dynamic Ips) and you spot
check your reports, it's not too bad. I'm not going to do it.
--John
