SMTP plugin changed to smtp-mailer
-
@d19dotca said in SMTP plugin changed to smtp-mailer:
Updating mailer settings
This log line is present in package v2.8.2 but not in v2.9.0.
@girish Okay something is weird, lol. So I tried a couple scenarios today restoring to the v2.8.2 package and then updating to v2.9.0 and then touching the plugins, and secondary scenario was touching the plugins prior to updating to v2.9.0 of the package - both scenarios worked.
At first I thought maybe the issue was that yesterday I had updated the package before I made any SMTP plugin changes, however it seems to be working fine whether before or after the package update today. And I'm certain I was on the correct package version yesterday because that was the only update available at the time (unless maybe it failed to update and I assumed it was successful?) - at least I'd be shocked if I somehow did all that testing without the updated package
If I did then... shame on me. haha.Quick question though as I found what appears to be one stumbling block now that it's actually configured... It seems set to "WordPress" as the "from name" and I'd rather that not exist and just be the email address as the from name instead as that's how all my sites are configured and how my clients are used to receiving emails from their sites for product orders and such. However, it seems that the password is needed on every single Save to the settings, which means I can't really update the settings at all. How does one go about doing that in this case? I guess we can just fill it in from the credentials.txt file each time?
--
Dustin Dauncey
www.d19.ca -
Actually I just realized I can kind of prove that I was running the correct version... here's a screenshot from the Events page: (blocking hostnames)
Notice it was updated to v2.9.0.
No idea why that wasn't working yesterday then after all that testing and suddenly working fine today.
-
I got SMTP Mailer to work but whenever I set the type of encryption to TLS, it reverts back to "No Encryption" after an app restart.
-
I got SMTP Mailer to work but whenever I set the type of encryption to TLS, it reverts back to "No Encryption" after an app restart.
-
@girish Okay something is weird, lol. So I tried a couple scenarios today restoring to the v2.8.2 package and then updating to v2.9.0 and then touching the plugins, and secondary scenario was touching the plugins prior to updating to v2.9.0 of the package - both scenarios worked.
At first I thought maybe the issue was that yesterday I had updated the package before I made any SMTP plugin changes, however it seems to be working fine whether before or after the package update today. And I'm certain I was on the correct package version yesterday because that was the only update available at the time (unless maybe it failed to update and I assumed it was successful?) - at least I'd be shocked if I somehow did all that testing without the updated package
If I did then... shame on me. haha.Quick question though as I found what appears to be one stumbling block now that it's actually configured... It seems set to "WordPress" as the "from name" and I'd rather that not exist and just be the email address as the from name instead as that's how all my sites are configured and how my clients are used to receiving emails from their sites for product orders and such. However, it seems that the password is needed on every single Save to the settings, which means I can't really update the settings at all. How does one go about doing that in this case? I guess we can just fill it in from the credentials.txt file each time?
@d19dotca said in SMTP plugin changed to smtp-mailer:
Quick question though as I found what appears to be one stumbling block now that it's actually configured... It seems set to "WordPress" as the "from name" and I'd rather that not exist and just be the email address as the from name instead as that's how all my sites are configured and how my clients are used to receiving emails from their sites for product orders and such. However, it seems that the password is needed on every single Save to the settings, which means I can't really update the settings at all. How does one go about doing that in this case? I guess we can just fill it in from the credentials.txt file each time?
There is code to make sure that the from name is persisted across restarts. So, if you change it to something from the default 'WordPress', it will not get overwritten. But as you pointed out, you need to also fill up the password field (which is in credentials.txt) listed under Sendmail Credentials to update it. I will try to report this in the smtp-mailer plugin.
-
@humptydumpty the encryption should not be TLS but be none. The connection is internal to the server and TLS is disabled for internal connections.
@girish Thanks Girish. It's just a bit confusing for noobs like me when there's a "recommended" tag for TLS. No harm done as it won't keep that setting anyway.
-
@d19dotca said in SMTP plugin changed to smtp-mailer:
Quick question though as I found what appears to be one stumbling block now that it's actually configured... It seems set to "WordPress" as the "from name" and I'd rather that not exist and just be the email address as the from name instead as that's how all my sites are configured and how my clients are used to receiving emails from their sites for product orders and such. However, it seems that the password is needed on every single Save to the settings, which means I can't really update the settings at all. How does one go about doing that in this case? I guess we can just fill it in from the credentials.txt file each time?
There is code to make sure that the from name is persisted across restarts. So, if you change it to something from the default 'WordPress', it will not get overwritten. But as you pointed out, you need to also fill up the password field (which is in credentials.txt) listed under Sendmail Credentials to update it. I will try to report this in the smtp-mailer plugin.
-
@d19dotca said in SMTP plugin changed to smtp-mailer:
Quick question though as I found what appears to be one stumbling block now that it's actually configured... It seems set to "WordPress" as the "from name" and I'd rather that not exist and just be the email address as the from name instead as that's how all my sites are configured and how my clients are used to receiving emails from their sites for product orders and such. However, it seems that the password is needed on every single Save to the settings, which means I can't really update the settings at all. How does one go about doing that in this case? I guess we can just fill it in from the credentials.txt file each time?
There is code to make sure that the from name is persisted across restarts. So, if you change it to something from the default 'WordPress', it will not get overwritten. But as you pointed out, you need to also fill up the password field (which is in credentials.txt) listed under Sendmail Credentials to update it. I will try to report this in the smtp-mailer plugin.
@girish Regarding the FROM name issue. I set my own site name there instead of Wordpress and hit save. Then, a misconfiguration error appears but an app restart will fix that and the modified FROM name is still in there. I tested it for both sites and it's working fine for me using this method.
-
Turns out
base64CLI tool output is multi-line by default
. This caused some updates to fail. An update has been pushed, in case your WP failed, just Updates -> Check For Updates and apply the update.The fix was to use
base64 -w 0(width 0 means all output is in a single line. the default width is 76) -
I'm impressed at the speed of development on that SMTP-Mailer plugin. They already released an update to resolve the request filed on being able to update some settings without needing the password each time.
Thanks for handling that, @girish!
--
Dustin Dauncey
www.d19.ca -
I'm impressed at the speed of development on that SMTP-Mailer plugin. They already released an update to resolve the request filed on being able to update some settings without needing the password each time.
Thanks for handling that, @girish!
Sorry about that.