This would be outgoing email (below). While I work for a company, deleting
email would be a no-no... we just put **spam** in the subject and let the
user's deal with it.
-Original Message-
From: "Richard Lyon" <[EMAIL PROTECTED]>
Sent 9/27/2007 10:22:31 AM
To: declude.junkmail@declude.com
The filters we have in place usually detect them. If you're not using
Sniffer, I highly recommend you add it.
Darin.
- Original Message -
From: "Kevin Stanford" <[EMAIL PROTECTED]>
To:
Sent: Thursday, September 27, 2007 10:55 AM
Subject: RE: [Declude.JunkMail] Postmaster Spoofed Retu
I suppose the detection of "any remnants of the original spam" is going to
be a manual process...correct?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darin
Cox
Sent: Thursday, September 27, 2007 9:08 AM
To: declude.junkmail@declude.com
Subject: Re: [D
Here is a filter that I use that's pretty successful for me. Now I'm a
company so I can penalize on things an ISP can't, so buyer beware.
The logic is to end if the body contains a reference (IP or name) to a legit
email server of mine or someone who can send from my email server. So legit
bounces
I'm interested in this as well - and have a related question. I would like to
prevent vacation messages and autoresponder messages from going out to
addresses which fail an SPF record check... is this possible? I know this won't
be that many, but every little bit helps.
I used Declude with Imail
Does anyone have any suggestions on how to stop returned email on spoofed
email addresses for our domain.
I was going to setup a rule but it would catch good and bad alike...
Thanks,
Kevin
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EM
SPF can help a bit, if the receiver of the spoofed emails uses SPF for
filtering and does not bounce on SPF violation.
We've been able to limit the bounces that get through so far to just a few,
mostly through detection of any remnants of the original spam in the bounce.
Darin.
- Original
