Re: can't send aol email
- From: dave@xxxxxxxx
- Date: 30 Dec 2006 23:23:39 -0800
Hi Marsee,
Don't worry...most companies use an internal namespace that is entirely
different from that which the world sees. You can change the FQDN that
your server reports via SMTP. I recommend making it match your email
domain in this case
For each Exchange server that sends outbound mail:
In Exchange System Manager go to
'...Servers/<YourServerName>/Protocols/SMTP' and view the properties of
the SMTP Virtual Server(s). On the Delivery Tab, click Advanced.
There you can alter the FQDN that the SMTP VS reports via the 'Fully
qualified domain name' box. So if the server is known externally as
mail.foo.org put mail.foo.org in that box and restart IIS (iisreset).
You may also want to implement SenderID. You can use SenderID to
declare which servers originate mail for your domain via DNS. Of
couse, the receiving party would need to support SenderID. Check this
out:
http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/
Dave
marsee wrote:
Several years ago I set the internal FQDN as .net for security reason
while our website and email use .org
All was fine until several months ago when AOL and Earthlink began to
view the .net and .org differance as a relay.
I have ensured that the MX records are pointing correctly.
The only remedy I can come up with would be to change the internal
domain to .org which would be a HUGE amount of work since each
workstation would have to be removed and then joined to the new .org
domain.
All of our printed material, etc uses the .org website so changing that
domain name isn't going to happen.
Anyone have any less painful ideas on how to fix this? Your input is
greatly appreciated. Thanks
.
- References:
- can't send aol email
- From: marsee
- can't send aol email
- Prev by Date: Re: RPC network traffic
- Next by Date: Re: exchange rpc over http problems
- Previous by thread: Re: can't send aol email
- Next by thread: Re: can't send aol email
- Index(es):
Relevant Pages
|
