If your team sends newsletters through a custom SMTP provider, every send could
fail with:
Please configure your sender settings for this SMTP provider
The confusing part was that this happened even when the campaign clearly had a
From name and From address filled in, and the email provider had a sender
address of its own. The only way through was for the person who created the
campaign to also save personal sender settings for that provider.
The cause was an internal mismatch: the newsletter sender was being handed to
the mail-sending code under a name that code never looked for, so it concluded
no From address had been supplied at all and refused to send.
What you may notice
- Newsletter campaigns on a custom SMTP provider now send using the campaign’s
own From name and From address, with no per-user sender settings required. - Campaigns sent through Outlook / Office 365 now use the campaign’s From
address too. Previously these did not fail, but quietly substituted the email
provider’s default sender, so newsletters could go out from the wrong address.
What this doesn’t change
If the person who created the campaign does have their own sender settings
saved for that provider, those still take precedence — same as before. And a
campaign with no From address anywhere (neither on the campaign nor on the
email provider) is still refused rather than sent from a blank sender.