Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 464
  • Last Modified:

Relay Exchange Server 2003

Help:
My exchange server will not send out emails from a internal server.  I have a applicataion that converts our invoices to a PDF and then send them using SMTP.  THis was working but recently I updateed our firewall and now my exchange server is rejecting these emails.  I have added the server IP address that is converting the invoices to a PDF in my exchange server to allow rellay from this IP address, but it is still rejecting these emails.
IE
Error: Sending to SMTP Server Failed: (48): Setting TO failed.
550 5.7.1 Unable to relay for penni@blue.edu
  Invoice No  0905793   BLUE CLIFF CAREER COLLEGE        
Error: Sending to SMTP Server Failed: (48): Setting TO failed.
550 5.7.1 Unable to relay for penni@blue.edu
I need a bit of direction, if someone can chime in and present outside point of view....

I this rejection becasue of the server the email is sending to or my exchange server.....?
0
Scott Johnston
Asked:
Scott Johnston
1 Solution
 
Schnell SolutionsSystems Infrastructure EngineerCommented:

How many Exchange servers you have?

How you delivery the emails to the Internet, do you use an equipment or are they delivery directly from the Exchange server?

0
 
Sikhumbuzo NtsadaCommented:
What firewall are you using - when you say updated did you change rules for your Exchange?
0
 
Suliman Abu KharroubIT Consultant Commented:
What are the updates you did on the firewall ? are the two servers hosted in the same network subnet ?
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
XCONBLRCommented:
This does not looks like an Exchange generated NDR.
Try to do a telnet from the IP address from where your application is submitting an email to the Exchange server on port 25.

try giving the following commands.
ehlo
mail from: test@test.com
rcpt to: <one of your external email address like yahoo adress or gmail address>
data
Subject: test

Test.
.

Check if the above commands is getting accepted by the Exchange server. - If it is accepted, your Exchange is fine.
If it is accepted, log on to your Exchange box and do a telnet to the MX record of the domain for which you are submitting the email to from your application.
Try following the same set of commands except that in the rcpt to: provide the email address to which the application sends emails to.
Check what is going on with it.
0
 
Scott JohnstonSystems ConsultantAuthor Commented:
I have done this test and it works from every server.....Any other ideas?
0
 
Scott JohnstonSystems ConsultantAuthor Commented:
PS I have a SonicWall firewall solution...
0
 
XCONBLRCommented:
Could you track your messages being sent from the Application through your server and see what is the stage at which  the message is getting an NDR? I am pretty sure that the server is not generating it, but could you confirm?
0
 
Scott JohnstonSystems ConsultantAuthor Commented:
My server is hung...It seems that I am relaying emails and have worked today to stop them but I still find that I am comming up as a relaying email server.
I used DNSGoodies to test and the results are:
220 BIOMAIL.corp.biotone.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.4675 ready at Thu, 8 Sep 2011 14:33:38 -0700
>> HELO 192.168.5.220
<< 250 BIOMAIL.corp.biotone.com Hello [208.82.183.220]
 
--------------------------------------------------------------------------------
>> MAIL FROM:<spammer@192.168.5.220>
<< 250 2.1.0 spammer@192.168.5.220....Sender OK
 >> RCPT TO:<spammee@64.73.243.238>
<< 550 5.7.1 Unable to relay for spammee@64.73.243.238
 >> RSET
<< 250 2.0.0 Resetting
 
--------------------------------------------------------------------------------
>> MAIL FROM:<spammer@192.168.5.220>
<< 250 2.1.0 spammer@192.168.5.220....Sender OK
 >> RCPT TO:<"spammee@64.73.243.238">
<< 250 2.1.5 "spammee@64.73.243.238"@biotone.com

So I have verfioed that I have Relaying turned off ..

I have these NDR in my application log...
Event Type:      Error
Event Source:      MSExchangeTransport
Event Category:      NDR
Event ID:      3030
Date:            9/8/2011
Time:            2:31:30 PM
User:            N/A
Computer:      BIOMAIL
Description:
A non-delivery report with a status code of 4.0.0 was generated for recipient rfc822;whocare2852@yahoo.com.tw (Message-ID  <ESAGCJXVUVBWQKKRPBTST.ECXUUZmatthewdean@yahoo.ca>).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
----------------------------------------

I also am getting this type of message:
Event Type:      Error
Event Source:      MSExchangeTransport
Event Category:      NDR
Event ID:      3018
Date:            9/8/2011
Time:            2:40:13 PM
User:            N/A
Computer:      BIOMAIL
Description:
A non-delivery report with a status code of 5.4.0 was generated for recipient rfc822;morris_tseng@a-chance.com.tw (Message-ID  <e1ff09ffe3f6469bb4036de9c2e52bce@fbd52300a3494c5d83236fa4496512f5>).  
Causes: This message indicates a DNS problem or an IP address configuration problem  
Solution: Check the DNS using nslookup or dnsq. Verify the IP address is in IPv4 literal format.
For more information, click http://www.microsoft.com/contentredirect.asp.
Data:
0000: ef 02 04 c0               ï..À

pLEASE ADVISE...  



Here is my smtp setup and I am not sure this is setup correctly....
0
 
Scott JohnstonSystems ConsultantAuthor Commented:
After much tweeking, I rebuilt the SMPT connector and reset the setting in exchange and it seems to be fixed.  Thank you for all your support.  IU think my conector had been attacked and or compromised.  Since I have reuilt the connector no more problems.
0
 
Scott JohnstonSystems ConsultantAuthor Commented:
My solution fixed the problem.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now