I suppose I was a bit lax in terminology.
It technically doesn't violate the SMTP spec to not send a DSN, but from the
RFC 5321 (SMTP) and RFC 821 (Old SMTP) standards, both state that if a message
is not able to be forwarded or delivered, "the message MUST be returned as
undeliverable." (RFC 5321) There is exceptions for things like harmful or
invalid return addresses, but I'd presume a log sent from a properly formatted
email address is neither of those.
It breaks a lot of things, including user expectations, to just have a message
disappear into the ether.
73,
Sean - VA5LF
On 2013-06-12, at 6:21 PM, Katsuhiro Kondou <kondou@voyackey.net> wrote:
> In article <D1B4A9A8-E416-4CF4-97D3-DB349FD24DBE@unixgeeks.ca>,
> Sean Cavanaugh <seanc@unixgeeks.ca> wrote,
> on "Wed, 12 Jun 2013 12:26:38 -0600";
>
>> Most servers send back a Delivery Status Notification (DSN) saying the mail
>> was undeliverable. I'm rather surprised the ARRL server doesn't, as it is
>> very useful for both informing someone they sent the message to the wrong
>> address, and for diagnosing any mail delivery problems that occur. It also
>> violates the applicable standards (RFC 5321), but it seems a lot of people
>> are willing to throw the baby out with the bathwater when it comes to
>> fighting spam.
>
> I don't think it violate, since DSN is RFC3461, which is
> just an SMTP extention.
> --
> Katsuhiro "Don" Kondou, JH5GHM
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|