Hi Neal,
In your case, it's probably fine that you send as scoop@sonic.net, assuming that the plugin is sending from Sonic's web servers and not a 3rd-party service. Since your MX for metaphorager.net is Sonic, you can also use any valid domain email address that you've set up - this can be handy if folks reply to your emails, since you can filter by the To: address being @metaphorager.net instead of direct emails to your plain sonic.net address.
If I were to venture a guess, I'd say that the warning in that plugin is because if you were to put something like a gmail address in there, it would probably be rejected by some providers, since Google (and many others) use Sender Policy Framework (SPF) and other checks to detect and reject messages that aren't coming from the official servers for that domain. By default, we set up the necessary records so that a domain we host (such as yours) can send with email addresses from it. (*@metaphorager.net in your case)
-- Joe
In your case, it's probably fine that you send as scoop@sonic.net, assuming that the plugin is sending from Sonic's web servers and not a 3rd-party service. Since your MX for metaphorager.net is Sonic, you can also use any valid domain email address that you've set up - this can be handy if folks reply to your emails, since you can filter by the To: address being @metaphorager.net instead of direct emails to your plain sonic.net address.
If I were to venture a guess, I'd say that the warning in that plugin is because if you were to put something like a gmail address in there, it would probably be rejected by some providers, since Google (and many others) use Sender Policy Framework (SPF) and other checks to detect and reject messages that aren't coming from the official servers for that domain. By default, we set up the necessary records so that a domain we host (such as yours) can send with email addresses from it. (*@metaphorager.net in your case)
-- Joe
Statistics: Posted by joemuller — Thu Dec 19, 2024 10:26 am
