Set name used in EHLO

[Jodrik]

I just got a complaint from a client about the non-correct SPF records being used, I looked into this with DEBUG logging and found the following:

Wed, 10 Sep 2014 11:22:45 -> Success: Action=[Add Mail To Queue], Details=[2 KB]
Wed, 10 Sep 2014 11:22:45 -> Success: Action=[Process Mail], Details=[2 KB: Start transfer.]
Wed, 10 Sep 2014 11:22:45 -> Success: Action=[MX Lookup], Details=[DNS=94.142.208.6, Domain=webtic.nl: Found 1 records]
Wed, 10 Sep 2014 11:22:45 -> Success: Action=[SMTP Transfer], Details=[Domain=webtic.nl, Host=exim1.webtic.nl:25, IP=82.94.199.249: Connection accepted.]
Wed, 10 Sep 2014 11:22:45 -> ***DEBUG*** -> Success: Action=[Recv Response], Details=[IP=82.94.199.249: 220 smurf.webtic.nl ESMTP Exim 4.77 Wed, 10 Sep 2014 11:23:32 +0200]
Wed, 10 Sep 2014 11:22:45 -> ***DEBUG*** -> Success: Action=[Send Command], Details=[IP=82.94.199.249: EHLO KO3.net]
Wed, 10 Sep 2014 11:22:45 -> ***DEBUG*** -> Success: Action=[Recv Response], Details=[IP=82.94.199.249: 250-smurf.webtic.nl Hello mx1.ko3.net [94.142.213.180]]
Wed, 10 Sep 2014 11:22:45 -> ***DEBUG*** -> Success: Action=[Recv Response], Details=[IP=82.94.199.249: 250-SIZE 52428800]
Wed, 10 Sep 2014 11:22:45 -> ***DEBUG*** -> Success: Action=[Recv Response], Details=[IP=82.94.199.249: 250-PIPELINING]
Wed, 10 Sep 2014 11:22:45 -> ***DEBUG*** -> Success: Action=[Recv Response], Details=[IP=82.94.199.249: 250-AUTH PLAIN LOGIN CRAM-MD5]
Wed, 10 Sep 2014 11:22:45 -> ***DEBUG*** -> Success: Action=[Recv Response], Details=[IP=82.94.199.249: 250 HELP]

It uses KO3.net in the EHLO where it should be using MX1.KO3.net. I could not find this setting in any of the .ini files. (How) can this be configured?

[Code Crafters]

This is the primary domain in the general settings which should be some domain that resolves to your IP correctly as you've stated.

In a future version we hope to add many more domain specific settings including showing appropriate EHLO domains based on the domain used to connect.

[Jodrik]

After setting the primary domain to MX1.KO3.net this indeed showed up as the EHLO response setting, this is a good enough fix for me!

Thu, 11 Sep 2014 10:32:01 -> ***DEBUG*** -> Success: Action=[Send Command], Details=[IP=64.235.154.66: EHLO MX1.KO3.net]

EDIT:
In my usecase I host about 50 domains, most use email from the ability server but all have their MX records set to MX1.KO3.net. Thus having a single field to set how the server identifies itself would be fine, another option would have been to include my domain in every SPF statement but that seems a bit over the top and will also slow down the delivery time for external servers.

[Code Crafters]

Most email servers only care that the domain in the EHLO resolves to your mail server IP.

As for SPF this is used only to specify what domains or IPs can send from those domains so again as long as the something in the record matches your mail server IP then that would be fine. Generally you always include the token "mx" in the SPF record as this should always point to your Ability Mail Server anyway meaning that no particular domain needs to be explicitly defined in the SPF record.

[Jodrik]

Our problem was that Domain example.com would have MX records for MX1.KO3.net & MX2.KO3.net. Since the server identifies as KO3.net and not MX1.KO3.net and the KO3.net domain was not included in the SPF records it would fail since KO3.net was not in the MX listing on the example.com domain.