WPIntell

Source evidence

SMTP module bugs

Admin and Site Enhancements (ASE) · support · 2026-06-29T10:38:00+00:00

complaintsentiment
highseverity
0.85relevance
6replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 17 rows with source links

23.5% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

13 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
VisedFAQ unresolved
Hi, first of all I’d like to thank you for the recent update where you changed the way STMP passwords are stored, because we already had situations when SMTP suddenly stopped working and we would lose some important emails because we didn’t even know that happened. However, there’re still a couple of issues. First of all the fact that I need to reenter SMTP password again on every webstite with new update (for us it’s 20+ websites using your SMTP module), because the old one can’t be decrypted anymore and SMTP is not working because of that: https://cleanshot.com/share/SM2gd8tR Another bug is that when I do change the password in the ASE SMTP settings and emails start working again, the password status still says “Not set”: https://cleanshot.com/share/hP5ysRC6 @visedfaq Thank you for reporting this. Did you originally perform the update to your 20+ sites via a website management tool like ManageWP or MainWP? So, remote update instead of manual update in wp-admin. Hi @qriouslad We do in general use ManageWP, but with first 2-3 websites I have updated plugin manually via WP admin. Also this “password decryption issue” message wasn’t actually consistent – it was shown for the website where the SMTP was working, and not showing for website with failing SMTP. That’s why I decided to update password everywhere just in case. @visedfaq I see. Thank you for the additional info. Will investigate further… your patience is appreciated. @visedfaq by the way, I’m guessing you were updating from 8.8.4 to 8.8.6? Or something else? Just trying to see if I can replicate the issue when manually updating. Hi @qriouslad No, I think I was actually updating from 8.8.0 or 8.8.1 @visedfaq noted. Will try to update from 8.8.0 and replicate the issue. Meanwhile, the password status bug has been confirmed and a fix for it will be included in the next release. This reply was modified 3 days, 12 hours ago by Bowo .

Comments

6 shown
Bowo 2026-06-29T14:43:00+00:00

@visedfaq Thank you for reporting this. Did you originally perform the update to your 20+ sites via a website management tool like ManageWP or MainWP? So, remote update instead of manual update in wp-admin.

VisedFAQ 2026-06-29T14:51:00+00:00

Hi @qriouslad We do in general use ManageWP, but with first 2-3 websites I have updated plugin manually via WP admin. Also this “password decryption issue” message wasn’t actually consistent – it was shown for the website where the SMTP was working, and not showing for website with failing SMTP. That’s why I decided to update password everywhere just in case.

Bowo 2026-06-29T14:53:00+00:00

@visedfaq I see. Thank you for the additional info. Will investigate further… your patience is appreciated.

Bowo 2026-06-30T11:25:00+00:00

@visedfaq by the way, I’m guessing you were updating from 8.8.4 to 8.8.6? Or something else? Just trying to see if I can replicate the issue when manually updating.

VisedFAQ 2026-06-30T11:39:00+00:00

Hi @qriouslad No, I think I was actually updating from 8.8.0 or 8.8.1

Bowo 2026-07-02T02:51:00+00:00

@visedfaq noted. Will try to update from 8.8.0 and replicate the issue. Meanwhile, the password status bug has been confirmed and a fix for it will be included in the next release. This reply was modified 3 days, 12 hours ago by Bowo .