Re: aol..
- From: v-terliu@xxxxxxxxxxxxxxxxxxxx (Terence Liu [MSFT])
- Date: Thu, 03 Jul 2008 08:23:14 GMT
Hello Patrick,
Thank you for posting here.
According to your description, I understand that you unable to send email
to AOL after you change the ISP. If I have misunderstood the problem,
please don't hesitate to let me know.
Based on my research, I suggest we try the following steps to see if we can
resolve this issue:
1. Please ensure you check all factors in the following page. Especially
the Blacklisting, Improper DNS resolution of Remote Server, PTR Record.
What to Check When Exchange Cannot Send Email to Certain Domains
http://blogs.technet.com/sbs/archive/2008/01/03/what-to-check-when-exchange-
cannot-send-email-to-certain-domains.aspx
2. If we unable to resolve this issue after steps above, I think this is
mostly because the AOL block your new IP address.
If the aol.com is blocking your new IP, you need to get it touch with them
to get the IP unblocked. Please refer to the following page:
http://postmaster.info.aol.com/errors/554rtrsc.html
3. If you send email outbound thru smarthost, this will be the smarthost
issue, you may need to contact he smarthost support for help.
4. Ensure you can resolve the MX record of aol.com on your SBS:
a. Open cmd on SBS
b. Run the following commands:
nslookup
set type=mx
aol.com
Do you resolve the MX aol.com to IP address?
If we cannot resolve the issue after we perform the steps above, please
help me collect some information for further investigation:
1. Please save the NDR as msg file and send to me.
2. Enable SMTP logging and gather SMTP log to troubleshoot the issue:
A. Open Exchange System Manager, expand Servers -> <Server name> ->
Protocols -> SMTP, right-click "Default SMTP Virtual Server" and click
Properties.
B. Under the General tab, check the option "Enable Logging".
C. With "W3C Extended Log File Format", click "Properties".
D. Under "General Properties", make sure "Use local time for file naming
and rollover" is CHECKED.
E. Switch to the "Extended Properties", and then select to enable All the
logging Options.
F. Click OK to apply the modification.
G. Right-click Default SMTP Virtual Server and click Stop.
H. Right-click Default SMTP Virtual Server and click Start to restart the
SMTP server.
I. Reproduce the issue, repeat step G to stop Default SMTP Virtual Server,
copy out or zip the SMTP log files in the
"%systemroot%\system32\logfiles\SmtpSvc1" folder, and then restart the
"Default SMTP Virtual Server".
I hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Thread-Topic: aol..<PatrickMcCarrick@xxxxxxxxxxxxxxxxxxxxxxxxx>
thread-index: AcjcmyDGfokdGJS9Q+eUAYmnJNs9OQ==
X-WBNR-Posting-Host: 207.46.193.207
From: =?Utf-8?B?UGF0cmljayBNYyBDYXJyaWNr?=
References: <C8B047F8-D671-4528-9531-4AF658A6F702@xxxxxxxxxxxxx><#j2FDrs0IHA.4164@xxxxxxxxxxxxxxxxxxxx>
<57A01B7F-D50A-4E06-80E3-70C7005BD821@xxxxxxxxxxxxx>
<O0o8kXt0IHA.2384@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: aol..http://blogs.technet.com/sbs/archive/2008/01/03/what-to-check-when-exchange-
Date: Wed, 2 Jul 2008 16:27:00 -0700
Lines: 115
Message-ID: <F13F2ECF-BDE9-4F13-836A-FABC1319510B@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
Newsgroups: microsoft.public.windows.server.sbs
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:113859
NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
X-Tomcat-NG: microsoft.public.windows.server.sbs
Hi LArry,
I tried checking all those links and no joy... im pulling whats left of my
hair out :)...
any more suggestions.....
Patrick
"Larry Struckmeyer [SBS-MVP]" wrote:
Look through this:
cannot-send-email-to-certain-domains.aspx
to
another link indicated that the MTU could be an issue, and if you want
inknow how to test that, look here:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;159211
--
Larry
Please post the resolution to
your issue so that all can benefit.
"Patrick Mc Carrick" <PatrickMcCarrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
othermessage news:57A01B7F-D50A-4E06-80E3-70C7005BD821@xxxxxxxxxxxxxxxx
From: System Administrator
Sent: Sunday, June 01, 2008 1:42 PM
To: jeankejklndallolson@xxxxxxx
Subject: Undeliverable:Silver Turtle account #
Your message did not reach some or all of the intended recipients.
Subject: Silver Turtle account #
Sent: 5/30/2008 1:37 PM
The following recipient(s) could not be reached:
jeasnskendallolson@xxxxxxx on 6/1/2008 1:42 PM
Could not deliver the message in the time limit specified.
Please retry or contact your administrator.
<csconsultingservice.com #4.4.7>
"Larry Struckmeyer [SBS-MVP]" wrote:
HI Patrick:
Your public DNS records look ok, with the following possiblity.
<snip>
WARNING: One or more of your mailservers is claiming to be a host
followedthan
what it really is (the SMTP greeting should be a 3-digit code,
by a
space or a dash, then the host name). If your mailserver sends out
byusing this domain in its EHLO or HELO, your E-mail might get blocked
(andanti-spam software. This is also a technical violation of RFC821 4.3
shouldRFC2821 4.3.1). Note that the hostname given in the SMTP greeting
<br />have an A record pointing back to the same server. Note that this one
test
may use a cached DNS record.
sbs.csconsultingservice.com claims to be host csconsultingservice.com
[but
that host is at 205.178.145.65 (may be cached), not 69.69.245.61].
or<end snip>
You could also check on the various block lists to see if your domain
wroteip
are on one or more. AOL is very aggressive about not accepting mail.
Can you please post the exact NDR?
--
Larry
Please post the resolution to
your issue so that all can benefit.
"Patrick Mc Carrick" <PatrickMcCarrick@xxxxxxxxxxxxxxxxxxxxxxxxx>
address. Itin
message news:C8B047F8-D671-4528-9531-4AF658A6F702@xxxxxxxxxxxxxxxx
hello,
cleint running sbs2003 R2 sp1
ISA 2004
domain csconsultingservice.com
we just moved over to a new ISP, and are using their dns to route
email.
however no matter what we can not send to any aol.com email
comes
back as undeliverable....
i know it has to be a dns issue but dont know where to start.. any
ideas
..
thanks
.
- Follow-Ups:
- Re: aol..
- From: Patrick Mc Carrick
- Re: aol..
- References:
- Re: aol..
- From: Patrick Mc Carrick
- Re: aol..
- Prev by Date: Re: RRAS Port configuration
- Next by Date: Re: anti-spam recommendations
- Previous by thread: Re: aol..
- Next by thread: Re: aol..
- Index(es):
Relevant Pages
|
Loading