View Issue Details

IDProjectCategoryView StatusLast Update
0017066phpList 3 applicationCampaign Send Processpublic21-06-18 13:05
Reporterleptserkhan Assigned To 
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status newResolutionopen 
Product Version3.0.5 
Target Versionnext major 
Summary0017066: helo_data sent by phplist using phpmailer causes high spam marks
DescriptionWhen sending email outbound via phpmailer, the receiving mail server is supposed to get a domain name in the helo dialogue. However, as setup in a standard install, the receiving server is getting a domain IP, which causes the mail to get high spam marks.
Steps To Reproducesend outbound email on version 3.0.5 NOT using smtp, which leaves the phpmailer.

Make sure the email is addressed to the email address you receive when visiting:

Check back to see the results.

They indicate the helo_data contains an IP address instead of a domain
TagsNo tags attached.



11-02-14 00:41

reporter   ~0052956

The technicians at provided me with the following useful information.

I then changed the listed file entries from "website" to "domain" in the mentioned files and this corrects the headers, but is still reporting that in the initial connection dialogue my outbound phplist server is sending an IP address instead of a domain name in the helo_data.

still unresolved.

Here are the culprit files according to technicians:

dmin/lib.php: $mail->Helo = getConfig("website");
admin/class.phplistmailer.php: $this->Helo = getConfig("website");
admin/class.phplistmailer.php: $this->Helo = getConfig("website");
admin/class.phplistmailer.php: $this->Helo = getConfig("website");
admin/phpmailer/ChangeLog.txt:* Fixed HELO/AUTH bugs on keep-alive connects


11-02-14 03:05

administrator   ~0052957

Seems like a local config issue to me.

If the HELO is set to getConfig("website") then the website config should work.

Check the DNS settings.

But will try to run some tests to try to verify and be sure.


13-02-14 17:23

reporter   ~0052996

I have heard back from both and They have some useful information.

1) When email is being sent via phplist script, indeed it is sending the domain name and NOT an IP address (that's good), however, SpamAssassin also uses the same rule to trigger on "untrusted_relay". Email outbound from my server as configured with phplist sending either smpt via smtp or phpmailer, includes the following information in the header. The following is provided by technicians:
This rule is not only triggered when the helo is an IP (and as I already said, it's not your case) but also when the email is coming from an untrusted relay.
I checked your headers and this one seems not valid to me:

Received: from localhost.localdomain ([]:57205
    with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from <>)
    id 1WDfX8-00088O-NR for;
    Wed, 12 Feb 2014 14:31:46 -0500

I don't think you should have a from localhost.localdomain there... that could be the culprit.

When tested outbound email using their php script (not phplist) there were no references to "Received: from localhost.localdomain ([]:57205 by"

In other words, no references to localhost.localdomain

I believe there is an entry in the config.php of phplist which allows a user to set this and if not set (localhost), email will not be sent out from a host which is running smpt server AND phplist.


13-02-14 22:56

administrator   ~0053010

the line

Received: from localhost.localdomain ([]:57205

is created by Exim and not phpList and it is caused by phplist connecting to Exim on

Exim then does a reverse lookup and maps it to localhost.localdomain

Change in you /etc/hosts