5.5.0 smtp;550 Authentication required

WINDOWS SERVER

    Sponsored Links

    Next

  • 1. Exchange SP2 - no autoupdate?
    I just realized one sbs server at a client's location isn't running exchange sp2 yet. I can't remember installing it on the others but this is the only one without it.. Is SP2 for exchange supposed to come as an auto update or only manually? Additionally, are there any specific checkpoints required to install Exchange SP2 on SBS 2003 Premium? Does it require a reboot? Keven.
  • 2. Event ID 529, NTLMSSP error from a foreign computer
    My client has MS Windows SBS 2003 and the following event is logged in the Security log -- Event Source: Security Event Category: Logon/Logoff Event ID: 529 Date: 5/5/2008 Time: 9:53:31 AM User: NT AUTHORITY\SYSTEM Computer: SBP01 Description: Logon Failure: Reason: Unknown user name or bad password User Name: OCW2K3$ Domain: OTCARR Logon Type: 3 Logon Process: NtLmSsp Authentication Package: NTLM Workstation Name: OCW2K3 Caller User Name: - Caller Domain: - Caller Logon ID: - Caller Process ID: - Transited Services: - Source Network Address: - Source Port: - This appears to be a failed login attempt from the system account of a computer called "OCW2K3". There is no computer by this name on the local network. This error occured several times over the span of 4 days. Questions: 1.) Is it correct to say that this is a hacking attempt from across the internet? 2.) If it is, what kind of login attempt would it be? I've tried fake logins to the SBS server via Remote Web Workplace, VPN, and OWA, but have not been able to reproduce this error message. Thanks. Matt

5.5.0 smtp;550 Authentication required

Postby cmplbms » Thu, 31 Aug 2006 14:14:02 GMT

Recently we have began having a rash of mail bounces with the following 
information presented:

There was a SMTP communication problem with the recipient's email server.  
Please contact your system administrator.

<ourcompanyname.com #5.5.0 smtp;550 Authentication required.

This server has been operating without problems for over a year.  The domain 
is not blacklisted and I have verified configurations using 
www.dnsreport.com.  Exchange is configured to use DNS for sending mail.  Is 
this the issue?  We use business class Road Runner.  Should I be forwarding 
mail to them instead of using DNS?  

To my knowledge, the server is patched with all of the latest patches and 
all systems use Symantec Antivirus Corp.

I have done a great deal of searching but cannot find a concise answer.

Any help would be appreciated.


RE: 5.5.0 smtp;550 Authentication required

Postby v-chacez » Fri, 01 Sep 2006 18:39:09 GMT

i,

Thank you for posting here.

According your description, I understand you encountered 550 NDR when
sending emails?

In order to get a clear picture on this issue, please let me know the
following questions:
Does the issue occur on certain users or all users?

Does this issue occur when you sending to internal recipients? Or external
recipients?

Does this issue occur when you send to all external domains or just some
specific domains?

I would like to suggest you perform the following steps to narrow down this
issue.


Step 1:
=====================

1. On the Windows taskbar click the Start button, point to Programs, point
to Microsoft Exchange, and then click System Manager

2. In System Manager dialog box, expand the Servers container, expand the
Protocols container, and then expand the SMTP container.

3. Right click Default SMTP Virtual Server, and in the Properties dialog
box, click the Access tab.

4. In the Access dialog box, under Access control, click the Authentication
button.

5. Under Select acceptable authentication method for this resource, click
to select the Anonymous Access checkbox, and then click OK.
NOTE: This setting allows any user to send mail from this Exchange server
computer.

Step 2: Check the PTR record
=====================

Verify the PTR records for the Exchange SMTP domain from the following
website: http://www.dnsstuff.com/

Step 3: Using Telnet
===============
Try to telnet to the remote mailer directly to test the issue. Detailed
steps are documented in the following article:

153119 XFOR: Telnet to Port 25 to Test SMTP Communication
http://support.microsoft.com/?id=153119

Step 3: Bypassing DNS
==================
Configure the SMTP connector to deliver message directly to the remote mail
server without DNS. To do so, see the following article:

285863 How to Bypass DNS Name Resolution to Test SMTP Mail Flow to Remote
http://support.microsoft.com/?id=285863

In addition, please collect the following information to me so that I can
find more information about the issue.


1 Collect the Message Tracking info to me.

a) Enable Message Tracking on. For more information, please refer to
the following KB article.

257265 XCON: General Troubleshooting for Exchange 2000 Transport
Issues
http://support.microsoft.com/?id=257265
b) Please send a message to reproduce the issue.
c) Search for the message in Message Tracking centre.
d) Double click to open it, make a screenshot of Message Tracking center
and send it to me as well.

3. Use the WinRoute tool below to collect the routing information to me.

http://www.microsoft.com/downloads/details.aspx?familyid=c5a8afbf-a4da-45e0-
adea-6d44eb6c257b&displaylang=en

4. Configure diagnostic logging on the Exchange 2003 server.

1) Start Exchange System Manager.

2) Expand "Administrative Groups", expand "First Administrative Group",
and then expand "Server".

3) Right-click the Exchange Server that is listed under "Servers", and
then click "Properties".

4) Click the "Diagnostics Logging" tab, and then click to select the
"MSExchangeTransport" box under the "Services" box.

5) Set the "Logging level" of each Category to "Maximum".

6) Click "OK".

After you reproduce the issue, send the Event Viewer logs to me.

Step 1: Click Start, click Run, and then type "eventvwr" (without the
quotation
marks), cli

Re: 5.5.0 smtp;550 Authentication required

Postby Steve Foster [SBS MVP] » Fri, 01 Sep 2006 23:18:13 GMT




You may be being redirected to a RoadRunner mail server automatically - 
and then blocked because it requires authentication.

I'd speak to them to find out if they are blocking outbound SMTP. It's not 
an uncommon thing for ISPs to start doing unannounced.

-- 
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Similar Threads:

1.#5.1.0 smtp;550 5.1.0 Authentication required

I'm a novice MCSE. On the side I'm supporting a small network (SBS - 3 
workstations - Exchange).  The small network was built nicely by a networking 
company who became too expensive for my client, who is a friend, who asked me 
to support it.

The first Thing (and only thing) I've done was changed the Administrator 
Password on the server.

Now I've had reports of this error when users try to reply to emails.

 The e-mail address could not be found. Perhaps the recipient moved to a 
different e-mail organization, or there was a mistake in the address. Check 
the address and try again.
  <mydomain.com #5.1.0 smtp;550 5.1.0 Authentication required



They can email successfully if they type out the email address, but it will 
not work when they simply hit reply and send.

Does anyone know what I can try to do to fix this?

Thanks

Joel B



2.550 5.7.1 Authentication Required Error (Verizon DSL)

As noted earlier, this just came out of the blue. No settings were
changed that I know of. I can't send anything, but mail is received
just fine.
     Has anyone had this happen and do you know of a cure?
Mozilla Thunderbird has no problems sending.
     Help much appreciated.
          Frank

3.550 Authentication required

Just today when trying to send email I started receiving this message,
I contacted my IP, Peoplepc and they say that I need a code to correct
this?

Delivery has failed on the enclosed message for the following reasons
reported either by

the mail delivery system on the mail relay host or by the local TCP/IP
transport module:

550 Authentication required



Thanks,

Tena



4.SMTP communication problem smtp;550 - emails bouncing back

Recently my customer has had emails bouncing back with the error:
There was a SMTP communication problem with the recipient's email server. 
Please contact your system administrator.
<Customer.com #5.5.0 smtp;550-(Customer.com) [1.2.3.4] is currently not 
permitted to relay through>

I do not have a MX record pointing at the Exchange server on the SBS2003R2.
I do not have a smart host setup at this time.
We do have a static IP on the router for the outside and I do have access to 
our dns records at our host.
What would be the proper way to deal with this issue?
Should I do something with MX record and dns?  If so how?
or
Should I setup a smart host to relay from the ISP (Verizon)?

Below is information about our system and information from some of the 
bounced emails.   Names and IP's were changed to protect the innocent.
Any help or advice would be appreciated.

Randy
Bewildered IT-Guy for the Customer



Customer's outside IP = 1.2.3.4 (changed for this post)
Customer;s server name = Server
Customer's SBS domain name = TheCustomer.local
Customer's Outside FQDN = Customer.com
-----------------------------------
Your message

  To:      John Doe
  Subject: Customer Irrigation
  Sent:    Wed, 12 Mar 2008 14:46:38 -0400

did not reach the following recipient(s):

 XXXX@XXXXX.COM  on Wed, 2 Apr 2008 08:38:12 -0400
    There was a SMTP communication problem with the recipient's email 
server.  Please contact your system administrator.
    <Customer.com #5.5.0
smtp;550-static-1-2-3-4.phil.east.verizon.net (Customer.com) [1.2.3.4]>

[details.txt]
Reporting-MTA: dns; server.TheCustomer.local

Final-Recipient: RFC822;  XXXX@XXXXX.COM 
Action: failed
Status: 5.5.0
X-Supplementary-Info: <Customer.com #5.5.0 
smtp;550-static-1-2-3-4.phil.east.verizon.net (Customer.com) [1.2.3.4]>
X-Display-Name:  XXXX@XXXXX.COM 
-------------------------------------

Your message

  To:       XXXX@XXXXX.COM ;  XXXX@XXXXX.COM ; Colon, Julio E [CK]
  Subject: Dissatisfied Customer
  Sent:    Mon, 31 Mar 2008 13:05:41 -0400

did not reach the following recipient(s):

 XXXX@XXXXX.COM  on Wed, 2 Apr 2008 08:38:51 -0400
    There was a SMTP communication problem with the recipient's email 
server.  Please contact your system administrator.
    <Customer.com #5.5.0
smtp;550-static-1-2-3-4.phil.east.verizon.net (Customer.com) [1.2.3.4]> 
 XXXX@XXXXX.COM  on Wed, 2 Apr 2008 08:38:51 -0400
    There was a SMTP communication problem with the recipient's email 
server.  Please contact your system administrator.
    <Customer.com #5.5.0
smtp;550-static-1-2-3-4.phil.east.verizon.net (Customer.com) [1.2.3.4]> 
 XXXX@XXXXX.COM  on Wed, 2 Apr 2008 08:38:51 -0400
    There was a SMTP communication problem with the recipient's email 
server.  Please contact your system administrator.
    <Customer.com #5.5.0
smtp;550-static-1-2-3-4.phil.east.verizon.net (Customer.com) [1.2.3.4]>

[details.txt]
Reporting-MTA: dns; server.TheCustomer.local

Final-Recipient: RFC822;  XXXX@XXXXX.COM 
Action: failed
Status: 5.5.0
X-Supplementary-Info: <Customer.com #5.5.0 
smtp;550-static-1-2-3-4.phil.east.verizon.net (Customer.com) [1.2.3.4]>
X-Display-Name:  XXXX@XXXXX.COM 

Final-Recipient: RFC822;  XXXX@XXXXX.COM 
Action: failed
Status: 5.5.0
X-Supplementary-Info: <Customer.com #5.5.0 
smtp;550-static-1-2-3-4.phil.east.verizon.net (Customer.com) [1.2.3.4]>
X-Display-Name:  XXXX@XXXXX.COM 

Final-Recipient: RFC822;  XXXX@XXXXX.COM 
Action: failed
Status: 5.5.0
X-Supplementary-Info: <Customer.com #5.5.0 
smtp;550-static-1-2-3-4.phil.east.verizon.net (Customer.com) [1.2.3.4]>
X-Display-Name:  XXXX@XXXXX.COM 
-----------------------------------------

Your message did not reach some or all of the intended recipients.
      Subject:  Customer
      Sent:     3/30/2008 1:57 PM
The following recipient(s) cannot be reached:
      ' XXXX@XXXXX.COM ' on 3/30/2008 1:57 PM
            There was a SMTP communication problem with the recipient's 
email server.  Please contact your system administrator.
            <Customer.com #5.5.0 smtp;550-(Customer.com) [1.2.3.4] is 
currently not permitted to relay through>


5.Error: #5.7.1 smtp;550 5.7.1 Access denied

6. smtp;550 5.7.1 Unable to relay for

7. SMTP error 550

8. SMTP error 550 when sending to Earthlink



Return to WINDOWS SERVER

 

Who is online

Users browsing this forum: No registered users and 69 guest