<p>I absolutely hate that "brush it under the rug" reasoning. Far better if you synthetise a list for them to clean up (makes perfect, economic, sense for both parties), or (if you feel a bit more evil) forward the bounces to their mail admin (who should be handling abuses anyway).<br>
Takes a bit of courage to tell a customer to desist from idiocy, but... You actually might get some cred from it, if presented nicely;-) </p>
<p>Cheers<br>
-- <br>
-- Glenn</p>
<p><blockquote type="cite">Den 17 dec 2010 17.52, "Mike Tremaine" <<a href="mailto:mgt@stellarcore.net">mgt@stellarcore.net</a>> skrev:<br><br><p><font color="#500050"><br>> If you do not want replies or handle the bounces its BCP to use an empty <br>
> envelope sender.<br>> Sa...</font></p>Sadly the world is an imperfect place. I have no control over the sender's configuration. They are a very large company that handles the webservers and the newsletters go out from their servers. The bounces are due to bit rot in the mailling lists. The problem comes from the 6-10 in their smtp cluster, they can drop 1,000 of emails a minute into my stack. We get through it but I'd rather not spend the CPU cycles on it.<br>
<br>
Hopefully the DISCARD action will handle it. I just have to wait for the next bubble to be sure.<br>
<p><font color="#500050"><br>-Mike-- <br>MailScanner mailing list<br><a href="mailto:mailscanner@lists.mailscanner.info">mailscanner@lists.mailscanner.info</a><br><a href="http://lists.mailscanner.info/.">http://lists.mailscanner.info/.</a>..</font></p>
</blockquote></p>