This is a discussion on Re: [courier-users] Spam black hole? within the Courier-Imap forums, part of the Mail Servers and Related category; --IbA9xpzOQlG26JSn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 02, ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
--IbA9xpzOQlG26JSn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 02, 2005 at 06:57:06AM -0700, Bill Taroli wrote: =20 > I learned recently that my employer's IT organization has decided it=20 > best for the MX to process all mail as if it were successful even when=20 > it's final disposition isn't. It neither returns 5xx (such as on bad=20 > address) nor do the subsequent MTA's and MDA's generate DSN's. Is this=20 > acceptable, or even suggested, practice? It's apparently generated a few= =20 > angry customers -- who think their emails are being ignored due to lack= =20 > of response -- but it also just seems wrong. I haven't reviewed the=20 > RFCs, but I wonder if it might also be considered non-compliant. Yes, RFC 2821 says: If an SMTP server has accepted the task of relaying the mail and later finds that the destination is incorrect or that the mail cannot be delivered for some other reason, then it MUST construct an "undeliverable mail" notification message and send it to the originator of the undeliverable mail (as indicated by the reverse- path). Formats specified for non-delivery reports by other standards (see, for example, [24, 25]) SHOULD be used if possible. In addition, in some legislations like Germany, this action may be consider= ed criminal (suppression of a message by a carrier, in essence). Jost --=20 | Jost.Krieger+sig@ruhr-uni-bochum.de Please help stamp out spam! | | Postmaster, JAPH, resident answer machine at RUB Comp. Center | | Sincere words are not sweet, sweet words are not sincere. | | Lao Tse, Tao Te King 81 | --IbA9xpzOQlG26JSn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (SunOS) iD8DBQFCoAUQ0+gPCYjXZAgRAg6MAKDSCm4Fumupi0TQ9XkfZm NkH4US6wCfVAJq fWG+tbutIItQMb+/n8SJKdM= =t/2d -----END PGP SIGNATURE----- --IbA9xpzOQlG26JSn-- ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users |