Issues when deleting subscribers from trash

Hi there @wlsfh,

Regarding the Welcome emails, yes that is expected behavior: welcome emails will only be triggered the first time they sign up, and switching to unsubscribed then resubscribing won’t trigger them again:
https://kb.mailpoet.com/article/360-troubleshooting-welcome-emails

Completely deleting the subscriber as you were trying to do would be necessary for sending the Welcome email again to the same address.

As for the issue you mentioned, after deleting the WordPress user, and then moving the MailPoet subscriber to the Trash, please try running the “Force sync” option on the WordPress users List under MailPoet > Lists. If the subscriber is still on the WP Users List then it would not be possible to delete them from the Trash, so re-syncing that list first will be necessary. Give it a bit to make sure it finishes syncing, then try deleting the subscriber from the Trash again.

Another recommendation, if you are testing with a Gmail address, you could try using the “+ trick” to create aliases and use those to sign-up.

If your address is “[email protected]”, you could try signing up on your MailPoet form with “[email protected]” — it will see it as a different address in MailPoet, but Gmail will still receive your emails:
https://www.cnet.com/tech/services-and-software/6-clever-gmail-tricks-to-minimize-regret-frustration-and-spam/

Hi

Thanks for the support.
Unfortunately did not work.

Let me explain further.
1) The test email is registered as WP User and well as Woocommerce Customer.
I tried to
a) delete user from WP->users
b) move user to trash
c) unsubscribed user
d) permanently delete
e) force synch as per your suggestion
Didnt work.
Does it have to do with Woo subs list?

If so, how do I permanently delete a user subs under a Woo lists? Db?

2) For testing purposes, I followed your gmail trick.
Although I manage to create a new account using the same email address and MailPoet sees it a [email protected], we still did not get any welcome message.
Guess MailPoet sees it as a duplicate?

Hi,

I’ve gotta rectify this.
Must have been the caching plugin, but I manage to get this to work using your force sync solution.

Brilliant!

Hi there @wlsfh,

Must have been the caching plugin, but I manage to get this to work using your force sync solution.
Brilliant!

Thanks for getting back to us here — glad to hear that it worked!

Yes, could’ve been something with caching, or if you have a huge number of users the sync may have taken a while. Anyway, glad it’s cleared up!

I’m going to mark this as resolved, but if you have any other questions, please feel free to open a new thread! Take care, and have a wonderful day.