Re: Unable to send email to certain domains?

Ryan:
Regarding the following message:
"The remote host "hq-pdc.hq.tdronline.com", responded to the SMTP
command "xexch50" with "504 Need to authenticate first ". The full
command sent was "XEXCH50 1964 2 ". This will probably cause the
connection to fail."

I don't think this is what is causing you the problem. You will see
this anytime a connection is established to Exchange 5.5, but the connection
goes through anyway. It is annoying, but not a problem.

The first thing I would think is that somehow your server is on a RBL
(block list). However, if your server connects to a remote server and gets
denied a connection because it is on an RBL, that is usually a 500-level
error and the message NDR's immediately. The error you are getting is a
#4.4.7 error.

This not a simple resolution, but here are some things to try:
1) Stop and restart the SMTP service and see if that clears up the
problem. Your problem messages should clear the queues if this fixes the
problem.
2) Check the external IP address that your outbound SMTP mail uses. Make
sure that IP address has a PTR record. Some SMTP services running under
Unix or on a firewall will reject your connection if your IP address does
not have a PTR record.
3) Make sure none of your Exchange servers connecting to the Internet
have an "_" character in their name. This may cause problems for some remote
SMTP systems that are running Unix.
4) Enable SMTP protocol logging on the SMTP virtual server. Enable the
time/date/client IP/server IP/method/URI stem/URI query attributes. Wait a
few minutes (to give AD a chance to replicate and the SMTP logging a chance
to take affect) then stop and restart the SMTP virtual server. The SMTP
logs will show up in the \windows\system32\logfiles\smtpsvc folder. These
are not simple to read, but you should be able to find the SMTP conversation
and get more detailed information on why the remote server is rejecting your
requests.
5) Worst case, get familiar with Network Monitor, install it on your
outbound SMTP server or Exchange server, then watch the SMTP conversations
to see if anything pops up that might tell you why the remote system is
rejecting your connections.

I wish I could give you better guidance on this, but the #4.4.7 error
can be a lot of different things. Hope this helps.

--
Jim McBee
Blog: http://mostlyexchange.blogspot.com
Web: http://www.somorita.com


"Ryan" <rtierney@xxxxxxxxxx> wrote in message
news:1136494918.788473.42160@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> For the past three days, several employees have been able to send
> emails to some of our clients (on different domains).
>
> These messages will stay in the Exchange 2003 queue until I choose to
> delete them from the queue (or stay there for a few days, whichever
> comes first).
> The NDR reads as follows:
>
> Could not deliver the message in the time limit specified. Please
> retry or contact your administrator. <email2.CHMA.com #4.4.7>
>
> It's a Windows 2003 network using a single Exchange 2003 with SP2.
> A few days ago, I was told that we would be switching domain providers
> so that the company that hosts our website also hosted our domain
> (chmack.com). Would this have any impact at all with switching over
> what records are stored where, etc?
>
> This is the first time I've ever run into a problem like this and other
> than switching domain name providers, there have been no Exchange, DNS,
> etc changes whatsoever.
>
> Finally, here is one of the entries in the Application Log:
>
> Event Type: Error
> Event Source: MSExchangeTransport
> Event Category: SMTP Protocol
> Event ID: 7004
> Date: 1/5/2006
> Time: 3:36:58 PM
> User: N/A
> Computer: EMAIL2
> Description:
> This is an SMTP protocol error log for virtual server ID 1, connection
> #407. The remote host "hq-pdc.hq.tdronline.com", responded to the SMTP
> command "xexch50" with "504 Need to authenticate first ". The full
> command sent was "XEXCH50 1964 2 ". This will probably cause the
> connection to fail.
>
>
> Does anyone have an idea what's causing this and how to fix it?
> I've run the report at dnsreports.com and it came back with no major
> errors.
>


.

Relevant Pages

  • [NT] Vulnerability in Exchange Server Could Allow Arbitrary Code Execution (MS03-046)
    ... Get your security news from a reliable source. ... In Exchange Server 5.5, a security vulnerability exists in the Internet ... an unauthenticated attacker to connect to the SMTP port on an Exchange ...
    (Securiteam)
  • RE: SMTP error (only from Outlook)
    ... This issue appeared on specify user or all SMTP clients? ... If yes, in Exchange System ... Is there any local bridgehead server listed in "Local ... to over three dozen open relay block lists. ...
    (microsoft.public.windows.server.sbs)
  • RE: strange email errors
    ... you to check the relay configuration on the SBS server. ... please restart the SMTP virtue server and Exchange ... Please also refer to the following steps to create a new SMTP Connector to ...
    (microsoft.public.windows.server.sbs)
  • Re: Spam filtering with Connection Filtering
    ... If I have SMTP logging on my server, will it show the dropped connections? ... > Microsoft CSS Online Newsgroup Support ... >>I used http://support.microsoft.com/kb/823866/en-us to set up Connection ...
    (microsoft.public.windows.server.sbs)
  • Re: SMTP Connector - How to throttle down
    ... I am using my ISPs SMTP server as a smart host until ... I migrate all of my users to Exchange and set up the MX record to ... faster DSL connection, and sent out our first mass mailing. ... is there a way to configure my SMTP connector to ...
    (microsoft.public.exchange.admin)
Loading