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: [email protected] [mailto:[email protected]] On Behalf Of [email protected]
Sent: Wednesday, August 17, 2011 7:57 AM
To: [email protected]
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
[email protected] is the human contact address.
[email protected] 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
[email protected] is the human contact address.
[email protected] is the list posting address.
See below URL for subscribe/unsubscribe and list options:
http://inet-access.net/mailman/listinfo/list