I just wanted to see how everyone sets up SMTP for client sites. Currently, I’m creating an additional email in their cPanel, such as info@ or contact@, or an exisitng email if there is which they rarely use. Then, I set it up with the “Other SMTP” option in the Fluent SMTP plugin. However, for clients who use Google Workspace or O365, it’s a chore to log in to their O365 account and go through the setup process for Fluent or WP Mail SMTP to work as I can’t use Other SMTP option, and have to choose the O365 or GWorkspace option.
Now, I’m considering creating an account with SendInBlue or SendGrid. I would add each client’s domain to the account, complete the DNS verification and setup process, and then use that. Alternatively, should I create SendInBlue or SendGrid accounts on behalf of each client and set it up that way?
I’m unsure whether I should do it under my account or the clients’ accounts. I’m just trying to find the easiest, simplest, yet best and free way to do it. Thanks all!https://www.reddit.com/r/Wordpress/comments/14nmemz/best_way_to_setup_smtp_for_clients_websites/
In response to the question about the best way to set up SMTP for client websites, /r/wordpress has provided a wealth of insights. The suggestions vary, reflecting the varied approaches of different agencies.
None of them recommend using the client’s existing web server, while others advocate for setting up an external mail service for the client or even letting the client use the agency’s external mail service. Each of these strategies has its own set of advantages and drawbacks, and the best choice depends on a variety of factors. To help you navigate these options, we’ve summarized the community’s insights into a handy table below.
|1. Using the client’s existing web server for sending emails||– Simple to set up, no need for additional services|
– No additional cost, as it uses existing infrastructure
|– Consumes server resources, which could affect website performance|
– Not suitable for high volume of emails, as it may lead to delivery issues
– Limited features compared to dedicated email services
|2. Setting up an external mail service for the client||– Resolves email delivery and IP reputation issues|
– Provides additional features like delivery reports, logs, and better control over the email sending process
– Offloads the task of managing a mail server, freeing up server resources
|– Requires setup and potentially cost, depending on the service chosen|
– May require managing DNS settings, which can be complex
|3. Letting the client use the agency’s external mail service||– Cost-effective for agencies with many clients, as the cost per client can be quite low|
– Agency manages the service, reducing the technical burden on the client
– Can provide a consistent email sending experience across all clients
|– Can be complex to manage external DNS settings for each client|
– Costs need to be incorporated into the client’s contract, which may affect pricing
– The agency needs to manage and maintain the service, which could be a burden if there are many clients
– Complicates handover if/when the client leaves for another agency.
Clarifier: The external mail services mentioned in approaches 2 and 3 can be accessed either via SMTP or API. SMTP access is more general and can be used with most WordPress mailer plugins, providing a broad compatibility. However, it introduces another moving part into the mailing process, which could potentially complicate troubleshooting. On the other hand, API access is provider-specific, which may limit the choice of services, but generally offers more reliable performance than SMTP, as it allows for direct interaction with the service, reducing the number of steps in the mailing process.