This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 98%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESL%3C/text%3E%3C/svg%3E)
We have a client who has an Exchange Server 2016.
The domain name of the server is xxxx.yyy.com whereas the mail domain name hosted on the server is yyy-kk.com.
We have set the SPF for yyy-kk which belongs to them to match their IP address and it works fine.
The problem they have is with one bank that is checking the SPF of the server's domain name which is yyy.com. yyy.com does not belong to the client and we have no access to their DNS. Is there a way we can change the server name they see when emails are send from their Exchange Server. Also why are they checking the SPF of the server's name and not only the SPF of the email domain name?
This is what I can see in the email header's when I send an email from this server.
Received: from xxxx.yyyy.com (xxxx.yyyy-kk.com [IP Address])
@Savvas Lazarides
I am writing here to confirm with you any update about this thread now.
If the suggestion below helps, please feel free to accept it as an answer to help more people.
Yea they shouldnt care about the name of the server, otherwise no could send from Exchange Online either :)
All that is needed is the SPF of xxxx.yyy.com contains the IP Addresses of the sending servers in yyy-kk.com and a PTR record exists in DNS for those sending servers.
Dear Andy,
thanks for your answer. Just to clarify.
Our server is named mailserver.yyyyy.com.
The emails are sent from the email address user@yyyy-kk.com which is the email domain hosted on their Exchange Server.
We have an SPF for the yyyy-kk.com pointing to the external IP of the server. The bank is checking the SPF of the yyyyy.com which is the domain of the server and which as it seems it belongs to another company. It was named like this from the vendor who initially setup the server for this company.
Does your answer above still holds? I mean they shouldn't check the yyyyy.com but only the yyyy-kk.com?
SPF is checked against the Return-Path of the sender ( The MAIL FROM ). Is that set correctly?
The return-path for these messages should be set to:
yyyy-kk.com
If it is, then they are checking things incorrectly
If its not, then you need to fix that on your end.
Exactly. this is set correctly and it passes their test as i can see on the results they have sent us. But then they check the spf of the server's name and it fails.
Yea, if you can show your SPF is setup correctly, then this is on them to explain why they are checking this incorrectly.