Solved

Blacklisted

Posted on 2013-12-09
5
321 Views
Last Modified: 2013-12-09
We are being blacklisted by 9 different blacklist companies according to mxtoolbox.  They include; Barracuda, CBL, Choon, ivmSIP, LASHBACK, NIXSPAM, SPAMCOP, Spamhaus Zen, UCEPROTECTL1.  Not long after I discovered the problem this morning I had a user call and say their computer is basically under attack.  I have shut down the computer.  What is the best way for me to verify that it was this computer causing the issue?
0
Comment
Question by:PDIS
5 Comments
 
LVL 1

Expert Comment

by:Trancebolt
ID: 39706259
Very difficult... I have had this problem with a few domains/ips...

Its either someone in house doing mass mailers or your outbound security is low so people are spoofing your name.

Barracuda is often one that blocks me...
0
 
LVL 13

Expert Comment

by:Alexios
ID: 39706278
Hello
It is better to remove the HD, add it as a secondary drive to another PC and scan it with updated antivirus and antimalware software.
Some examples
http://www.microsoft.com/security_essentials/
http://www.malwarebytes.org/ 

Write down all possible threats that these programs will find and search them to a virus database. In their decription you will if any of them is causing spamming
0
 
LVL 1

Expert Comment

by:Trancebolt
ID: 39706282
VEry sound advice, but in my experience nothing  clears bugs out except reformatting and setting up from scratch =D
0
 

Author Comment

by:PDIS
ID: 39706290
I will reformat the computer before I put it back in use.  I'm just trying to verify that this computer is the culprit for us being blacklisted
0
 
LVL 19

Accepted Solution

by:
xterm earned 500 total points
ID: 39706328
If you have multiple PCs on a LAN that is using NAT behind one common gateway, then all your outbound emails will appear to originate from a single IP address and there is no way of knowing if the infected machine is the culprit.  Obviously, if the machine has a public static IP, then that will be the IP in the DNSBL listing, but I'm guessing that's not the case for you.

The best thing you can do is put an internal ACL on your switches/routers that denies all outbound SMTP (port 25/tcp) to any IP except for your actual Exchange/SMTP server(s).  This forces systems to relay instead of doing direct-to-MX, and then you can deploy controls on Exchange itself to limit outbound volume.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Utilizing an array to gracefully append to a list of EmailAddresses
Read this checklist to learn more about the 15 things you should never include in an email signature.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
how to add IIS SMTP to handle application/Scanner relays into office 365.

832 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question