--
Message: 6
Date: Fri, 01 Mar 2013 12:52:11 +0100
From: Fritz Borgstedt f...@iworld.de
Subject: Re: [Assp-test] Whitelisting by sender domain/ip recipient
To: ASSP development mailing list assp-test@lists.sourceforge.net
Message-ID:
Further to this and the reply I think the BCC thing is a complete red herring.
We are simply seeing lots of emails coming through are missing the headers.
I've already spent nearly an hour processing manual resend requests today so it
is becoming quite a big issue and people are starting to ask
I just started to get a flood of ATT Wireless bill emails this
morning and see that there is no SPF record for their domain. Any
suggestions on how to block this without blocking the real emails, which
I have validated also come from the same source email address? Headers
for the bad email are
Remove ica...@amcustomercare.att-mail.com from whitelist
Add att.com to whiteorg.txt (whiteSenderBase)
--
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013
Fritz,
Should I add att.com or att-mail.com or
amcustomercare.att-mail.com to the whiteSenderBase? ATT.com doesn't seem
related to the below email address is why I ask.
Rusty Nejdl
On
2013-03-08 13:02, Fritz Borgstedt wrote:
Remove
ica...@amcustomercare.att-mail.com from whitelist
Add
rne...@ringofsaturn.com schreibt:
Should I add att.com or att-mail.com or
amcustomercare.att-mail.com to the whiteSenderBase? ATT.com doesn't seem
related to the below email address is why I ask.
whiteSenderBase is using the sending IP to check organization/domain for
whitelisted entries.
The
My ASSP uses test mode. causing the subject to be prefixed with [SPAM] which I
catch downstream. (in case that matters). The problem I'm having is that mail
with a faked from address (different from MAIL FROM) is getting through
unmarked.
Below is an analysis of such a message. As you can
