RE: cannot send emails to somebody@AOL .com



Hello Martin,

Thank you for posting in the SBS newsgroup.

Also, many thanks for Nicolas's input.

According to your description, I understand that you cannot send emails to
somebody@xxxxxxxx If I have misunderstood your concern, please don't
hesitate to let me know.

To narrow down this issue, please answer and perform the following
questions and steps:

1. Based on my research, the Numeric Code: 4.4.7 means:

Possible Cause: The message in the queue has expired. The sending server
tried to relay or deliver the message, but the action was not completed
before the message expiration time occurred. This NDR may also indicate
that a message header limit has been reached on a remote server or that
some other protocol timeout occurred during communication with the remote
server.

Troubleshooting: This code typically indicates an issue on the receiving
server. Verify the validity of the recipient address, and verify that the
receiving server is configured to receive messages correctly. You may have
to reduce the number of recipients in the header of the message for the
host that you are receiving this NDR from. If you re-send the message, it
is placed in the queue again. If the receiving server is on line, the
message is delivered.

284204 Delivery status notifications in Exchange Server and in Small
Business
http://support.microsoft.com/?id=284204

2. I also have tried to telnet AOL by using the same command, I got the
same result. I think you can refer to the below steps to try again:

telnet mailin-01.mx.aol.com 25
220-rly-xk01.mx.aol.com ESMTP mail_relay_in-xk1.1; Thu, 28 Jul 2005
00:04:51 -0400
220-America Online (AOL) and its affiliated companies do not
220- authorize the use of its proprietary computers and computer
220- networks to accept, transmit, or distribute unsolicited bulk
220- e-mail sent from the internet. Effective immediately: AOL
220- may no longer accept connections from IP addresses which
220 have no reverse-DNS (PTR record) assigned.
helo mydomain.com
250 rly-xk01.mx.aol.com OK
mail from:<martin@xxxxxxxxxxxx>
250 OK
rcpt to:<someone@xxxxxxx>
250 OK
....

3. Based on my research, nowadays many mail servers on the Internet are
enabled to perform reverse DNS lookup to make sure the senders'' SMTP
domains do exist. This is used to prevent spam emails which use fake SMTP
addresses. As I know, AOL will also perform reverse DNS check and if your
SMTP domain name is not resolved to the public IP address which the MX
record is pointed to, your emails will be rejected. I suggest you contact
your ISP and see if your SMTP domain is publicly registered and if yes, see
if the MX record is correctly pointed to your SBS 2000 server or to your
ISP''s mail server
(thus you use POP3 Connector to download your incoming emails from the
ISP''s mail server).

If you already have a publicly registered domain name, such as
YourCompany.com, and the MX record is also correctly configured, you need
to make sure you are using YourCompany.com as your primary email domain
other than the local domain name, YourCompany.local. To check this, open
Exchange System Manager, go to Recipients\Recipient Policies, double click
to open the Default Policy, click the "E-Mail Addresses (Policy)" tab, and
then make sure the "@YourCompany.com" address is listed as the primary
address (appears in bold). If it is not there, click New, choose "SMTP
Address" and add it. Check the "This Exchange Organization ..." box when
you add the SMTP address. If it is there but not bolded, you can select it
and click the "Set as Primary" button.

For more information, see:

319188 HOW TO: Use Recipient Policies to Control Mailboxes in Exchange 2000
http://support.microsoft.com/?id=319188

4. Additionally, please configure a SMTP connector to deliver all the
outgoing messages to AOL using Smart Host, and then check if the issue can
be re-produced.

265293 How to Configure the SMTP Connector in Exchange
http://support.microsoft.com/?id=265293

If the issue is not related to this situation, please help to collect the
SMTP logging using the following steps:

a. Open the properties page of the Default SMTP Virtual Server in Exchange
System Manager.

b. On the General tab, check the "Enable logging" box.

c. Click Properties, click the Extended Properties tab and check all the
boxes on the list.

d. Click OK twice.

e. Stop and restart the SMTP virtual server.

f. Ask a client to send two test emails entailed "Test Email To AOL #1(2)"
to an AOL recipient. Wait till you get the NDRs.

g. Stop the SMTP virtual server.

h. Go to the C:\WINDOWS\system32\LogFiles\SMTPSVC1 folder and send me the
latest two (if there are many) log files to
my mailbox: v-natliu@xxxxxxxxxxxxxx

I am appreciated your time and cooperation. If anything is unclear, please
feel free to let me know. I am looking forward to hearing from you.

Best regards,

Nathan 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.

--------------------
>From: "Martin Cheng" <martinwxcheng@xxxxxxxxxxx>
>Subject: cannot send emails to somebody@AOL .com
>Date: Wed, 27 Jul 2005 15:45:09 -0700
>Lines: 47
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <OK#iYzvkFHA.3656@xxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: 208.181.1.241
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:139316
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>We Can send emails through our sbs2003 but just find that we cannot send
>emails to AOL's email servers.
>
>SBS2003 sends a timeout report to us in a couple of days, like this
>
>
>Your message did not reach some or all of the intended recipients.
>Subject: RE: LONDON HAMBURG AUGUST 2005
>Sent: 7/25/2005 9:10 AM
>The following recipient(s) could not be reached:
>NeilSon@xxxxxxx on 7/27/2005 9:26 AM
>Could not deliver the message in the time limit specified. Please retry or
>contact your administrator.
><google-travel.com #4.4.7>
>
>
>I manually telnet to AOL
>
>telnet mailin-01.mx.aol.com 25
>220-rly-xg01.mx.aol.com ESMTP mail_relay_in-xg1.3; Wed, 27 Jul 2005
>13:34:21 -0400
>220-America Online (AOL) and its affiliated companies do not
>220- authorize the use of its proprietary computers and computer
>220- networks to accept, transmit, or distribute unsolicited bulk
>220- e-mail sent from the internet. Effective immediately: AOL
>220- may no longer accept connections from IP addresses which
>220 have no reverse-DNS (PTR record) assigned.
>helo mydomain.com
>250 rly-xg01.mx.aol.com OK
>mail from: martin@xxxxxxxxxxxx
>501 SYNTAX ERROR IN PARAMETERS OR ARGUMENTS
>
>
>
>I did the same thing from Internet to my win2003sbs server and no problem.
>
>Why AOL cannot report "501 SYNTAX ERROR IN PARAMETERS OR ARGUMENTS" to the
>[mail from] command from our sbs2003 server?
>
>
>
>
>
>
>
>
>
>

.