← login as normal email and password is registered on TV

#BulkEmail #newsletters #MailingProceduresystem #emailListVerify


anyway null … my point is can i focus back on this … and end up sharing something with denise and maybe keeping this enterprise together so that it can support thinking.live untill that can survive on its own.

Note 1:  If you are using SparkPost for email delivery, you might expect that you can determine which email addresses in a mailing list resulted in bounced messages by logging into the SparkPost website, clicking on Reports and then Bounces. But, though that will give you a total number for bounced email messages and the percentage of messages that bounced, and even the reasons email bounced, the report doesn’t identify the individual email addresses that caused email to bounce. To see particular addresses that caused email to bounce, if you click on Lists, rather than Reports, and then click on Suppressions and check the check box next to Bounce Rule and click on Search, you will see recipients email addresses listed that triggered a bounced email.

if you click on the SAVE AS CSV button at the bottom of the page, you can obtain a comma-separated values (CSV) file.

Also see more re getting bounces etc throu the API here.

Also see SparkPost doc re supression lists here.

the list of reasons verify has to reject the emails are here.

Alex’s bot just sent me a video … not that i didnt already know that stuff null

okay 25,031 emails to be verified here with #EmailListVerify

25k X $4/k = ~ $100 … well within our budget
and i expect this is a one time expense null

i wonder if i can find the email list from here → nope, it is still locked in a different partition of this computer.
… hmmm maybe time to do it live from denises ← #done 

do i have access here now? … … i do … but unlinked for the sake of the email addresses owners privacy.

Here is the sample input-to and output-from the #EmailListVerify tool …

and here is the screen shot from the page from which i recieve the results …


Changing my estatus coding now.
  • “old” → prior to cutoffdate and never to be used
  • “” → unverified – newly introduced, not yet emailed to and hence verified
  • “ok” → verified
  • unsubscribe = “unsubscirbe”
So email output file, emaillist.csv,  should be selected as per …
\!empty(email) and (empty(estatus) or estatus = “ok”)


#shucks i have been waiting for Alex to process this file for over 8 hours now.

Bad #timeing …
i do need to #grasp this now …
but i can not.

#OhWell … moving on anyway …

null #OMG Alex finally made the run ...

you’d expect this to be automated … but apparently one needs to wake Alex up so he can do it manually.

The figures match  my anticipations.