Alan DeKok wrote:
http://www.striker.ottawa.on.ca/~aland/smtp-sucks/problems.txt
I had only a short glance, but
*> 5. Don't allow multiple RCPT TO's for unknown senders.
*> The problem is that you can't selectively NACK later RCTP TO's. The
*> sending MTA then decides that the entire message was NACK'd, and
*> discards (or retries) it.
If the MTA is behaving that way it is seriously broken. The behaviour
as you describe only happens if you NACK the "DATA" command after the
CRLF.CRLF (RFC 2821 4.2.5 Reply Codes After DATA and the Subsequent
<CRLF>.<CRLF>)
Our mailserver doesn't allow more than 5 RCPT TO per session. The others
are answered with a temp failure (4xx code). This works without any
problems for years.
Btw. I have posted some stats (backed by someone from an university,
sorry forgot about the name) and it showed that more than 95% of all spam
is NOT multi-RCPT. However I can't find it in the archives nor in my
mailbox at the moment :((
\Maex
--
SpaceNet AG | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development | D-80807 Muenchen | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
proportional to the amount of vacuity between the ears of the admin"
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg