金世旗国际控股股东:请大家帮忙翻译一下简单的片断

Note that 61.129.113.238 was connecting to our servers and identifying
itself via HELO as "61.129.113.238". Which is quite suspicious
in and of itself.

This is USUALLY spamware, but in some rare circumstances, it can be a
misconfiguration in your mail server. The CBL attempts to distinguish
real mail server software from malware SMTP clients by expecting users
to name their mail server[s] to indicate who _they_ are, not their
provider and be consistent with Internet protocol standards.

Use of a bare IP address in the HELO is a violation of
RFC2821 section 4.1.1.1, which says that the HELO value MUST
be either a fully qualified domain name (such as "mail01.example.com")
or an IP address enclosed in square brackets (such as "[61.129.113.238]").

You will need to investigate and fix this.

If this is a simple configuration error, if you set
your mail server to claim to be, for example,

mail.<your domain>

You won't be relisted unless except via viruses or spam compromises.

Notes on specific software:

1) It has been reported that Lyris ListManager (particularly older
versions) is occasionally auto-configured in such a way to cause this
problem. On Windows, this can be resolved by using the "lyris.exe" (or
"lm.exe" in later versions thusly:

lyris.exe helotext <desired HELO name>

2) It has been reported that sendmail's "milter-sender" package
occasionally does this (usually something to do with having DNS
resolution problems at the time). At the time of writing, the
latest version of milter-sender permits you to set the HELO
explicitly, and thus avoid this problem.

3) If you're running a MultiTech firewall filter (eg: "RouteFinder
VPN"), or Plesk - both of which use qmail, or just "bare" qmail,
check the file /var/qmail/control/helohost and /var/qmail/control/me
(directory location may vary depending on operating system).

To be certain that things are set correctly, edit both the "me" and
"localhost" files to have your mail server's fully qualified domain
name. If localhost file doesn't exist, correcting the "me" setting
should suffice on its own. Now restart qmail.

4) Older versions of ZAEP (a challenge/response tool) installations
appear to default to doing this. According to the release notes
at http://www.zaep.com/releasenotes.asp, ZAEP version 4.1.0.0
released on Sept 26th fixes this problem. Please upgrade.

I've removed the entry from the list.

It may take a few hours to propogate to the public nameservers.

WARNING: the CBL WILL relist this IP if the underlying issues are not
resolved, and the CBL detects the same thing again.

--
Ray, CBL Team