请翻译：202.192.1.5 is making SMTP connections which indicate that it is misconfigured. Some elements of your existing configuration create message characteristics identical to previously identified spam messages. Please align the mail erver's HELO/EHLO 'icoremail.net' with proper DNS (forward and reverse) values for a mail server. Here is an example: Correct HELO/DNS/rDNS alignment for domain example.com: - Mail server HELO: mail.example.com - Mail server IP: 192.0.2.12 - Forward DNS: mail.example.com -> 192.0.2.12 - Reverse DNS: 192.0.2.12 -> mail.example.com Correcting an invalid HELO or a HELO/forward DNS lookup mismatch will stop the IP from being listed again. Points to consider: * Alignment: it is strongly recommended that the forward DNS lookup (domain name to IP address) and rDNS (IP to domain) of your IP should match the HELO value set in your server, if possible * The IP and the HELO value should both have forward and rDNS, and should resolve in public DNS * Ensure that the domain used in HELO actually exists! Additional points: * According to RFC, the HELO must be a fully qualified domain name (FQDN): "hostname.example.com" is an FQDN and "example.com" is not an FQDN. * The domain used should belong to your organisation. * HELO is commonly a server setting, not DNS. Contact your hosting provider for assistance if needed. You can test a server's HELO configuration by sending an email from it to helocheck@abuseat.org. A bounce that contains the required information will be returned immediately. It will look like an error, it is not. Please examine the contents of this email. If all settings are correct, you have a different problem, probably malware/spambot. Again, the HELO we are seeing is 'icoremail.net'. The last detection was at 2023-05-27 13:35:00 (UTC). For information on misconfigured or hacked SMTP servers and networks, please see this FAQ: https://www.spamhaus.org/faq/section/Hacked...%20Here's%20help#539 CSS listings expire a few days after last detection. You can always open a ticket (or update an existing one) to inform us when and how the situation was been secured.

202.192.1.5正在建立SMTP连接，表明其配置不正确。您现有的一些配置元素创建与先前识别的垃圾邮件相同的消息特征。请将邮件服务器的HELO/EHLO“icoremail.net”与邮件服务器的适当DNS（正向和反向）值对齐。以下是一个示例：域示例.com的正确HELO/DNS/rDNS对齐方式：-邮件服务器HELO：mail.example.com-邮件服务器IP：192.0.2.12-正向DNS：mail.example.com->192.0.2.12-反向DNS：192.0.2.12->mail.example.com。更正无效的HELO或HELO/正向DNS查找不匹配将停止该IP再次被列出。需要考虑的要点：*对齐：强烈建议您的IP的正向DNS查找（域名到IP地址）和rDNS（IP到域）应与服务器中设置的HELO值匹配，如果可能的话。* IP和HELO值都应具有正向和反向DNS，并且应在公共DNS中解析。*确保在HELO中使用的域实际存在！附加要点：*根据RFC，HELO必须是完全限定域名（FQDN）：“hostname.example.com”是FQDN，“example.com”不是FQDN。*使用的域应属于您的组织。*HELO通常是服务器设置，而不是DNS。如有需要，请联系您的托管提供商寻求帮助。您可以通过向helocheck@abuseat.org发送电子邮件来测试服务器的HELO配置。将立即返回包含所需信息的反弹。它看起来像一个错误，但它不是。请检查此电子邮件的内容。如果所有设置都正确，则您可能有不同的问题，可能是恶意软件/垃圾邮件机器人。再次看到的HELO是“icoremail.net”。最后一次检测是在2023年5月27日13:35:00（UTC）。有关配置不正确或被黑客攻击的SMTP服务器和网络的信息，请参见此FAQ：https://www.spamhaus.org/faq/section/Hacked...%20Here's%20help#539。CSS列表在最后检测几天后过期。您始终可以打开一个工单（或更新现有工单），以告知我们何时以及如何安全地解决了该情况。