RE: Your message did not reach some or all of the intended recipie

Hi Nathan,

I have configured the settings to smart host

In your details you are saying to type the following command

'mail from:' and press enter even when I do this on my server where my mail
is working fine I still get the following error message,

mail from:
501 5.5.4 Invalid Address

How easy is it just to uninstall exchange and reinstall ?


--
Ian Campbell


""Nathan Liu [MSFT]"" wrote:

> Hi Ian,
>
> Thank you for your update.
>
> To narrow down this issue, please refer to the below information:
>
> I. For the error message "mailfrom: 500 5.3.3 Unrecognized command, mail
> from: 501 5.5.4 Invalid Address", please understand if we type the
> incorrect SMTP telnet command, we will receive the "Unrecognized command"
> error message, we must re-open a new command prompt, then re-establish the
> SMTP telnet session. Thanks for your understanding.
>
> Step 1: When the issue happens again, in the Exchange Server, please telnet
> the destination mail server which you cannot send mail to by the following
> steps.
>
> 1. Click 'Start', click 'Run', type 'telnet', and then click 'OK'.
>
> 2. At the Microsoft Telnet command prompt, type 'open server_name 25', and
> then press ENTER.
>
> 3. To verify that you are successfully connected to the SMTP Mail Service,
> type 'helo domain.com', and then press ENTER.
>
> 4. Type 'mail from:' , and then press ENTER.
>
> 5. Type 'rcpt to:', and then press ENTER.
>
> 6. Type "quit" (without the quotation marks), and then press 'ENTER' two
> times to close the connection to the server and leave the Telnet session
> running.
>
>
> Step 2: When the issue happens again, in the Exchange Server, please telnet
> the destination mail server which you cannot send mail to by the following
> steps.
>
> 1. Click 'Start', click 'Run', type 'telnet', and then click 'OK'.
>
> 2. At the Microsoft Telnet command prompt, type 'open server_name 25', and
> then press ENTER.
>
> 3. To verify that you are successfully connected to the SMTP Mail Service,
> type 'ehlo domain.com', and then press ENTER.
>
> 4. Type 'mail from:' , and then press ENTER.
>
> 5. Type 'rcpt to:', and then press ENTER.
>
> 6. Type "quit" (without the quotation marks), and then press 'ENTER' two
> times to close the connection to the server and leave the Telnet session
> running.
> More detailed information:
>
> XFOR: Telnet to Port 25 of IMC to Test IMC Communication:
> http://support.microsoft.com/?id=153119
>
> II. Did you switch to forward to smarthost to deliver emails? You can
> refer to the detailed steps in my previous reply.
>
> III. If the issue persists, please perform the below steps:
>
> 1. Open the Server Management console, go to DomainName(Exchange) ->
> Connectors, right click 'SmallBusiness SMTP connector' and select
> Properties.
>
> 2. In the dialog box, click the Advanced tab, click the 'Send HELO instead
> of EHLO' check box, then click Apply.
>
> 3. Please check if the issue can be reproduced.
>
> I appreciate 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.
>
> --------------------
> >Thread-Topic: Your message did not reach some or all of the intended
> recipie
> >thread-index: AcWyn7KaufjPq44TQouWmfMx57a3qg==
> >X-WBNR-Posting-Host: 144.134.225.123
> >From: =?Utf-8?B?SWFu?= <Ian@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <C8026CBE-2A16-4629-89F3-D5A9EFD0D610@xxxxxxxxxxxxx>
> <ADoa4mdsFHA.3308@xxxxxxxxxxxxxxxxxxxxx>
> <B8C103C3-D1BE-4166-9CC7-8D0AFB73222E@xxxxxxxxxxxxx>
> >Subject: RE: Your message did not reach some or all of the intended recipie
> >Date: Mon, 5 Sep 2005 21:59:01 -0700
> >Lines: 263
> >Message-ID: <05758678-9399-4420-AE5A-47D8B0433EE1@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.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:151047
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Just tried to send another email to my own address.
> >
> >
> >Your message did not reach some or all of the intended recipients.
> >
> > Subject: Test Test
> > Sent: 6/09/2005 2:53 PM
> >
> >The following recipient(s) could not be reached:
> >
> > iancampbell@xxxxxxxxxxxxxxxxxxxx on 6/09/2005 2:54 PM
> > There was a SMTP communication problem with the recipient's
> >email server. Please contact your system administrator.
> > <AHSSBS03.allanhogansolicitors.local #5.5.0 smtp;553
> >allanhogansolicitors.local does not exist>
> >
> >
> >
> >--
> > Ian Campbell
> >
> >
> >"Ian" wrote:
> >
> >> Nathan,
> >>
> >> 1. I can connect to the mail server via Telnet
> >> 2. When I typed mail from: , I got the following error message.
> >>
> >>
> >> 220 AHSSBS03.allanhogansolicitors.local Microsoft ESMTP MAIL Service,
> Versi
> >> .0.3790.1830 ready at Tue, 6 Sep 2005 14:20:33 +1000
> >> helo domain.com
> >> 250 AHSSBS03.allanhogansolicitors.local Hello [10.0.0.1]
> >> mailfrom:
> >> 500 5.3.3 Unrecognized command
> >> mail from:,
> >> 501 5.5.4 Invalid Address
> >>
> >>
> >>
> >>
> >> --
> >> Ian Campbell
> >>
> >>
> >> ""Nathan Liu [MSFT]"" wrote:
> >>
> >> > Hello Ian,
> >> >
> >> > Thank you for posting in the SBS newsgroup.
> >> >
> >> > I am sorry for the delayed response due to weekend. Please understand
> that
> >> > the newsgroups are staffed weekdays by Microsoft Support professionals
> to
> >> > answer your systems and applications questions. Your understanding is
> >> > greatly appreciated!
> >> >
> >> > According to your description, I understand that you received the NDR
> 5.5.0
> >> > when you sent emails. If I have misunderstood your concern, please
> don't
> >> > hesitate to let me know.
> >> >
> >> > Based on my knowledge, the Non-Delivery Report 5.5.0 refers to Generic
> >> > protocol error (SMTP error). The remote SMTP response to our EHLO with
> a
> >> > 500 level error and the sending system will QUIT the connection and
> report
> >> > this with NDR indicating the remote SMTP server cannot handle the
> protocol.
> >> >
> >> > More info here:
> >> > 284204 Delivery Status Notifications in Exchange 2000 Server
> >> > http://support.microsoft.com/?id=284204
> >> >
> >> > Please perform the following steps:
> >> >
> >> > 1. When the issue happens again, in the Exchange Server, please
> telnet
> >> > the destination mail server which you cannot send mail to by the
> following
> >> > steps.
> >> >
> >> > a. Click Start, click Run, type telnet, and then click OK.
> >> >
> >> > b. At the Microsoft Telnet command prompt, type open server_name 25,
> and
> >> > then press ENTER.
> >> >
> >> > c. To verify that you are successfully connected to the SMTP Mail
> Service,
> >> > type helo domain.com, and then press ENTER.
> >> >
> >> > d. Type mail from: , and then press ENTER.
> >> >
> >> > e. Type rcpt to: , and then press ENTER.
> >> >
> >> > f. Type "quit" (without the quotation marks), and then press ENTER two
> >> > times to close the connection to the server and leave the Telnet
> session
> >> > running.
> >> >
> >> > For more information about these 6 steps, please refer to the
> following
> >> > article.
> >> >
> >> > XFOR: Telnet to Port 25 of IMC to Test IMC Communication:
> >> > http://support.microsoft.com/?id=153119
> >> >
> >> > Please let me know the result and capture a screen shot if there is
> any
> >> > error during this process and attach it in your reply.
> >> >
> >> > 2. As you mentioned, you are using the POP3 Connector to retrieve
> inbound
> >> > emails, and using DNS to send outbound emails. To narrow down this
> issue,
> >> > please switch to forward to smarthost to deliver emails:
> >> >
> >> > To switch between using DNS and Smart Host, you can do the following
> steps:
> >> >
> >> > a. Open Exchange System Manager and expand the "Connectors" node.
> >> >
> >> > b. Right click "SmallBusiness SMTP connector" and choose Properties.
> >> >
> >> > c. On the General page, you can choose to use DNS or Forward to smart
> host
> >> > to send emails. If your customer is now using DNS to send emails, you
> can
> >> > choose to forward emails to the ISP's email server (smart host) and
> then
> >> > type the FQDN of the ISP's email server. If your ISP provides you the
> IP
> >> > address of their email server, for example, 12.34.56.78, you should
> type
> >> > the IP address as "[12.34.56.78]" (without the quotation marks) on the
> >> > connector's properties page.
> >> >
> >> > d. Expand to Servers\ServerName\Protocols\SMTP and restart the Default
> SMTP
> >> > Virtual Server. Then check if the issue disappears.
> >> >
> >> >
> >> > If the problem still persists, please help gather the following
> information
> >> > for analysis:
> >> >
> >> > 1. 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
.

Relevant Pages

  • Re: IP Blocker in SBS2003 exchange
    ... > What I was trying to explain in the telnet section was that I realise ... > the server is listening for connections on ports 110 and 25. ... > but he can connect to port 110. ... > well as another wireless broadband connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sharing Internet access with a XP box.
    ... > connects to the Internet via a dial-up ISDN connection. ... > run a telnet client on the XP machine and connect to it from the BSD ... supported on FreeBSD and you have to jump through a couple of hoops to ... or, more generically, a server. ...
    (freebsd-newbies)
  • Re: Sending to External Email Attachment Blocking
    ... I also tried changing the limits and the ... change was also shown via the telnet command. ... I’m pretty sure that the problem is with our server, ...
    (microsoft.public.exchange.admin)
  • Re: Email not reaching individul domain, but is reaching all others.
    ... I too have manged to make a connection to this server, ... If I Telnet jacklinks.info i get a message "Could not ... tracert uses ICMP which a lot of companies block. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange/ISA Questions
    ... SBS using port 25 for it's SMTP server has ... NAT is not working but this doesn't explain why the telnet to SBS:25 is not ... It should have a command equivalent ...
    (microsoft.public.backoffice.smallbiz2000)