David wrote:
> I will quit with the top posting in an already bottom posted thread, I
> suppose.
That would be greatly appreciated. It helps to have conformity to some
degree.
> What I meant was if ASSP has logs of the outgoing mail that it proxies
> to my MTA, instead of a user using his ISP's SMTP server (which we
> prevent by not allowing relaying and using smtp auth), then it would be
> decently easy to check to see if we actually did send the mail that is
> causing us to get the backscatter. The backscatter I'm referring to is
> not only non-existent users, but also vacation/auto-responders,
> challenge/verify emails, ISP Spam notices and others. While technically
> not spam, nor an NDR, why would I want to know that Clarice is out of
> the office if I never emailed her in the first place? Some crafty
> reg-ex's might help ASSP identify these and check them against the log
> of recently delivered messages.
>
I have never received any backscatter at any of my organizations. My
advice is:
1. Create SPF records. Use the "- all" option, not ""~all".
2. If you get any backscatter from a specific mail server, complain
and ask them to check SPF records or you will forward their
backscatter to DNSBL providers.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
