Re: sendmail problem

Hi Grant,

the result showed below and any commet about this issue.

Thanks.

Version 8.13.7
Compiled with: DNSMAP HESIOD HES_GETMAILHOST LDAPMAP LOG MAP_REGEX
MATCHGECOS MILTER MIME7TO8 MIME8TO7 NAMED_BIND NETINET
NETINET6
NETUNIX NEWDB NIS PIPELINING SASLv2 SCANF SOCKETMAP
STARTTLS
TCPWRAPPERS USERDB USE_LDAP_INIT
OS Defines: ADDRCONFIG_IS_BROKEN HASFCHOWN HASFCHMOD
HASGETDTABLESIZE HASINITGROUPS HASLSTAT HASNICE
HASRANDOM
HASRRESVPORT HASSETREGID HASSETREUID HASSETRLIMIT
HASSETSID
HASSETVBUF HASURANDOMDEV HASSTRERROR HASUNAME
HASUNSETENV
HASWAITPID IDENTPROTO NEEDSGETIPNODE REQUIRES_DIR_FSYNC
USE_DOUBLE_FORK USE_SIGLONGJMP
Kernel symbols: /boot/vmlinux
Conf file: /etc/mail/submit.cf (default for MSP)
Conf file: /etc/mail/sendmail.cf (default for MTA)
Pid file: /var/run/sendmail.pid (default)
Canonical name: mail.fortune-star.com.hk
UUCP nodename: mail.fortune-star.com.hk
a.k.a.: mail
a.k.a.: [203.98.178.xx]
Conf file: /etc/mail/submit.cf (selected)
Pid file: /var/run/sm-client.pid (selected)

============ SYSTEM IDENTITY (after readcf) ============
(short domain name) $w = mail
(canonical domain name) $j = mail.fortune-star.com.hk
(subdomain name) $m = fortune-star.com.hk
(node name) $k = mail.fortune-star.com.hk
========================================================

Recipient names must be specified



Taylor, Grant 寫道：

On 08/06/06 12:12, Douglas wrote:
Hi all,

any idea of this error when i send to this site. any configuration caused in
my sendmail server.

thanks

----- The following addresses had permanent fatal errors -----
<eric@xxxxxxxxxxx>
(reason: 553 Bogus helo classic.asianet.co.th 203.98.178.XX.
<http://unblock.secureserver.net/?ip=203.98.178.*>)
<michelle@xxxxxxxxxxx>
(reason: 553 Bogus helo classic.asianet.co.th 203.98.178.XX.
<http://unblock.secureserver.net/?ip=203.98.178.*>)

This indicates that the receiving server did not like your HELO / EHLO name.

The bounce back message shows that the email was returned 'due to
excessive spam' and has returned a 'bogus helo'. This indicates that
the server the email originated from either has a virus or has not been
setup correctly. Please refer to the following information regarding
this issue:

The administrator's comment corroborates what I stated above.

(See more below)
The SMTP HELO command is used by the outgoing mail server to greet the
destination servers that they are connecting to. It is usually the
first command issued when mail is being sent. It means "Hello, I am
...." Many viruses and bulk emailers send false or nonstandard HELO
messages. We are starting to filter these messages and block traffic
from email servers that utilize non-standard HELO settings.


Here are the types of error messages related to helo issues that you
may experience:


1. bogus helo

This means that the sending email server connected to our email server
and said "HELO [their IP]". RFC 1123 says that the HELO ("hello")
message should contain "a valid principal host domain name for the
client host". This means a name like "smtp.exampledomain.com", or
"mail.exampledomain.com". An IP address is not a valid listing for the
name of the server.

In order to resolve this situation, the sending server's administrators
will need to configure the server properly, which will cause it to
identify itself by name rather than IP address. The administrators of
this server may also want to check it for viruses, as many viruses use
the HELO command with an IP rather than the name.


2. bogus helo (203.98.178.xx)

This means that the sending server connected to us and said "HELO
(receiving email server's IP)". What this means is that the sending
server tried to say "Hello, I'm you!" This action is generally caused
by a virus.

In order to resolve this situation, the sending server's administrators
will need to check it for viruses.


3. bogus helo matches rcpt

This means that the sending system connected to our email server and
said "HELO (receiving email server's domain name)". This is another
version of "Hello, I'm you!" but using the server's domain name rather
than the server's IP address. This is normally caused by a virus or a
bulk emailer.

If this process is not done intentionally, it is generally created by a
virus. The server's administrators will need to check the machine for
problems.

We hope that this information is useful in diagnosing and resolving the
issue that you are experiencing.

This description tells you why SecureServers.Net will reject your messages
stating a bogus helo. Check to see if any of the above are the case.

You can check to see what Sendmail believes it's host name is by:

sendmail -d0.10

Check the "SENDMIAL IDENTITY (after readcf)" section.



Grant. . . .

.

Relevant Pages

  • Re: sendmail problem
    ... any configuration caused in my sendmail server. ... excessive spam' and has returned a 'bogus helo'. ... Many viruses and bulk emailers send false or nonstandard HELO ... This means that the sending email server connected to our email server ...
    (comp.mail.sendmail)
  • Re: GoDaddy blocking email from Exchange server
    ... Seems to me you want to change the FQDN, not the masquerade domain. ... Then type helo and you should see mail.sholarco.com which should be what ... click the virtual server that you ... This means that the sending email server connected to our mail server ...
    (microsoft.public.windows.server.sbs)
  • RE: GoDaddy blocking email from Exchange server
    ... GoDaddy accounts now. ... We have an Exchange server that can't send email to any address @ ... The SMTP HELO command is used by the outgoing mail server to greet the ... This means that the sending email server connected to our mail server and ...
    (microsoft.public.windows.server.sbs)
  • Re: GoDaddy blocking email from Exchange server
    ... Then type helo and you should see mail.sholarco.com which should be what ... In Exchange System Manager, click the virtual server that you ... This means that the sending email server connected to our mail server ...
    (microsoft.public.windows.server.sbs)
  • Re: Eine bestimmte Datei per Script als eMail-Attachment versenden
    ... Ohne "Option Explicit" wird cdoBasic zu Null angenommen, ... wenn der Server auf SMTP-Auth besteht. ... der erwartet im HELO einen FQDN; steht doch laut und deutlich da! ... sowie §1004 Abs. ...
    (microsoft.public.de.german.scripting.wsh)
Loading