• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Setting up mail on Plesk 12 with hostname hosted on a different server

ilijamt

Basic Pleskian
I have a server that I use to host my primary domain, and I have a cople Plesk servers, now I updated the hostnames of all the servers like

Code:
s1.de.myserverplace.de

Now when the plesk server sends a mail it goes in spam always,

In the SPF records of the primary domain sits this
Code:
myserverplace.de.   IN    TXT    "v=spf1 a mx a:myserverplace.de a:s1.de.myserverplace.de ip4:148.251.100.157 ip4:144.76.163.46 ip6:2a01:4f8:201:81b8::60 ?all"

But when I actually send the mail in the headers of the received mail I get this.

Code:
Received: from s1.de.myserverplace.de (s1.de.myserverplace.de. [144.76.163.46])
by mx.google.com with ESMTPS id p2si2158952wjy.73.2015.05.14.04.09.17
for <[email protected]>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 14 May 2015 04:09:17 -0700 (PDT)
Received-SPF: none (google.com: [email protected] does not designate permitted sender hosts) client-ip=144.76.163.46;
Authentication-Results: mx.google.com;
spf=none (google.com: [email protected] does not designate permitted sender hosts) [email protected];
dmarc=fail (p=NONE dis=NONE) header.from=myserverplace.de

Any idea how would I set this up so this doesn't happen?
 
Hi ilijamt,

Received-SPF: none (google.com: [email protected] does not designate permitted sender hosts) client-ip=144.76.163.46
You seem to have forgotten to set/add/edit your SPF - records at "s1.de.myserverplace.de", which resolves to the IP "144.76.163.46". Currently, there is only an A - record:
Code:
s1.de.myserverplace.de.    38400    IN    A    144.76.163.46
 
Hello,

Actually I did set them they are there

dig s1.de.myserverplace.de any
Code:
s1.de.myserverplace.de.    21599    IN    A    144.76.163.46
s1.de.myserverplace.de.    21599    IN    TXT    "v=spf1 include:_spf.myserverplace.de ?all"

dig _spf.myserverplace.de TXT
Code:
_spf.myserverplace.de.    21599    IN    TXT    "v=spf1 a mx a:myserverplace.de a:s1.de.myserverplace.de ip4:148.251.100.157 ip4:144.76.163.46 ip6:2a01:4f8:201:81b8::60 ?all"

Looks like it took a little time for the DNS to update, that's why it didn't work
 
Looks like DNS propagation is going slow this time, but I was doing major restructuring of the way things worked.
 
Back
Top