Configuration: SBS2k3 with all latest fixes and updates, Server performance reports have providied a set of ongoing errors.  The sbs 2k3 server is just one of 3 servers on the local LAN but the exchange does not need to synch/update with any of the other servers. 

 

Problem: The log files have indicated that a large amount of RAM on the sbs2k3 server was has been used by the Store.exe and other applications.  I doubled the RAM (Now, 2 G) and the errors are even more frequent.  I suspect that the exchange server was being used as a spam relay.  I have reviewed and completed the changes as outlined in several KB articles.  The errors now are a few times a week (mostly at early morning hours 2-6 am).  

Error (event ID 7010)- MSExchangeTransport:  This is an SMTP protocol log for virtual server ID 1, connection #647. The client at "w.x.y.z" sent a "rcpt" command, and the SMTP server responded with "550 5.7.1 Unable to relay for someone@not.mine.domain ". The full command sent was "rcpt TO: <someone@not.mine.domain>". This will probably cause the connection to fail. For more information, click http://www.microsoft.com/contentredirect.asp.

 

The actual ip address was changed to w.x.y.z and the email address was change to "someone@not.mine.domain".  The IP/email addresses do not belong to any of my users or my domain.

Question:  What is this error and what does it mean?

Hi Ryan,

 

I think you have turned up the smtp logging, right? That error is actually telling you that your server is not being used as a relay.

About the RAM, did you also adjust the pagefile to 1 1/2 times the RAM? Have you applied SP1 for Exchange yet with the additional SBS 843539?

Hi Ryan,

increasing the memory will not help, exchange will try (and succeed ) to use as many ram as available. This is however by design: when other apps need it, the memory will be available again.

 

About the errors: could you please provide more info about the network setup as it may be related with the problem.

regards,

pim

 

The Virtual Memory setting is set to 4094 MB for the 2 Gig's of RAM on the system.  Exchange sp 1 is applied but I have not applied the 2k3 server sp.  I am waiting for the sbs 2k3 sp to be released. 

 

SMTP logging is turned on.  This was part of the configuration that was done with the alert and reporting wizard. 

 

So are you telling me that I have nothing to worry about?  If so, then why would other ISP's (verizon, AOL, etc) be rejecting emails sent from my users?

 

Thanks for your help.

Hi Ryan,

You should indeed wait with W2k3 SP1 till the SBS SP1 is released. I meant the 843539 patch which you will have to apply after SP1 for Exchange.

Are you using DNS for sending email? Setup another smtp connector and let that one go through smarthost for the AOL domain and other domains that are rejecting your email. Which ndr do you get from them?

Applied the 843539 patch.  Thanks- my users did not like the extra domain information required with OWA that this fixed as well. 

 
your Question: Are you using DNS for sending email? Not sure how to answer that.  I have DNS setup on the SBS for internal LAN DNS but forward the external DNS to my ISP.  The SMTP connector uses my internal IP and forwards it thru my dsl router as the gateway.  Did that help?

The NDR for the AOL email was:

Have a URL for the setup steps on the SMTP smarthost?  What is the reason for this change?

Hi Ryan,

 

In the properties of the SMTP Connector you can check if you are using DNS or smarthost. If it is DNS, just create another SMTP connector, check the smarthost and fill in your ISP's mailserver. On the Address space tab, add the AOL.COM domain (and other domains that are having problems). All email with those domains will go through your ISP's mailserver in stead of straight via DNS.