Re: MSExchangeTransport Errors
- From: "Jeff Teel" <jdteel@xxxxxxxxxxxx>
- Date: Wed, 16 Nov 2005 07:58:37 -0500
Hi Nathan
Thanks for responding to my post.
I'll go through your questions in the order that you have asked them.
1. Not really a question from you but is logging for Exchange Transport SMTP
on by default in SBS. It seems that I remember turning it on but can't
recall for sure? I think I'll leave it in for now just to see what activity
there is from those trying to "relay" through my mail server.
2. Then only Trend application that is installed is CSM v3.0
3. Authentication is set as you have stated.
4. I have not seen any other problems with Exchange or noticed any issues
with sending/receiving mail internally or externally.
Thanks
Jeff
""Nathan Liu [MSFT]"" <v-natliu@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:JlwCaKm6FHA.3036@xxxxxxxxxxxxxxxxxxxxxxxx
> Hello Jeff,
>
> Thank you for posting in the SBS newsgroup.
>
> According to your description, I understand that you received the Event
> Errors "Event Source: MSExchangeTransport, Event ID: 7010" in the SBS 2003
> Server. If I have misunderstood the problem, please don't hesitate to let
> me know.
>
> To isolate this issue, please answer and perform the following questions
> and steps:
>
> 1. >> Description: This is an SMTP protocol log for virtual server ID 1,
> connection #5. The
> client at "220.137.106.178" sent a "rcpt" command, and the SMTP server
> responded with "550 5.7.1
> Unable to relay for a231.b233@xxxxxxxxxxxxx ". The full command sent was
> "rcpt TO:<a231.b233@xxxxxxxxxxxxx>". This will probably cause the
> connection to fail.
>
> It seems that someone was trying to relay through your SBS server. The
> fact
> you get that message shows you are not relaying :-)
>
> If you don''t want the events to be logged, you can follow the steps
> below:
>
> A. In Exchange System Manager, right-click your server and click
> Properties.
> B. On the Diagnostic Logging tab, click MSExchangeTransport in the left
> pane.
> C. Click SMTP Protocol in its categories, and select the None logging
> level.
>
> 2. Do you have Interscan from Trend Micro running on the SBS server? I saw
> some cases that indicated the events might be logged if you have Interscan
> running.
>
> Additional information:
>
> 324958 HOW TO: Block Open SMTP Relaying and Clean Up Exchange Server SMTP
> Queues on SBS
> http://support.microsoft.com/?id=324958
>
> 3. >> Description: This is an SMTP protocol log for virtual server ID 1,
> connection #2. The
> client at "4.40.64.58" sent a "xexch50" command, and the SMTP server
> responded with
> "504 Need to authenticate first ". The full command sent was "xexch50
> 1036
> 2". This will probably cause the connection to fail.
>
> Please verify that Integrated Windows Authentication is enabled on the
> SMTP
> virtual servers on the Exchange Server computers in your organization. If
> it is not enabled, follow these steps:
>
> a. In Exchange System Manager, expand "Administrative Groups", expand
> "Servers", expand "<Exchange Server Name>", expand "Protocols", and then
> expand "SMTP".
>
> b. Right-click the SMTP virtual server. (By default, this is named Default
> SMTP Virtual Server.)
>
> c. Click "Properties", click the "Access" tab, and then click
> "Authentication". Make sure that only "Anonymous access", "Basic
> authentication (Password is sent in clear text)" and " "Integrated Windows
> Authentication" check boxes are selected.
>
> Detailed information:
>
> How to troubleshoot the "504 need to authenticate first" SMTP protocol
> error
> http://support.microsoft.com/?id=843106
>
> To have a detailed investigation of your SBS server, please collect
> following information.
>
> 1. Do you have any issue when send/receive internal/external email in the
> SBS network?
>
> 2. Is any other issue related with exchange you are experiencing?
>
> 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.
>
>
> --------------------
>>From: "Jeff Teel" <jdteel@xxxxxxxxxxxx>
>>Subject: MSExchangeTransport Errors
>>Date: Tue, 15 Nov 2005 06:59:01 -0500
>>Lines: 52
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>>X-RFC2646: Format=Flowed; Original
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>>Message-ID: <#l2O5vd6FHA.1184@xxxxxxxxxxxxxxxxxxxx>
>>Newsgroups: microsoft.public.windows.server.sbs
>>NNTP-Posting-Host: 206.230.187.18
>>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:222404
>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>
>>The past three days I've been seeing a few errors from MSExchangetransport
>>in category SMTP Protocol. Here are the two different messages that I'm
>>seeing from this category with one stating that it is unable to relay the
>>message and the other needing to authenticate first. Is there any advice
> on
>>cleaning these errors up? There have been five of these over the last four
>>days.
>>
>>SIBS 2003 SPA
>>Exchange 2003 SPA
>>
>>Thanks
>>Jeff
>>
>>
>>Event Type: Error
>>Event Source: MSExchangeTransport
>>Event Category: SMTP Protocol
>>Event ID: 7010
>>Date: 11/15/2005
>>Time: 4:51:16 AM
>>User: N/A
>>Computer: SBSERVER
>>Description:
>>This is an SMTP protocol log for virtual server ID 1, connection #5. The
>>client at "220.137.106.178" sent a "rcpt" command, and the SMTP server
>>responded with "550 5.7.1
>>Unable to relay for a231.b233@xxxxxxxxxxxxx ". The full command sent was
>>"rcpt TO:<a231.b233@xxxxxxxxxxxxx>". This will probably cause the
>>connection to fail.
>>
>>For more information, click http://www.microsoft.com/contentredirect.asp.
>>
>>
>>Event Type: Error
>>Event Source: MSExchangeTransport
>>Event Category: SMTP Protocol
>>Event ID: 7010
>>Date: 11/14/2005
>>Time: 10:25:54 AM
>>User: N/A
>>Computer: SBSERVER
>>Description:
>>This is an SMTP protocol log for virtual server ID 1, connection #2. The
>>client at "4.40.64.58" sent a "xexch50" command, and the SMTP server
>>responded with
>>"504 Need to authenticate first ". The full command sent was "xexch50
> 1036
>>2". This will probably cause the connection to fail.
>>
>>For more information, click http://www.microsoft.com/contentredirect.asp.
>>
>>
>>
>>
>
.
- Follow-Ups:
- Re: MSExchangeTransport Errors
- From: "Nathan Liu [MSFT]"
- Re: MSExchangeTransport Errors
- Prev by Date: RE: Remote Web Workplace Connect to client computer error
- Next by Date: Re: Error when installing Monitor SBS 2003
- Previous by thread: Re: Newbie Sharepoint services question
- Next by thread: Re: MSExchangeTransport Errors
- Index(es):
Relevant Pages
|