/etc/mailhelo problem with invalid HELO argument

[deanstev]

Ok, the following only occurs when I enable the Send outgoing mail from accounts ip address instead of the main ip address. option; disabling it allows all mails to go out. It does the same for SMTP as Webmail.

I do have the /etc/mail_reverse_dns setup correct.

Whenever my client tries to send an e-Mail to some other domains (not others), they get a bounce back which includes the following:

From: Mail Delivery System [mailto:Mailer-Daemon@HOSTNAME.MYSERVER.TLD] 
To: CUSTOMER@MYCUSTOMERDOMAIN.TLD
Subject: Mail delivery failed: returning message to sender

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

 NONCUSTOMER@EXTERNALDOMAIN.TLD
   SMTP error from remote mail server after HELO :
   host HOST.EXTERNALDOMAIN.TLD [THEIR.IP.HERE]: 501 HELO requires domain address

Below is stuff taken from the exim_mainlog:

2008-06-04 00:43:14 H=localhost (WEBMAIL.MYCUSTOMERDOMAIN.TLD) [127.0.0.1] Warning: Sender rate 0.7 / 1h
2008-06-04 00:43:14 1K3g9q-000216-BS <= CUSTOMER@MYCUSTOMERDOMAIN.TLD H=localhost (WEBMAIL.MYCUSTOMERDOMAIN.TLD) [127.0.0.1] P=esmtpa A=fixed_login:CUSTOMER@MYCUSTOMERDOMAIN.TLD S=933 id=44529.92.20.6.5.1212536594.squirrel@WEBMAIL.MYCUSTOMERDOMAIN.TLD T="Test"
2008-06-04 00:43:14 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1K3g9q-000216-BS
2008-06-04 00:43:22 1K3g9q-000216-BS ** NONCUSTOMER@EXTERNALDOMAIN.TLD R=dk_lookuphost T=dk_remote_smtp: SMTP error from remote mail server after HELO : host HOST.EXTERNALDOMAIN.TLD [THEIR.IP.HERE]: 501 5.0.0 HELO requires domain address
2008-06-04 00:43:22 1K3g9y-00023I-Kr <= <> R=1K3g9q-000216-BS U=mailnull P=local S=1902 T="Mail delivery failed: returning message to sender"
2008-06-04 00:43:22 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1K3g9y-00023I-Kr
2008-06-04 00:43:22 1K3g9q-000216-BS Completed
2008-06-04 00:43:22 1K3g9y-00023I-Kr => CUSTOMER <CUSTOMER@MYCUSTOMERDOMAIN.TLD> R=virtual_user T=virtual_userdelivery
2008-06-04 00:43:22 1K3g9y-00023I-Kr Completed

[isputra]

I have the same problem and i look at /etc/mailhelo and domain use to send email is not complete :

domain.com: domain.com
sender.com:

You see that sender.com is not complete. So i change it to

sender.com: sender.com

And the problem solved.

But this problem will appear again when you have to upgrade cpanel because after upgrade cpanel sender.com back to "sender.com:"

Is there any fix to this problem ?

[isputra]

Hi,

I have problem with /etc/mailhelo

Some of domain inside /etc/mailhelo did not have complete configuration. You can look at below example :

domain1.com: domain1.com
domain2.com: domain2.com
domain3.com:
domain4.com: domain4.com

So everytime domain3.com send email to host that have HELO check will be return with this message :

----------------
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

someone@receiver.net
SMTP error from remote mail server after HELO :
host in-receiver.net [123.456.78.90]: 501 Syntactically invalid HELO argument(s)
-----------------

And when i change domain3.com to "domain3.com: domain.com" the problem gone.

But this fix is only temporary. If i have to upgrade cpanel, the configuration back to "domain3.com:" so i have to change it again for domain3.com to work.

Is there any permanent fix for this problem ?

[cpanelnick]

Please open a ticket @ https://tickets.cpanel.net/submit/ so we can determine why there is no value for this domain.

[cpanelnick]

I will look @ your ticket personally if you pm me the #.

[deanstev]

Hmmm, mine doesn't list every domain on the server, does it matter?

Ticket: 259921

[cpanelnick]

This will be addressed in the next builds. I will be looking at your server shortly.

[isputra]

I will look @ your ticket personally if you pm me the #.

Thanks Nick for your help. You already answered my ticket and solved it.

For anyone that have same problem with me, here is the ticket answer from Nick :

-------------------
I have adjusted updateuserdomains to address this issue. The fix should be in public builds tonight or tomorrow. If you have any other servers with this issue, just copy /scripts/updateuserdomains to the server, run it and it will be corrected.

-Nick
-------------------