Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Bounced email handling suggestions/spam prevention for social networksBounced email handling suggestions/spam prevention for social networks
Previous
 
Next
New Post
5/26/2009 8:55 AM
 

Hi,

this is not really a DNN query but it affects any site that sends mail and I need some opinions please.

Basically up until 6 months ago I was running as UnVerified on PokerDIY, which means that a lot of emails/users were using invalid addresses (just the nature of the beast). I highly recommend that you switch to Verified Users as soon as possible on your site to save this kind of pain later but that's another thread.

The problem I face now is that when I send a Newsletter I get a lot of SMTP errors and bounces. For example - out of 10 000 I might get 500 invalid emails/failed to send/unkown user etc. etc.

My question is: What should I do with these user records? From a spam point of view am I correct in thinking that every bounce is like a black mark against your SMTP server IP and after enough bounces your IP may be recorded on Email Blacklists?

If this is the case then I need to remove these emails (I am dogfooding the Proximity Mailer on PokerDIY which sends a monthly summary of users in your home town/area and country to each user so it will keep repeating otherwise). What I have been doing is setting all the emails to my own address and removing them from the Newsletter and other email roles so they do not get bothered in the future. Another option would be to set their account to UnAuthorised but then Google has ranked their profiles and I lose a lot of data and Google Juice by doing it this way.

If you think about it logically, if a user used a dodgy email there is NO way you can contact them, and there is no way they can request a new password, so you may as well change their email to your own. This way if they ever requested a password or someone else sent them a PM or something you would get it and at least know that the user was active. All PM notifications, event invites etc. etc. would otherwise bounce with the same message if you just left the record.

From what I understand the web mailing services (Constant Contact etc) automatically remove email addresses that bounce (is this correct, DotNetNuke Corp? You must get a few.) This is fine if you use their service but those records will still be live on your system and whenever your site or a person sends them mail from your IP the problem would remain.

Even verified users might have a valid email and then might not log into Hotmail for 3 months and their account goes inactive. Would this bounce the mail? If so, would you want to just leave it in case they re-activate it again? How do you differentiate between perm bounces and temp bounces?

Does anyone know more about mail/SMTP/spam/managing a social network wrt to emailing? I'd love to hear some thoughts...


Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
5/26/2009 1:15 PM
 

Your email troubles basically have nothing to do with email.  They are all related to how you selected the addresses to send email to.  You took a random group of email addresses, valid and invalid, and sent mail to them.  That's a great way to get blacklisted.  Only send email to subscribers, those who have specifically signed up for the email and validated their email addresses.  That eliminates 99% of your problem.

The last 1% is those users who have moved, died, been abducted by aliens or otherwise disconnected the email address they have on record with you.  This is easily handled by most mailing software automatically, unsubscribing those accounts when an email bounces.  And that's the second key, use mailing list software to send email, not a web application.

Jeff

 
New Post
5/26/2009 3:18 PM
 

I use getanewsletter.com for this and have no headace at all .....

 
New Post
5/26/2009 6:07 PM
 

Jeff Cochran wrote

Your email troubles basically have nothing to do with email.  They are all related to how you selected the addresses to send email to.  You took a random group of email addresses, valid and invalid, and sent mail to them.  That's a great way to get blacklisted.  Only send email to subscribers, those who have specifically signed up for the email and validated their email addresses.  That eliminates 99% of your problem.

The last 1% is those users who have moved, died, been abducted by aliens or otherwise disconnected the email address they have on record with you.  This is easily handled by most mailing software automatically, unsubscribing those accounts when an email bounces.  And that's the second key, use mailing list software to send email, not a web application.

All very true Jeff. If I had run with Verified from the start then I would not have this issue.

The problem is that it's unrealistic to expect a web app not to send email - every day there are private messages, event invites, group invites, game comments, blog comments, summary updates, PM notifications and 100 other emails whizzing around to users. Newsletters are just a tiny % of the emails that are sent. I want to address the bigger issue of how to handle invalid emails at core system level, not merely unsubscribing them from a role (either automatically using 3rd party mailing software or internally). I have seen APIs on sites like Campaign Monitor but I don't think it is sufficient for handling every day traffic of a large social network. If they are charging 1c a mail it would soon add up with all the notifications etc going out daily. There is a LOT of business logic in apps that can't be offloaded to a 3rd party service either.

The bottom line is that if a user on a social network has an invalid address then they need to be handled somehow.


Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
5/26/2009 6:23 PM
 

I completely agree with you Rodney.

1. You need a mailbox (or a couple) to capture the messages.

2. You need a method to read and parse the messages. 

3. Then you need an easy way to manage parsing rules and what actions to take. 

For example, the person may have a bad email address, but is very active on your site.  You don't want to remove the user.  You need to prompt the user to update their email address.  You also need to take into consideration the random DNS issues or mail server outages.  The email address may have bounced, but will be perfectly fine the next day.  I can think of about a dozen different rules with different actions that you would need. 

We have this on our road map for Active Social.  We will be using a pop3 client component and the DNN scheduler.


Will Morgenweck
VP, Product Management
DotNetNuke Corp.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Bounced email handling suggestions/spam prevention for social networksBounced email handling suggestions/spam prevention for social networks


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out