3 ms·
To most, including Gmail, it's actually no problem with DMARC in my experience too. However, one of my servers IPs is on a Microsoft blacklist since many years
by kro 5y ago
To most, including Gmail, it's actually no problem with DMARC in my experience too.
However, one of my servers IPs is on a Microsoft blacklist since many years now.
It sends <10 messages / day. I've tried every unlist form I could find, even called MS but it does not get taken of that list and they "won't disclose why".
I'm routing SMTP to MS via another relay now :)
- tudorw 5y agosame experience here, perfect score but no mail into Microsoft
- feanaro 5y ago> I'm routing SMTP to MS via another relay now :) How do you do this? Could you share details on the setup?
- kortilla 5y agohttps://serverfault.com/questions/257637/postfix-to-relay-mails-to-other-smtp-for-particular-domain https://serverfault.com/questions/257637/postfix-to-relay-ma...
- kro 5y agoIt's a rather simple Postfix setup: transport.db: hotmail.com relay:[relay.server.tld]:587 # and other domains main.cf: transport_maps = hash:/etc/postfix/transport smtp_sasl_password_maps = hash:/etc/postfix/relay_passwd relay_passwd.db: # if necessary / not authenticated by IP relay.server.tld user:pass The relay can/should rewrite the Return-Path to pass SPF. It's no problem for DMARC as the DKIM signature added by the initial server still authenticates it. It requires manually adding domains of custom 365 installations to the list - at this size I do this manually, but should probably be automated "on bounce" or maybe even by a smart rule based on the MX record. In Exim4 it's also possible to conditionally rewrite based on for example the recipient domain.