reachmazharul

Hello @betamovement

Sorry to hear that whitelisting the [email protected] email address didn’t help you with your scenario. In this case, could you please share the console error if you are facing any? In order to do that please follow the guideline from here: https://getwemail.io/docs/wemail/f-a-q/browser-console-error/

Looking forward to hearing from you.

Hello @tdechangy

Thanks for writing back with all the details. We can understand why you feel this way. Please allow me to explain why we have adopted the SMTP approach for sending the email.

1. For sending a few emails it’s ok to use the WordPress built-in option which doesn’t need any additional configuration. But the weMail’ main purpose is to serve the use case of newsletters where it related to a huge number of emails. And sending that many numbers of emails via WordPress built-in way would be very difficult and it may cause some inconvenience depending on the hosting provider. But by using the SMTP this scenario can be managed.

2. Thanks for sharing your thoughts, we appreciate it. Yes, definitely it can be handy for our users and we have listed this on our future feature log. Hopefully, very soon we will be able to implement this feature on future releases.

3. Right now by default weMail may not be able to help you, to customize WooCommerce’s default notification and transaction email. But the good news is we have a recent plan for making available this feature.

Hello @tdechangy,

Thanks for considering weMail to serve your purpose. We appreciate it. Regarding the scenario you have mentioned, I would like to inform you that by using our included SMTP configuration, you can use any SMTP you like.

Sending email through SMTP is the most convenient approach that’s why we have built the included SMTP configuration in a way that you can use SMTP from any provider. It can be from your host ( if they offer ) or it can be any premium services, It’s totally up to your preference. From weMail’s side, there isn’t any restriction.

Hopefully, I was able to clear your concept. Feel free to let us know if you need more clarification on this or if I have misunderstood the scenario you are referring to.

Hello @betamovement

After several investigations, we have found that the SMTP service you are using, that service provider is creating inconvenience for our this domain/email: [email protected] This is the reason for the whole scenario you are experiencing. In order to solve the scenario please contact the SMTP service provider and ask them to whitelist this email: [email protected] Hopefully, this will resolve this.

Let me elaborate on the purpose of this email: [email protected] we use this email for handling the bounce emails. Like, if there is an invalid email then those will be enlisted/managed/handled by our this email: [email protected]

Hopefully, I was able o clear your concept. Please feel free to let us know if you need more clarification on this.

Hello @elliekennard

Sorry for the unexpected behavior that you are facing, from the plugin. After receiving your concern we have tried to reproduce the scenario but the afford wasn’t that successful.

Is it possible to let us know how can we reproduce that? If possible please share screenshots of your settings and configuration so that we can do that same to investigate. And please make sure there aren’t any theme/plugin conflicts.

Looking forward to hearing from you soon.

Hello @elliekennard,

Thanks for sharing all the details. After receiving your concern we have proceeded with some tests and we haven’t able to reproduce your mentioned scenario. In this case, it may cause by the internal theme or plugin conflicts.

Note: It’s highly recommended to take a full backup before proceeding with the conflicts test.

The following section provides instructions for determining if an issue you are experiencing is caused by a theme or plugin conflict.

1. Theme Test
=> Switch to the default WordPress theme as we know that the default WordPress theme is coded properly. Now try again and see if the issue is still there. Take note if you see a difference in behavior after you have switched the theme. Switch back to the theme you were using.

2. Plugin Test
If the theme didn’t have anything to do with the issue then move on to the plugins section. There are many WordPress plugins out there and not all of them are coded nicely so let’s see if you have a plugin installed that is not playing nice.
=> Try to deactivate the plugins excepts Subscribe2 then check again.

Let us know how it goes for you.

Hello @elliekennard

We are sorry for the scenario that you are currently having. Is there any error notice that you are facing? Is there a possibility that email has other activity on the website? Like, those emails are associated with website users?

Looking forward to hearing from you.

Hello @midey22

We are sorry for the inconvenience that you are currently experiencing. I can assure you that weMail is compatible with the latest version of WordPress.

After receiving your concern we have run some tests with weMail default forms, weMail integrated forms, and it seems like we didn’t face such a scenario. In this case, is it possible to share more details on this? Like, let us know with which form you are facing this error, is it the Embedded forms, and please share the error from the console that you may be having. To share the console error please check the guideline from here.

Looking forward to hearing from you.

Hello @betamovement

We appreciate your consideration of using the weMail. We are sorry for the experience that you are having, but till now we haven’t received or faced such an Error. That’s why it may hard to provide the solution with a single word.

After receiving your concern we have analyzed your Error and it seems like maybe there is a problem with your SMTP credentials. Or it’s not the exact SMTP credentials. Is it possible to make sure again that you have gathered SMTP credentials correctly and you have confirmed on weMail in the right way?

And if possible please share a screenshot of your SMTP credentials and your weMail fields credentials. You can share screenshots by making sensitive information blur. If you can do that it will help us to dialysis the scenario more investigative way.

About the Sendgrid bounce rate, in such cases, we recommend considering Double Opt-in. You can check more details and guidelines about the double Opt-in from here.

Let us know how it goes for you.

Hello @daihlo

After checking the available resource, it seems like the Geolocation module isn’t available on the Dokan lite. And as per the www.remarpro.com support policy, it’s not allowed to discuss a topic that is not associated with the free version.

Hello @victory98

We are sorry for the inconvenience that you are experiencing.

Is there any possibility that you are using any external SMTP plugin? If there is any, could you please deactivate that for testing purpose and try the whole scenario again? And make sure you are using the latest version fo the WordPress and the latest version of the weMail plugin. After doing the test, let us know the update.

Thanks.

Hello @autopilotdk,

Excellent, good to know. If you encounter any inconvenience in the future with weMail be sure to get in touch.

Hello @autopilotdk,

Thanks for considering weMail to serve your purpose. Till now, we haven’t experienced such an error that’s why I am sharing some basic scenarios to make sure you have fulfilled these.

–Make sure you have configured the weMail properly according to this doc: https://getwemail.io/docs/wemail/get-started/wemail-installation/ If you have done that, then check that you have configured the gateways. You can check the documentation here.

–If you have done the above configuration accordingly then check the fourth step of the Campaign which is Send. Here you will find a field called “Preheader” make sure you haven’t put the character more than 100.

Finally, check all the above basic scenarios and let us know the update.

Looking forward to hearing from you.

Hello @djek

We are so delighted to find such positive feedback on our work! We appreciate it. Thank you!

Best regards.

Hello @thesia122

Thanks for sharing the screenshots. Although it’s not a certain issue (It’s not certain in a way that, some of us didn’t face ), the weMail team currently working on a priority fix in the next release. We’ll keep you updated when it is out, to ensure you can get the fix. Thanks so much for your help and patience as we work to resolve this.