|
Really? BulkVerifier (if I have read their
site correctly) should be detected by a good email server as a directory
harvest attack and blocked. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Matrosity Hosting we use BulkVerifier 1.2 which is $60, I think, and it
works great. We do this gratus for our clients so we don't have to worry about
bounces. We have a couple of clients that have a fairly large subscriber base fortheir newsletters -- one in particular sends email to about 29,000 emailaddresses each week, and the base of subscribers is growing.When they send their newsletter, of course a certain percentage, around 8 to10%, always bounce. Because the email list program they are using is notvery advanced, there is no real "cleansing" of the list taking place,unfortunately.The question is, what to do with the bounces. I've told them to monitor thePOP account that is the "FROM" address of their newsletter - that they needto check that address specifically for people that may just hit "reply" andask to be removed. It's also caused a problem when the POP account fillsup, and the double bounces start happening (yes, I could increase the sizeof the pop account, but that feels like "condoning" their lack of attentionto the account and the messages that come into it).The newsletters in general are certainly legit - people have to specificallysign up, and they have a link in the newsletter to unsubscribe which isalways honored.But what is considered "best practice" or "proper netiquette" when dealingwith the returns from a large newsletter mailing? What should I be askingthis client to do, as part of their responsibility for running thisnewsletter, weekly? Or should I just "lighten up" and delete the bouncesthat come in, since there's really no easy way to clean them up?Welcoming your advice,MarcTo Unsubscribe: http://www.ipswitch.com/support/mailing-lists.htmlList Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ |
