“Ok, I think I found the issue. I had to set the Sender From email field AND enable “Force From” email enforce the email address from which all mail should be sent – and now it works. I guess enforcing “from sender” email also enforces a the send domain for SendGrid. Thanks,
Hello here too, @standoutsites 😜
SendGrid’s sending API takes no domain at all. The only thing it needs from the plugin is the API key, and the request itself carries just the sender, the recipients and the message. So there is no Send Domain field in Meow Mailer because there is nothing to send it to.
The domain part lives entirely on SendGrid’s side, and it is almost certainly what is blocking you. SendGrid refuses any email whose From address is not a verified sender. In your SendGrid dashboard, under Settings then Sender Authentication, you have two options:
- Single Sender Verification, which verifies one address by email and takes a minute. Good for getting going.
- Domain Authentication, which adds DNS records for your domain and lets you send as any address on it. This is the one you want long term, since it is also what gets your mail through SPF and DKIM.
Whichever you pick, the From address in Meow Mailer’s Sender settings has to match what you verified there.
To confirm that is the problem, you can send a test email, then open that entry in the Meow Mailer log.
I actually think that you might have seen a Sending Domain field in another plugin 😊 That field is optional there too, and it is only used to check your SPF records when you send a test. It is not part of sending the email.
Cheers,
Jordy.
Haha, I see you had already solved it while I was writing that 😊
Your setup is exactly right! Force From makes every email use the address you verified, instead of whatever WordPress or another plugin decides to send as. That is precisely what it is there for, so there is nothing else to do.
Thanks for coming back to say what fixed it 😊
Cheers,
Jordy.
