• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Relaying issues

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Exchange 2003 SBS >> Relaying issues Page: [1]
Login
Message << Older Topic   Newer Topic >>
Relaying issues - 9.Dec.2009 5:25:56 PM   
Ambictus

 

Posts: 18
Joined: 23.Nov.2005
Status: offline
Ok, so for the last 3 days or so I've been experiencing a problem with my SBS 2003 server. I've been getting a lot of messages bounced back stating that relaying is denied. After a lot of searching and attempting multiple fixes I believe I've discovered the problem, but am unsure of how to fix it.

First let me state that I'm completely baffled as to why it started happening. I have made no changes in IP or DNS nor have I patched the server or changed the config.

It seems that my server is either attempting to deliver messages to the wrong servers or is simply attempting to use those servers to relay our messages to the proper server. The issue only occurs when a message is sent to multiple recipients.

So I believe our server opens a connection to the first recipients server and simply attempts to hand off the messages for all recipients. Below are a couple of examples of the errors from the event viewer.

This is an SMTP protocol error log for virtual server ID 1, connection #61. The remote host "X.X.X.X", responded to the SMTP command "rcpt" with "550-5.1.1 The email account that you tried to reach does not exist. Please try  550-5.1.1 double-checking the recipient's email address for typos or  550-5.1.1 unnecessary spaces. Learn more at                               550 5.1.1 http://mail.google.com/support/bin/answer.py?answer=6596 2si525366qyk.111  ". The full command sent was "RCPT TO:<X@X.com>  ".  This will probably cause the connection to fail.


This is an SMTP protocol error log for virtual server ID 1, connection #62. The remote host "X.X.X.X", responded to the SMTP command "rcpt" with "550 5.7.1 Relaying denied  ". The full command sent was "RCPT TO:<X@X.com>  ".  This will probably cause the connection to fail.
Post #: 1
RE: Relaying issues - 10.Dec.2009 5:20:12 PM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
Are you sure the bounces are being caused by legitimate outbound messages?  If you attempt to send an outbound message to yahoo.com, does it bounce?

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to Ambictus)
Post #: 2
RE: Relaying issues - 11.Dec.2009 2:26:55 PM   
Ambictus

 

Posts: 18
Joined: 23.Nov.2005
Status: offline
Yes, I can verify that the e-mails being bounced are legitimate. It's happening to all of my users(me included). It seems that it may be some kind of corruption in the database. I defragmented the database and ran "isinteg -s ServerName -fix -test alltests" which alleviated the problem but only for a very short period of time. I may just use exmerge and create a new database over the weekend.

(in reply to uemurad)
Post #: 3
RE: Relaying issues - 11.Dec.2009 2:52:40 PM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
Do you send outbound messages directly to the recipient domains, or do you send to a smarthost?

Do you have SMTP logging enabled?  If so, what does it say about the outbound attempts?

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to Ambictus)
Post #: 4
RE: Relaying issues - 14.Dec.2009 11:27:07 AM   
Ambictus

 

Posts: 18
Joined: 23.Nov.2005
Status: offline
We aren't using a smarthost though it almost seems my exchange server thinks we are.

As for the log file which are you looking for? Windows\System32\LogFiles or Exchsrvr\SERVER.log?

(in reply to uemurad)
Post #: 5
RE: Relaying issues - 14.Dec.2009 12:35:15 PM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
By default the files are named EXyymmdd.log where yymmdd is the current date.  The enable/disable and location configurations are found in the Default SMTP Virtual Server settings.

There are two places you can define a smarthost.  One is in the Default SMTP Virtual Server as mentioned above, the other is in an SMTP connector.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to Ambictus)
Post #: 6
RE: Relaying issues - 14.Dec.2009 12:46:58 PM   
Ambictus

 

Posts: 18
Joined: 23.Nov.2005
Status: offline
16:44:05 207.97.242.51 EHLO - 250
16:44:05 207.97.242.51 MAIL - 250
16:44:05 207.97.242.51 RCPT - 250
16:44:05 207.97.242.51 DATA - 250
16:44:05 207.97.242.51 QUIT - 240

That's from the log.

Smart host is not setup. I've checked both places. If you're looking for info from a different log let me know.

(in reply to uemurad)
Post #: 7
RE: Relaying issues - 14.Dec.2009 12:51:57 PM   
Ambictus

 

Posts: 18
Joined: 23.Nov.2005
Status: offline
I realize how much of a failure that log is. Give me just a moment and I'll post a better log entry.

(in reply to Ambictus)
Post #: 8
RE: Relaying issues - 14.Dec.2009 12:53:28 PM   
Ambictus

 

Posts: 18
Joined: 23.Nov.2005
Status: offline
2009-12-14 17:50:15 10.10.10.23 [10.10.10.23] SMTPSVC1 LOVEMAIL 10.10.10.254 0 EHLO - +[10.10.10.23] 250 0 308 18 0 SMTP - - - -
2009-12-14 17:50:15 10.10.10.23 [10.10.10.23] SMTPSVC1 LOVEMAIL 10.10.10.254 0 MAIL - +FROM:<doug@lovecomm.net> 250 0 42 38 0 SMTP - - - -
2009-12-14 17:50:15 10.10.10.23 [10.10.10.23] SMTPSVC1 LOVEMAIL 10.10.10.254 0 RCPT - +TO:<dugssmtp@excite.com> 250 0 32 29 0 SMTP - - - -
2009-12-14 17:50:15 10.10.10.23 [10.10.10.23] SMTPSVC1 LOVEMAIL 10.10.10.254 0 RCPT - +TO:<xxzone@gmail.com> 250 0 29 26 0 SMTP - - - -
2009-12-14 17:50:15 10.10.10.23 [10.10.10.23] SMTPSVC1 LOVEMAIL 10.10.10.254 0 RCPT - +TO:<bhansen@wavelink.com> 250 0 33 30 0 SMTP - - - -
2009-12-14 17:50:15 10.10.10.23 [10.10.10.23] SMTPSVC1 LOVEMAIL 10.10.10.254 0 DATA - +<4B267AB2.4020702@lovecomm.net> 250 0 115 424 0 SMTP - - - -
2009-12-14 17:50:15 10.10.10.23 [10.10.10.23] SMTPSVC1 LOVEMAIL 10.10.10.254 0 QUIT - [10.10.10.23] 240 32 66 4 0 SMTP - - - -
2009-12-14 17:50:15 209.85.221.68 OutboundConnectionResponse SMTPSVC1 LOVEMAIL - 25 - - 220+mx.google.com+ESMTP+42si3783493qyk.6 0 0 40 0 78 SMTP - - - -
2009-12-14 17:50:15 209.85.221.68 OutboundConnectionCommand SMTPSVC1 LOVEMAIL - 25 HELO - mail.lovecomm.net 0 0 4 0 78 SMTP - - - -
2009-12-14 17:50:15 209.85.221.68 OutboundConnectionResponse SMTPSVC1 LOVEMAIL - 25 - - 250+mx.google.com+at+your+service 0 0 33 0 188 SMTP - - - -
2009-12-14 17:50:15 209.85.221.68 OutboundConnectionCommand SMTPSVC1 LOVEMAIL - 25 MAIL - FROM:<doug@lovecomm.net> 0 0 4 0 188 SMTP - - - -
2009-12-14 17:50:15 209.85.221.68 OutboundConnectionResponse SMTPSVC1 LOVEMAIL - 25 - - 250+2.1.0+OK+42si3783493qyk.6 0 0 29 0 266 SMTP - - - -
2009-12-14 17:50:15 209.85.221.68 OutboundConnectionCommand SMTPSVC1 LOVEMAIL - 25 RCPT - TO:<bhansen@wavelink.com> 0 0 4 0 266 SMTP - - - -
2009-12-14 17:50:19 209.85.221.68 OutboundConnectionResponse SMTPSVC1 LOVEMAIL - 25 - - 550-5.1.1+The+email+account+that+you+tried+to+reach+does+not+exist.+Please+try 0 0 78 0 3407 SMTP - - - -
2009-12-14 17:50:19 209.85.221.68 OutboundConnectionCommand SMTPSVC1 LOVEMAIL - 25 RSET - - 0 0 4 0 3407 SMTP - - - -
2009-12-14 17:50:19 209.85.221.68 OutboundConnectionResponse SMTPSVC1 LOVEMAIL - 25 - - 250+2.1.5+Flushed+42si3783493qyk.6 0 0 34 0 3516 SMTP - - - -
2009-12-14 17:50:19 209.85.221.68 OutboundConnectionCommand SMTPSVC1 LOVEMAIL - 25 QUIT - - 0 0 4 0 3516 SMTP - - - -

(in reply to Ambictus)
Post #: 9
RE: Relaying issues - 14.Dec.2009 1:39:26 PM   
Ambictus

 

Posts: 18
Joined: 23.Nov.2005
Status: offline
Also, I'm not sure if this will help at all, but we have 2 virtual SMTP connectors. One is for internal use and is on port 25. This connector is locked down so that only internal addresses and our spam filtering service can connect to it. The other is on port 2515 and is open for our users that send e-mails from home etc.

We have it setup this way because spammers were bypassing our spam service and sending directly to our server's IP.

The issue exists no matter which virtual server the mail is sent to.

(in reply to Ambictus)
Post #: 10
RE: Relaying issues - 17.Dec.2009 12:51:23 AM   
fa2lerror

 

Posts: 8
Joined: 16.Dec.2009
Status: offline
Have you used MXTOOLBOX.COM? this is a sweet site that has proven/disproven open relaying and have shut up ISP when they said my servers are open relays when in fact they were not. IF you do suspect a corrupt store then you can rename the existing priv1.edb & .stm along with associated log files (i think i have just moved the entire contents from the MDBDATA folder to a sub folder) and start exchange with no logs or stores. This will force exchange to create a new store and logs. That test cost me $495 on a MS incident to prove an issue was not database related. I wouldnt keep that database to long if the problem persists after. Id hate for you to have divergent data.

As far as spammers bypassing your spam service, dont know what service you use but if you are using PostINI or some sort of 3rd party prefilter who then forwards on to you, you can create firewall rules that only allow incoming SMTP from your provider. All other sources would be dropped.

(in reply to Ambictus)
Post #: 11

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> Exchange 2003 SBS >> Relaying issues Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter