An friend of mine obtained a list of 10,000 email addresses from from a data-harvesting effort on an open-source state-sponsored website. (My friends actions were covered by FOIA, http://www.justice.gov/oip/foia-resources.html
.) He then took 1000 of his 10,000 addresses and sent out a marketing email via MailChimp. The marketing email was effective, but MailChimp complained that the 1000 addresses had a 16% bounce rate.
In an effort to weed-out the bad emails, my friend created a new Gmail account and built a .NET tool to send a test email to the 1000 addresses. Presumably, any bounce in the Gmail account's inbox indicated that the address was bad.
Initially, all went well. Bounces from bad email addresses and bad domain domains started appearing in the Gmail account's inbox, but then the following messages started to appear:
Technical details of permanent failure:
Message rejected. See http://support.gTechnical
details of permanent failure:
Message rejected. See http://support.google.com/mail/bin/answer.py?answer=69585
for more information.oogle.com/mail
r=69585 for more information.
The recipient domain wasn't bouncing the message, the GMail SMTP server was bouncing the message. The bounce is understandable. Google doesn't want to be party to spammers. One of its anti-spam algorithms picked up on my friend's .NET tool.
My friend would like to minimize is impact the Gmail system and on the email recipients, but he would also like to weed-out the bad emails. Suggestions?