550 when seding mail to hotmail

Perp · Post by **Perp** » Mon Nov 20, 2017 7:22 pm

When emails are sent to hotmail, they are not delivered with code '550 command rejected due to Sender ID validation failure.'

There is also a link by Microsoft support that recommends this:

Outlook.com will not allow delivery of email sent from a domain where the Sender ID record was configured by the domain owner to NOT allow ANY IP to send mail from that domain. Sender ID allows a domain owner to protect domains that aren't intended for sending email in order to help protect their domain from being spoofed. This can be done by publishing a simple TXT record in DNS like the following example (note: the organization would replace example.com with their own domain and or sub-domain name):
example.com IN TXT "v=spf1 -all"

when I check DNS settings inside vesta, I already have similar records there:

Code: Select all

@ TXT "v=spf1 a mx ip4:[SERVER_IP] ?all"

So should I add recommended setting by MS Support, or is there something else that's messing with delivering mails to hotmail ? How can I fix it ?

Help is greatly appreciated.

Post by **tjebbeke** » Tue Nov 21, 2017 4:53 pm

Do you have multiple IP's? Maybe IPv6? That are not listed in your SPF record.

Perp · Post by **Perp** » Sun Nov 26, 2017 8:30 am

tjebbeke wrote:Do you have multiple IP's? Maybe IPv6? That are not listed in your SPF record.

Nothing of the sort... only one ip4 address and it is in SPF records.
I added ms recommended record, so Im gonna see if that helps.

anros · Post by **anros** » Wed Dec 06, 2017 12:12 pm

Hi.
Even we are facing same problem.our domain has valid SPF record. But still mails are bouncing with error as "SPF FROM check failed"
Cheers

sysdop · Post by **sysdop** » Fri Dec 08, 2017 2:05 am

Perp wrote:
tjebbeke wrote:Do you have multiple IP's? Maybe IPv6? That are not listed in your SPF record.
Nothing of the sort... only one ip4 address and it is in SPF records.
I added ms recommended record, so Im gonna see if that helps.

@Perp The problem occurs because you are using SPF 2.0, delete that record and stay with the first version of SPF. Also make sure that all the IPs as well as IPv4 and IPv6 are listed in that record, finally wait for the propagation time established according to the TTL you have posts.

Post by **mehargags** » Fri Dec 08, 2017 12:03 pm

and also make sure you have rDNS pointing correctly for that IP Address

Vesta Control Panel - Forum