我的设置：cPanel w / Centos + CloudLinux 6 EXIM。 suPHP。 PHP 5.5。 '防止'没有'用户发送..''启用其他启用设置：CSF防火墙（SMTP调整启用），CXS，suPHP，邮件头跟踪，'nobody'阻止，最大每小时100，以及许多其他的调整。
在我的EXIMconfiguration中：“从帐户的专用IP地址发送邮件”已启用。 我在下面的域中启用了DKIM和SPF，因为这里只是出于隐私的原因而屏蔽了这些域。
任何人都可以请解释如何防止这个？ 这是一个共享的托pipe服务器。 除了CBL和Spamhaus之外，我的IP是干净的（他们彼此相关，这就是为什么）。
来自CBL滥用团队
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: 2015:06:12 ~23:30 UTC+/- 15 minutes (approximately 16 hours, 15 minutes ago). The names seen included: client.com, e-client.com, client.net, client.com, client.com, client.com, server.mydomain.com 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.