On 27/08/2020 12:39, Jaroslaw Rafa via mailop wrote:
It's rather strange that you are comparing this to SPF. 1) SPF has no "default deny" policy; if a domain has no SPF record at all, then mail is (or at least should be) accepted by default.
No, but it's possible for a receiver to have a policy to not accept mail from an unknown server that doesn't match the sending domain's SPF record (and that such a record has to exist). If you're going to have the sending server have to have some form of 'authorisation', then requiring SPF would be better than requiring an one-off ad-hoc authorisation method.
2) as the original poster mentioned, once you have authorized your server with them, you can send mail *with any sender domain*. It does not compare to SPF in any way.
I missed that. I thought they had to say 'this mail server can send from this domain'. If the server can send from *any* domain, then it's a useless policy, as well as being unscalable.
-- Paul Paul Smith Computer Services [email protected] - 01484 855800 -- Paul Smith Computer Services Tel: 01484 855800 Vat No: GB 685 6987 53 Sign up for news & updates at http://www.pscs.co.uk/go/subscribe _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
