>>> The basic problem is allowing an ESP customer to import a list that >>> existed before the customer became a customer of this ESP. I can't >>> think of an ESP that would not allow that. >> >> I saw this again as someone replied to it. >> >> Sadly, there is at least one legitimate reasons to allow this: >> how else could a customer change ESP ? > > It should only be possible to import addresses from a list once or > twice, not on a regular basis. > > After that there should be an integrated opt-in process to verify any > new email address for that ESP customer's list.
While this sounds simple and like a no-brainer, it doesn’t account for how complex many companies email programs are. In many, many cases full customer data isn’t kept at the ESP - nor should it be. The ESP doesn’t need to know (and in fact absolutely shouldn’t know) things like credit card numbers or login passwords. There are also a number of systems that don’t keep email addresses at all. Mail is triggered through an API call and all of the email addresses are stored on the sender’s system, “lists” never go near the ESP. All the ESP sees are send requests. There are opt-in processes that don’t involve “signing up for a list” as well. You register an account with PayPal, or your bank, or whatever. Yes, those organizations should (and many do) have verification processes in place. But that should be handled by the data controller, not the ESP. ESPs have many, many problems, but the fixes being suggested here on mailop are overly simplistic and evidence a lack of conceptual understanding of how bulk email is sent in 2022. laura -- The Delivery Experts Laura Atkins Word to the Wise la...@wordtothewise.com Email Delivery Blog: http://wordtothewise.com/blog
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
