Hit ENTER after each Tag to add it to your post; Numbers in parentheses represent the Tag's usage.
I have a system set up for clients to send opt-in bulk emails from their website through a SM bulk email server, and want to send the emails from: their domain, which is primarily housed on another, transactional email server. If Auth Bypass is set on, it works fine, as long as my email script logs in with the proper credentials. But that is a little dangerous. Hackers can obtain the un/pw and then go to town.
I have control of all my clients' DNS and have both the main and the bulk server IPs listed in their SPF record, but I still get the relaying error when attempting to send emails from their domain and I have Auth Bypass set off.
An expert on SM and email in general told me that mail servers always look locally, and never at the domain's DNS. This has always frustrated me, and made me wonder why the email server can't do a DNS lookup to see if sending the email is ok? The answer I was given was "this is how every email server works."
Me? I think it's just lazy. And don't tell me that it's a security feature. With all the other settings available in SM, an admin could wreak havoc and open the box wide to the world.
So, can someone from ST tell me if this is in fact the case, that email servers never check the DNS records for whether or not they are ok to send the email, and if so, why? I mean, DNS is fairly unhackable, just as much as any setting in SM.
Perhaps this could be added as another switch? "Check DNS for SPF Authority" or something.
Mik MullerMontague WebWorks