• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue 421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com

D

DaarGaJeDan

Basic Pleskian
hi Guys,

I have problems setting up the mail servers and the DNS settings.

I try to mail to ziggo.nl but i keep getting the following error:
421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com

i should expect that example.com should be mail.example.com.
it looks like ziggo doesnt use the MX record to check the domein.
My A record for example.com goes to a different ip address then mail.example.com (= plesk servers ip and the rDNS ip for s2.myserver.com)
 
Does your srever hostname resolve to serer IP resolve to the same server hostname?
 
I found something is wrong with the SPF. Looks like postfix uses a local ip 127.0.0.1 instead of the public ip.

How can i set the public ip adres here?

____________ MXTools report: _____________

spf:example.com:127.0.0.1

v=spf1 +a +mx +a:s2.example.com +a:mail.example.com +a:example.com -all
PrefixTypeValuePrefixDescDescription
vspf1The SPF record version
+aPassMatch if IP has a DNS 'A' record in given domain.
+mxPassMatch if IP is one of the MX hosts for given domain name.
+as2.myserver.comPassMatch if IP has a DNS 'A' record in given domain.
+amail.example.comPassMatch if IP has a DNS 'A' record in given domain.
+aexample.comPassMatch if IP has a DNS 'A' record in given domain.
-allFailAlways matches. It goes at the end of your record.

TestResult
SPF AuthenticationSPF Failed for IP - 127.0.0.1
info.png
More Info
SPF Record PublishedSPF Record found
SPF Record DeprecatedNo deprecated records found
SPF Multiple RecordsLess than two records found
SPF AlignmentDomain found in SPF
SPF Contains characters after ALLNo items after 'ALL'.
SPF Syntax CheckThe record is valid
SPF Included LookupsNumber of included lookups is OK
SPF Type PTR CheckNo type PTR found
SPF Void LookupsNumber of void lookups is OK
SPF MX Resource RecordsNumber of MX Resource Records is OK
SPF Record Null ValueNo Null DNS Lookups found
 
Last edited by a moderator:
You might want to edit that "More info" link ...

Normally SPF should only check the IP that tries to connect and deliver mail, which can't ever be 127.0.0.1 on a host where the name isn't recognized as local, so I wonder what mxtools does there and why. Received: lines aren't trustworthy and should not be checked.
As a dirty fix, you could include +ip4:127.0.0.1 to your spf record.
 
Postfix is using 127.0.0.1 when you are sending emails not through SMTP auth from an external source but from a webmail source on the server. In that case, the webmail software is the first hop, and that inserts the IP 127.0.0.1 to the chain in the mail header. To fix that issue, edit /etc/postfix/main.cf and add this line:
myhostname = <public hostname of your server>
Then restart postfix and try again with sending a mail from the server.
 
Ok but i know for sure i sended this test with apple mail client

Also my

myhostname = s2.example.com
I found:
mydestination = localhost, localhost.localdomain, localhost
smtpd_authorized_xforward_hosts = 127.0.0.0/8 [::1]/128
 
Could you please update your Postfix file as described an try again?
Also could you please verify that in your /etc/hosts file you have at least one line with your public IPv4 or IPv6 address and your public hostname? Maybe that file only lists the 127.0.0.1 and localhost association.
 
DaarGaJeDan said:
Ok but i know for sure i sended this test with apple mail client

Also my

myhostname = s2.example.com
I found:
mydestination = localhost, localhost.localdomain, localhost
smtpd_authorized_xforward_hosts = 127.0.0.0/8 [::1]/128
Click to expand...
That is correct.
 
Peter Debik said:
Also could you please verify that in your /etc/hosts file you have at least one line with your public IPv4 or IPv6 address and your public hostname? Maybe that file only lists the 127.0.0.1 and localhost association.
Click to expand...
Have you done that, too? It is often tiresome to having to ask the same questions over and over again and not to get the feedback. These are points that must be checked when symptoms like you describe them occur. Have you checked it? What was the result?
 
In Plesk GUI: What is set as "Outgoing mail mode" in Tools & Settings > Server.-Wide Mail Settings?
Outgoing mail mode
Send from domain IP addresses
Send from domain IP addresses and use domain names in SMTP greeting
Send from the specified IP addresses
?

Also I suggest to send an email to any external address, then open the hidden mail headlines and to paste them here so that we can see what is really listed between "From" and the recipient. We'll need to find out where the 127.0.0.1 sender IP is coming from. Recipient name and sender hostname can be anonymized.
 
We use Send from domain IP addresses because of other issues.

Here are the headers: I masked some domainnames and ip addresses you can still see the 127 address:

Received: from pv33p00im-smtpin032.me.com ([17.142.180.58])
by ms62004.mac.com (Oracle Communications Messaging Server 8.0.2.5.20200127
64bit (built Jan 27 2020)) with ESMTP id <[email protected]>
for [email protected]; Sat, 19 Feb 2022 20:40:13 +0000 (GMT)
Original-recipient: rfc822;[email protected]
Return-path: <[email protected]>
Received: from s2.example.com (s2.example.com [80.200.100.100])
by pv33p00im-smtpin032.me.com (Postfix) with ESMTPS id 37B92761E97 for
<[email protected]>; Sat, 19 Feb 2022 20:40:10 +0000 (UTC)
X-ICL-SCORE: 3.3330333300
X-ICL-INFO:
GAtbVUseBVFGSVVESwMGUldZCh4MXUMRSFsIVVhDQ19XFwkZHRIWBxFERBo4Bl9MGxVEVx5UC0BD
EEgZFBIWERwJW1VABxhQQEpIRkwIGFNGQURXEFVaDUhbFUVWBl9MGxVEVwhERF9XClRZTlkYDBlb
RhMcDRRUHFcIG1oQWwsRRERLSHIDJkxMUk9VdHJWNlRSR0kJGyMzSyRaTXYAVkQ4IzI7AXJQNU8P
WRZcCEBVCwVKWl1XBgccEBILcFsHWxoJGlo=
Authentication-results: dmarc.icloud.com; dmarc=pass header.from=example.com
x-dmarc-info: pass=pass; dmarc-policy=none; s=r1; d=r1
x-dmarc-policy: v=DMARC1; p=none
Authentication-results: dkim-verifier.icloud.com; dkim=pass (1024-bit key)
header.d=example.com [email protected] header.b=dgDoSXMq
Authentication-results: spf.icloud.com; spf=pass (spf.icloud.com: domain of
[email protected] designates 80.200.100.100 as permitted sender) smtp.mailfrom=[email protected]
Received-SPF: pass (spf.icloud.com: domain of [email protected] designates 80.200.100.100
as permitted sender) receiver=spf.icloud.com; client-ip=80.200.100.100;
helo=s2.example.com; envelope-from=[email protected]
Received: from s2.example.com (localhost.localdomain [127.0.0.1])
by s2.example.com (Postfix) with ESMTP id 49A4913BE45 for <[email protected]>; Sat,
19 Feb 2022 21:40:09 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=example.com; s=default;
t=1645303209; bh=g3zLYH4xKxcPrHOD18z9YfpQcnk/GaJedfustWU5uGs=;
h=Received:Received:From:Subject:To;
b=dgDoSXMqfJI67RvTqVvIxVSYiX92RBbteSHp0dn2VkjhCN0r06F5mRcoyU6bHVQvA
o8w7CCOQ6A826VJbezb/UfKm0oPV852dcf7xVWs7aSq64nYQSpkkapLZjDJdL+DQqZ
ZbICYQDNirr7HbYWE3qJukJGoBfU7mIXve1s2Z+M=
Authentication-results: s2.example.com; spf=pass (sender IP is 127.0.0.1)
smtp.mailfrom=[email protected] smtp.helo=s2.example.com
Received-SPF: pass (s2.example.com: localhost is always allowed.)
client-ip=127.0.0.1; envelope-from=[email protected]; helo=s2.example.com;
X-Spam-Flag: NO
X-Spam-Score: -3.1
X-Spam-Level:
X-Spam-Status: No, score=-3.1 tagged_above=-9999 required=5
tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001,
URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from s2.example.com ([127.0.0.1]) by s2.example.com (s2.example.com [127.0.0.1])
(amavisd-new, port 10024) with ESMTP id aBtK7SvZ4-Oe for <[email protected]>;
Sat, 19 Feb 2022 21:40:06 +0100 (CET)
Received: from smtpclient.apple
(82-72-226-187.cable.dynamic.v4.ziggo.nl [82.72.226.187])
by s2.example.com (Postfix) with ESMTPSA id D5E9413BE16 for <[email protected]>; Sat,
19 Feb 2022 21:40:05 +0100 (CET)
Received-SPF: pass (s2.example.com: connection is authenticated)
From: Jan Janssen <[email protected]>
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
MIME-version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Subject: Test
Message-id: <[email protected]>
Date: Sat, 19 Feb 2022 21:40:01 +0100
To: Jan Janssen <[email protected]>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
X-PPP-Message-ID: <[email protected]>
X-PPP-Vhost: example.com
X-MANTSH: 1TEIXWlwZGVoaGkNHB0tNT0ReQ0QeHhofEQpMQxcbGgQbGxgEHBMEGBgfEBseGh8
aEQpMWRcbGhoaEQpZRBdpcFB8R00TAVNoXxEKWU0Xek9YWUVES0ZrRkZFXREKX1kXGxMeEQpfT
RdkRURPEQpZSRcdH3EbBhsfGncGBxwYBhoGGgYbBhgaGnEbGhoQGncGGgYaBhkaBgcfGgYaBhp
xGhAadwYaEQpZXhdsbHkRCkNOF2sSa2RQeR9cTxpOfl5gGUEYWh9tRGccdWB6Y0FZX3lzEQpYX
BcZBBoEHh8HSxsbGxwaTxwFGx0EGx4YBBsTEgQeGBAbHhofGhEKXlkXcHhcWm0RCk1cFxkRCkx
aF1Jpa11rEQpFWRd7EQpMXxd6BQUFBQUFBQUFZREKTU4XaWsRCkxGF01rEQpDWhcSHQQYHxkEG
x4SBBsZEhEKQl4XGxEKQlwXGxEKXk4XGxEKQksXY2R/elBoHWhDGVIRCkJJF2Nkf3pQaB1oQxl
SEQpCRRdmRmBmZ1loX2JHfhEKQk4XY2R/elBoHWhDGVIRCkJMF2J6WVp6TWt6aF5mEQpCbBdsB
R8aGUVIT3p7QBEKQkAXZkhceWl8UAEFGVwRCkJYF2V4RGFSR3gaS2BjEQpCeBdlQF1dGgF+eR9
dQREKTV4XGxEKcGgXYmNHeFJwU0RhTFsQBxsdEQpwbBdpa35ceklTcn9BQhAZGhEKcEwXelNOY
2tkE355cHgQGRoRCnBDF2ZcQ3lsZkNjY0ZkEBkaEQptfhcbEQpYTRdLEQ==
X-CLX-Shades: PersonalAllow

test
 
First i see:
Received: from s2.example.com (s2.example.com [80.200.100.100])

Then
Received: from s2.example.com (localhost.localdomain [127.0.0.1])

Then:
Received: from s2.example.com ([127.0.0.1]) by s2.example.com (s2.example.com [127.0.0.1])

I checked everything, i can't figure out why this is.
 
My host file:

127.0.0.1 localhost.localdomain localhost

# The following lines are desirable for IPv6 capable hosts
::1 localhost.localdomain localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

80.200.100.100 s2.example.com s2
 
You must log in or register to reply here.

Similar threads

A
Resolved How to align the mail server's HELO/EHLO with proper DNS (forward and reverse) values>
2
Replies
22
Views
30K
SteveITS
S
falconsi
Resolved PTR Record resolved, what to do for various domains?
Replies
7
Views
18K
EmperorFPI
E
I
Issue Problem with sending emails (not matching your DNS configuration)
Replies
14
Views
9K
igork1
I
B
Resolved My mail server is on a spam list
Replies
2
Views
5K
brownbag
B
F
Issue Problem with reverse DNS (SMTP Banner) for multiple Domains
Replies
2
Views
6K
frankyab
F
Back
Top