Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How was this server relaying??

Status
Not open for further replies.

RNW2

Technical User
Feb 10, 2009
70
0
0
GB
Hi all,

Need a bit of advice\opinions.

I recently was asked to look at an Exchange 2003 server (actually an SBS2003 server but this is purely E2K related so thought best to post here) that was being used as a relay. External checks from places like MXToolbox showed that the server wasn't set up as an open relay so I jumped onto the server to have a look at how it's been configured.

First thing I checked was the queues and there were lots of spurious emails from random addresses going outbound to random addresses. Not good.

Next I checked the relay setup on the smtp vs and sure enough the server wasn't configured as an open relay but the person that had configured it had set it to allow relaying from all machines on the subnet and had left the "Allow all computers that successfully authenticate to relay, regardless of the list above" option checked.

That being the case I figured that a system on the network probably had an issue (Virus, malware, blah) and as the exchange server allowed it it was using it to relay all over the place. I changed the allowed relay IP addresses to the IP address of the exchange server (and 127.0.0.1 for good measure), removed the config that allowed the entire subnet to relay and then unchecked the "allow all computers that successfully....." and sure enough after deleting the built up SPAM queues no more random emails appeared in the queue.

Now here's the thing. I enabled logging on the smtp vs to identify the client IP addresses that were accessing the smtp vs so I could find out where the problem was. Once I checked this all the traffic appeared to be coming from external IP addresses. I didn't expect this at all. Can anyone explain??

The only thing I can think of is that the "allow all computers that successfully....." check box was the cause but I was under the impression that this was valid only for systems that had a valid computer account in AD. Am I wrong here??

I can post a selection of the smtp log file if anyone needs but just was seeking clarification.

Cheers all.

R
 
Outlook doesn't use SMTP in a domain joined environment. So you wouldn't see SMTP traffic coming from internal machines under normal circumstances. You should block SMTP at the firewall to only go OUT from your SBS box and nothing else.

In an SBS environment, you'd only see SMTP traffic to/from external addresses.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Hi,

Yeah Outlook uses MAPI but I didn't think that whatever it was that was sending the SPAM would have used outlook. I was thinking it'd be more crappy smtp engine that was using the exchange server to relay. What do you think?

Changing the firewall to only allow the SBS box out on 25 wouldn't have made any difference here as it was exchange box that was queueing all the SPAM and fireing it out.

Fair enough on the smtp logs. I just thought they might give an idea of where the traffic was coming from and how.
 
You could be getting hit by backskatter spam. Wouldn't surprise me. Some info on the Google machine about that.

As for the firewall, that's a best practices thing.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top