I think if the MTA sends a 5xx rejection code due to message size ASSP will proxy that to the sender instead of 220 OK, thus no backscatter. Mailbox full is a very common reason for backscatter spam though becase most MTA's can't determine during the SMTP session if the mailbox will be full (not properly configured probably) so they just accept it and send NDR's later. But ASSP can't do anything about that
On 9/29/2009 9:31 PM, Scott Haneda wrote: > How does rejection of oversized messages work in this case? Wouldn't > the primary MTA reject back to ASSP, (backscatter)? > > It's like greylisting, while I can do this on my MTA, if I do, it will > break when any proxy sits in front of ASSP. > > How does one define MTA specific features that can cause rejections > and not have rejection message issues? Perhaps I am misunderstanding > the mail flow. > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test