Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So found out my IP is blacklisted with Spamhaus because of a CBL blacklisting.
Quote:
IP Address xxx.xxx.xxx is listed in the CBL. It shows signs of being infected with a spam sending trojan, malicious link or some other form of botnet.
It was last detected at 2015-07-05 09:00 GMT (+/- 30 minutes), approximately 1 days, 13 hours ago.
Server Config
cPanel w/ Centos + CloudLinux 6
EXIM. suPHP. PHP 5.5.
'prevent 'nobody' user from sending..' enabled
Other Enabled Settings: CSF firewall (SMTP tweak enabled), CXS, suPHP, mail header tracking, 'nobody' prevented, max hourly at 100, and so many other tweaks in place.
In my EXIM config: "Send mail from account's dedicated IP address" is enabled. I've enabled DKIM and SPF on the below domains which I've masked for privacy reasons here only.
I emailed them couple weeks ago too about this.
Their response
Quote:
This definitely looks to be caused by your shared hosting:
Note: if you have received messages from us about IPSwitch/IMail before, please note that IPSwitch has finally implemented a workaround.
Please see below. We will no longer be perm-delisting IMail installations unless there's no alternative.
The CBL attempts to detect compromised machines in a number of ways based upon the email that the CBL's mail servers receive.
During this it tries distinguish whether the connections represent real mail servers by ensuring that each connection is claiming a plausible machine name for itself (via SMTP HELO), and not listing any IP that corresponds to a real mail server (or several mail servers if the IP address is a NAT firewall with multiple mail servers behind it).
xxx.xxx.33.191 was found to be using several different EHLO/HELO names during multiple connections on or about:
Note that the above list may include one or more names that are not fully qualified DNS names (FQDNs). Host names (ie: Windows node names) without a dot are not FQDNs.
RFC2821 requires that the HELO be either an IP address literal - an IP address surrounded by square brackets (ie: "[1.2.3.4]"), or a FQDN.
To resolve this you need to identify whether these are real names of your machines. If not:
- you have an open proxy used for spamming on that IP, or
- you have a NAT firewall, and one or more machines behind it
have an open proxy used for spamming.
- if all of the names above are IP addresses belonging to you
(without the square brackets) you probably using Blue Squirrel's
"Spam Sleuth" "Turing" feature. You will need to turn the
"Turing" feature off until you can get a patched version that
doesn't do this (identifies itself consistently).
If they are real names, you need to consider whether one or more of these machines are supposed to be sending email to the Internet (this implies that xxx.xxx.33.191 is a NAT firewall.)
If not, one or more machines on your internal network has an open proxy used for spamming.
If these are real names corresponding to real mail servers behind a NAT firewall, we strongly suggest that you configure your machines to have consistent fully qualified domain names, like:
mail01.<your domain>, mail02.<your domain>
This is usually done by setting the machine's node name to be one of the above, but sometimes it's a configuration parameter for the mail server.
The final possibility is that xxx.xxx.33.191 is not a NAT firewall, and is instead a single box with many domains provisioned on it, some that send email directly, setting the HELO as the sending domain. If this is the case, to prevent a relisting we strongly recommend setting the mail software on the box so that a single identifying name is used in
outbound SMTP connections. As an alternate workaround, you can
configure the mail software to relay its outbound email through an intermediate mail server. Even a co-resident mail server package (such as IIS on Windows) will do fine.
Note: If you are running CPanel, this problem could be caused by CPanel bug #59785, whereby CPanel is unable to send emails associated with the virtual IP address assigned to the sender domain. In other words, CPanel (via exim most likely) is failing to bind to the sender domain's IP address before sending. You will want to turn this feature off until the bug is fixed. This "failure to bind" is the root cause of similar problems with older versions of IMail. This is apparently, in the case of CPanel, fixable in the Exim configuration, but we don't know the details, and CPanel may well clobber such changes next time you patch or upgrade.
Note: there is a fairly common belief that the HELO has to match the
From: line, otherwise mail server spam filtering will block it. This is mistaken. If it were true, large scale email hosting environments (such as Google, godaddy or mail.com/1and1 etc) would be unable to function.
If xxx.xxx.33.191 is a NAT firewall, we STRONGLY recommend that you configure it to prevent machines (except your real mail
servers) on your local network connecting to the Internet on port 25 (SMTP/email). In this way you can contain any insecure machines (either by open proxy/spam trojan or emailing worm like Netsky) from attacking others on the Internet.
I ran the recommended fintbot.pl file CBL's site provides, but I get a bunch of gibberish while tailing the process.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.