Sending to gmail.com is failing for some users in domain

We have exchange 2010 running from SBS 2011.  Everything pretty much seems fine MX, DNS and reverse pointer records.  But when sending to gmail from one user in particular we are getting the error below.  Another user sent to the same gmail address and it worked properly.  The other issue is that our MX record is 1.2.3.101 not 1.2.3.97 (IP masked)  I'm not sure what to look at for this error.  Any suggestions?



mx.google.com gave this error:
[1.2.3.97 12] Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked. Please visit http://support.google.com/mail/bin/answer.py?hl=en&answer=188131 for more information. 9si30080279qam.38 - gsmtp

Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.
mcioffi209Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mcioffi209Author Commented:
Ok so it is more then just GMAIL.COM.

I'm having more issues with other users now.  

Is this a reverse DNS lookup issue?  It keeps retuning 1.2.3.97 instead of the configured 1.2.3.101.  My primary IP on the firewall is 1.2.3.97, but the address object for email is 1.2.3.101.  

IP Address 1.2.3.97 is listed in the CBL. It appears to be infected with a spam sending trojan, proxy or some other form of botnet.

It was last detected at 2014-11-13 10:00 GMT (+/- 30 minutes), approximately 4 hours, 30 minutes ago.

It has been relisted following a previous removal at 2014-11-11 17:08 GMT (1 days, 21 hours, 36 minutes ago)

This IP is, or is natting for, a Linux (or other UNIX-like) computer whose SSH facility is being used to tunnel email spam. This RackAid article and posting on Shaun Rowland's blog gives introductions on how SSH is being used, but it does not give the full details. This "geekblog" article shows how even a disabled userid can be used to spam by this mechanism.

This is Exchange 2010 running from Small Business Server 2011 not LINUX.
0
mcioffi209Author Commented:
I scanned the server with Stinger and nothing was found.  I'm getting desperate here as I cannot seem to find the issue.
0
DMTechGrooupCommented:
http://www.anti-abuse.org/multi-rbl-check/

http://mxtoolbox.com/blacklists.aspx

Start by running those blacklist test.

Does your IP or domain show up on any list?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

mcioffi209Author Commented:
I used MXToolbox and did find the primary IP address of the location, 1.2.3.97 as black listed.  What it makes sense that the outgoing email from the office is coming up as 1.2.3.97 as that is the first ip address in the static range and that is the address of the firewall primary wan.

The MX record uses 1.2.3.101.  

I blocked all port 25 traffic from the office, except for the mail server.  I then set up a trace on the firewall and found a machine on the network sending email.  I need to clean that machine out, but how can I speed removal from gmail?  They send to gmail addresses and aol a lot so this is important.


I have requested removal from the CBL list it was on already.
0
DMTechGrooupCommented:
Once you are off the list it is pretty quick but can take up to 24 hours.  Its probably a good idea to keep the block on the email for port 25.

Just for extra protection I searched out and found https://spamwall.com/outbound_filtering.html and we decided that the 30 a month was worth the extra protection to ensure our email was clean from our email server.

Just to say it incase.. we are not part of spamwall, we are an actual customer and they have not asked us to endorse or recommend their product.
0
mcioffi209Author Commented:
In my case it is/was due to a machine in the network sending rouge email.  I need to clean that machine, but I will probably keep the block on for awhile just in case, as you suggested.

Would that product help me this situation?
0
DMTechGrooupCommented:
Well it can make things move quicker now.. but if your exchange sent all mail to them to be checked then sent out your mail would not be blocked by IP as it would come from the scanning company IP which has a great reputation as far as not sending spam so they arent blocked.
0
mcioffi209Author Commented:
Setting the packet capture on the firewall showed me the "bad" machine so I can focus on cleaning it up.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.