Hello @t-rek,
I understand your concern regarding reauthorization when using FluentSMTP with staging websites.
The issue stems from the fact that some SMTP connection types rely on the website-specific URL to generate an authorization token for email sending. When you stage your website, the URL changes, rendering the token invalid. This is why you encounter the reauthorization requirement when pushing the staged website live.
To handle this type of case, you may consider the following options based on our experiences:
- Switch to an SMTP connection type that does not require a website-specific URL, such as “Other SMTP,” “SES,” or “Google Workplace.”
- After staging your website, manually update the SMTP connection details, particularly the sender’s email address which may be changed by the method of the staging site creation. This should ensure that the connection remains valid after the URL change.
I understand that this can be an inconvenience, and I have forwarded your feedback as a feature request to our development team. They will explore the possibility of implementing a more seamless staging workflow in future releases.
In the meantime, I kindly request you to reconsider your review based on the overall functionality and benefits that FluentSMTP provides. Your feedback is invaluable to us, and we are committed to improving our plugin based on user experiences.
Thank you for your understanding and continued support.
