> Unfortunately, the export also includes people who've unsubscribed (why does Mailchimp keep these?!)
Isn’t this illegal, in many countries? I guess the rationale, is so that you can tell them they unsubbed, in the past, if they try to sign up again. I suspect the real reason is not so wholesome.
It’s a problem. I once got spammed by the legit admin of a site I had deleted my account from, years previously, because he scraped the DB. He used it to try ginning up followers for his new personal Twitter account.
Because (accidentally) mailing an unsubscribed user hurts your deliverability. And because there are users out there that will attempt to add spam traps to your mailing lists, sou you keep them off the list
(double opt-in doesn't really help with the latter as you're still mailing it)
> Because (accidentally) mailing an unsubscribed user hurts your deliverability.
Simple solution: completely remove the email, and flush the cache. No accidental mailing.
As far as spamtraps go, I don’t think there’s a way to realistically address this. There’s a couple of well-known services, like spamex, but it’s easy to set them up, if you have your own domain.
I use spamex, because I want people to know it’s a spamtrap.
Makes sense, but I have a system that does something similar. I handle it, by having a separate, temporary DB that has the transitional data, which is completely erased, once we have set up the account.
Isn’t this illegal, in many countries? I guess the rationale, is so that you can tell them they unsubbed, in the past, if they try to sign up again. I suspect the real reason is not so wholesome.
It’s a problem. I once got spammed by the legit admin of a site I had deleted my account from, years previously, because he scraped the DB. He used it to try ginning up followers for his new personal Twitter account.