Friday, August 21, 2009 10:26 AM
To: MS-Exchange Admin Issues
Subject: Re: BLOCKING SPOOFED INTERNAL EMAIL--FOLLOW UP!
On Thu, Aug 20, 2009 at 4:57 PM, Murray Freeman wrote:
> If we use the *...@alant.org in the SPF, we then create a problem with
legitimate
> email coming from an external mail se
On Thu, Aug 20, 2009 at 4:57 PM, Murray Freeman wrote:
> If we use the *...@alant.org in the SPF, we then create a problem with
> legitimate
> email coming from an external mail server, our website which is hosted by a
> third party.
As ME2 says, you should add your web server's IP address to t
rnate mail address to the required users so the external messages are
reply-able.
Carl
From: Murray Freeman [mailto:mfree...@alanet.org]
Sent: Thursday, August 20, 2009 4:58 PM
To: MS-Exchange Admin Issues
Subject: BLOCKING SPOOFED INTERNAL EMAIL--FOLLOW UP!
I really appreciate the respo
You can use the "include" option if you can do it based on sender
domain name, or use the "ip4" option to specify specific valid sending
IP4 addresses.
e.g. You can easily just add 'include:constantcontact.com" if you need
to allow ConstantContact to send emails on your behalf, and you trust
that
I really appreciate the responses to my request for help blocking
spoofed Internal email. I did some research and found that Exchange
Server 2K3 has some potential to assist with this issue, but there is
one problem. If we use the *...@alant.org in the SPF, we then create a
problem with legitimate
