Thomas Duerlund Falkenberg

Hi @wfpeter

This has happened before and now was on new sites with no prior config or just the standard config.

I haven’t checked manually. Bot even though. I would like to count on what Central says, because I use it so I don’t have to login to the sites to do changes.

Hi @dakeg

Thank you for the good and eloborate answer. For me it’s shady when Easy WP SMTP is taken over without any statement other than logos in the plugin. And many used that plugin, because they didn’t want to use this one. You could have been more open and communicating about it.

Great to hear that features and qualiy will come to them both.

How are you positioning them from each other?

Plugin support members from the Easy WP SMTP plugin are also active in the WPmail SMTP forum..

I don’t see any issues with that. I’m nor using WPmail SMTP either and are not going to.

It has to be a light SMTP plugin with the security in order.

Second this. It causes issues on the in WordPress and with the rest API.

Hi Andrea,

There’s still issues with the plugin. Updated a few days ago and it only updates some of the .htaccess file while leaving the rest with stuff from previous version.

Thank you for the answer @capuderg.

I just don’t want a plugin that does all these things and is filled up with all this stuff. That’s exactly why we loved this plugin and didn’t use WP Mail SMTP by WPForms, because that does that and it’s annyoing.

We want a small plugin that only does the required stuff. Creating a compact mode is not enough.

Thanks. @hpr78 !

I’ll take a look and do some testing on it. I don’t need these commercially. Basically they just went bloatware and I need something lite the does the just with our current setup, not a new provider.

Hi Andrea,

I have tested this on .16, 17 and now 18. The issue still persists. I have to deactive and active the plugin in order to update te .htaccess file with the new changes.

Hi Andrea,

Thank you so much for the help. ?? Great to hear you was able to fix it.

Hi Andrea,

Thaks for getting back to me. WordPress is latest stable version 6.1.1 and all plugin that supports automatic update is set to that.

This happens across multiple site and sites with different server setup. All running latest WordPress version.

Hi @isaumya ,

I have tried to manually enter it as well. Still the same issue. I think you’re right with the PHP decoding.

But we’ll just use the API key instead. That works as expected.

Thanks for all your help! ??

– After you enter the API Token & Email ID you need to click Update settings and not Verify.

Yes, my bad. Update Settings. But nothing happens. It stays at step 2.

• This reply was modified 3 years, 8 months ago by Thomas Duerlund Falkenberg.

I tried again @isaumya with the same result.

I have noticed when I’m using the API key then in the dropdown the name of the domain is spelled with ? (haneh?j.dk), but when using the API token it populates the domain as xn--hanehj-fya.dk.

Hi @isaumya,

It’s totally possible I’m doing something wrong.

I deactivated and then deleted the plugin. I even changed the setting so it deleted the settings when I’m deleted the plugin. Then I went to the server and deleted any folder still there related to the plugin.

Then I downloaded the version you sent me and installed that and then started the process of verifying the API token and all the settings needed.

The domainname was populated as xn--hanehj-fya.dk. But nothing happened when I clicked Verify.

I’ll try and do it again. ??

Hi Saumya,

I can’t get it to work here still.