> The above employee can, however, send mail claiming he is still @yourdomain
> if he can find an SMTP server to use.
My problem is there's no "..if he can find an SMTP server to use". He already knows an SMTP server to use. Mine.
Yes, but he can only use it to send mail to your users. If he has any brains, he'll use another SMTP server (such as his ISP's), so he can send mail to *anywhere*.
I'll research SPF, but the way I understand it; without SPF I'm stuck with choosing between
FYI, with SPF, all you need to do is add a single DNS record. There is no cost involved, and the only real work is figuring out where users are allowed to send from.
But, I've found a solution if it is a problem with just a handful of disgruntled ex-employees: You can add them to your IMail SMTP Kill File. That way, they can't send E-mail to your customers from their old E-mail addresses.
They can still send to any other domains on the Internet, but the *only* technical solution (IE not tracking down the ex-employee and suing them) is something like SPF.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
