[prev in list] [next in list] [prev in thread] [next in thread] 

List:       inet-access
Subject:    RE: Blacklisting your own domain?
From:       up () 3 ! am
Date:       2011-08-17 21:15:44
Message-ID: a1bf86b4577d674355dd9ccd96356ccf.squirrel () ssl ! pil ! net
[Download RAW message or body]


Since these are generated by localhost, or servers that already bypass it,
SpamAssassin won't be called.  That is all controlled by ucspi tcp.


> Don't forget you will need to exempt all addresses coming from daemons and
> administrative applications.  (Think about legitimate bounce messages)
>
> Kevin
>
>
>
>> -----Original Message-----
>> From: list-bounces@inet-access.net [mailto:list-bounces@inet-access.net]
>> On Behalf Of Frank Bulk
>> Sent: Wednesday, August 17, 2011 3:34 PM
>> To: list@inet-access.net
>> Subject: RE: Blacklisting your own domain?
>>
>> If you run your own domain with a small number of users, SPF can be an
>> effective means to accomplish what the OP is looking to do.  Any larger
>> and
>> you have to start dealing with re-emailers (i.e. sending an email from
>> cnn.com and sending it to a user in your own domain).
>>
>> Frank
>>
>> -----Original Message-----
>> From: list-bounces@inet-access.net [mailto:list-bounces@inet-access.net]
>> On
>> Behalf Of Blake Pfankuch
>> Sent: Wednesday, August 17, 2011 11:41 AM
>> To: list@inet-access.net
>> Subject: RE: Blacklisting your own domain?
>>
>> I've been using strict SPF validation for this as well on my personal .  I
>> ran into a single issue with a single server on the outside of my network
>> that does email alerts based on process status on that server that I
>> didn't
>> have added to SPF.  As far as blocking *@fqdn, I've done that a few times
>> too however I've been trying to stick with SPF.
>>
>> Blake Pfankuch
>>
>> -----Original Message-----
>> From: list-bounces@inet-access.net [mailto:list-bounces@inet-access.net]
>> On
>> Behalf Of up@3.am
>> Sent: Wednesday, August 17, 2011 7:57 AM
>> To: list@inet-access.net
>> Subject: Blacklisting your own domain?
>>
>> After having yet another user fall for a phishing scam and giving their
>> user/pass out to spammers, and the ensuing headaches (delistings,
>> temporary
>> re-routings, etc), I'm decided to try something really simple in
>> SpamAssassin:
>>
>> blacklist_from          *@pil.net
>>
>> I'm trying to think how this might cause problems, but I can't think of
>> any.
>>
>> Users that SMTP Auth or POP Before SMTP bypass SA.  Is this fairly common
>> practice already?  Am I that slow to the game?
>> --
>> Eat sushi frequently. - Avi
>> inet@inet-access.net is the human contact address.
>> list@inet-access.net is the list posting address.
>> See below URL for subscribe/unsubscribe and list options:
>> http://inet-access.net/mailman/listinfo/list
>> --
>> Eat sushi frequently. - Avi
>> inet@inet-access.net is the human contact address.
>> list@inet-access.net is the list posting address.
>> See below URL for subscribe/unsubscribe and list options:
>> http://inet-access.net/mailman/listinfo/list
>>
>> --
>> Eat sushi frequently. - Avi
>> inet@inet-access.net is the human contact address.
>> list@inet-access.net is the list posting address.
>> See below URL for subscribe/unsubscribe and list options:
>> http://inet-access.net/mailman/listinfo/list
> --
> Eat sushi frequently. - Avi
> inet@inet-access.net is the human contact address.
> list@inet-access.net is the list posting address.
> See below URL for subscribe/unsubscribe and list options:
> http://inet-access.net/mailman/listinfo/list
>

-- 
Eat sushi frequently. - Avi
inet@inet-access.net is the human contact address.
list@inet-access.net is the list posting address.
See below URL for subscribe/unsubscribe and list options:
http://inet-access.net/mailman/listinfo/list
[prev in list] [next in list] [prev in thread] [next in thread]