Re: [Declude.JunkMail] blocking spam faked as coming from local address

[Matthew Bramble]

It would solve that issue, however I'm a big promoter of never using a domain that you don't own when you can avoid it because it creates a liability, though not on simple replies.  I've worked with many to help them remove any trace of an old ISP account and this might tell their receivers that the un-owned account is still active.  I'd rather whitelist them instead, it would be less work. I'm not worried about adding a couple extra points to that stuff though since their ISP's mail server should be fairly clean, and I have decided that rejecting valid E-mail from a server marked as an open relay isn't in fact a false positive, though this only rarely happens.  It's the non-customers sending valid stuff that is forged and the hardware devices that send out notifications which tend to have difficulties in passing some of the technical tests (HELOBOGUS, BADHEADERS and SPAMHEADERS among others).  I already have some issues with this stuff FP'ing and bounces aren't useful in the second instance. Matt Bill Landry wrote: ----- Original Message ----- From: Matthew Bramble Thanks for the link to the GNU stuff. I might be asking for some help writing useful strings of pipes in the future :) No problem, I have several scripts I run to generate differnt kinds of reports. [snip] I think you might have overlooked this in your response because WHITELIST AUTH won't forgive these senders, [...] Good point. I would suggest that in these circumstances where a customer is using their ISP's MTA for outbound mail delivery, that you have them set their e-mail address in their e-mail client to their ISP account and then set their "Reply To" address as their e-mail address on your IMail server. I think this would resolve the inadvertant flagging of these customer e-mails with referrence to the spamdomains tests. Bill