> Wrong, the mail is NOT being delivered, it is being accepted for
> delivery. The message is then being rejected because of a local
> failure on the part of the users mailbox.
> What I'm saying is that on most systems, I get a single report for the
> message delivered to that site.
I think you'll find that this is generally NOT true when some of the
messages fail due to permanent errors while others fail due to
persistent transient errors. A mailer will normally report all errors
that occur within a single delivery "pass" in a single message.
Permanent errors get caught in the first "pass", but transient errors
cause further attempts at delivery. It's only later, when the mailer
"gives up", that it bounces those messages.
> Something that states that the 1 message that was to be received by
> users a,b,c,d was not delivered to c and d for reason x and y. It
> can and should be delivered to a and b. This does happen on most
> system, but not AOL. AOL is taking the 1 message and making 8 out
> of it internally, then doing 8 seperate deliveries or bounces.
If this is true it should be a simple fix to their system. AOL uses
sendmail, at least for the front-end, and sendmail is quite capable of
doing multiple delivery attempts in a single pass.
If it is not doing so, I suspect it is because they're so large that
they split mail delivery across several machines. (even if this is
the case, it's fairly easy to fix this so that the errors are all
collected at a single site.)
Next time you get multiple bounces from AOL, look at their headers.
Are they being bounced from different physical machines or the same
one?
Keith Moore
References:
|
|
