We have a smtp server for sending email ,but recently we found that when we send hundred of newsletter to *@yahoo.com at a short time, it will blocked them. any one have better solution to solve it ? Thanks in advance!
|
migrated from stackoverflow.com Aug 26 '09 at 13:18
|
Are you following Yahoo's Best practise guidelines as seen here? Also, have you filled in the form here? |
|||
|
|
|
It seems that Yahoo recognises spam when it sees it. |
|||||||
|
|
They key here is "within a short time." If the IP you're sending from is unrecognized and doesn't have a "reputation" built up yet, then many of the server providers will throttle the number of messages they will accept from you over time. Some suggestions:
|
|||
|
|
|
General problems with sending mail (either high or low volume):
I think that is about it - hopefully you are not "spamming" and this is some sort of double opt-in list and also it is CAN-SPAM compliant. |
|||
|
|
|
I hate to be the one to tell you this but you are going to run into constant issues with getting email delivered. As time goes on some individuals will mark your emails as spam, which will get your ip address listed as a spam source. You ability to get email delivered will get worse and worse. I recommend that you outsource email delivery to a company such as Aweber.com or Getresponse.com (there are several more good ones). These companies will manage your deliverability for you and remove this immense headache from your life. Good Luck |
|||
|
|
|
|
|||
|
|
|
You can setup a feedback loop with yahoo to check your emails are not taken as spam by your recipients. |
|||
|
|
|
I have seen this behavior with Yahoo in the past. They do greylisting so when you start sending much email to them it starts getting delayed. I have seen email delayed for up to 72 hours in the past. As Zypher pointed out they have a form to register for bulk email. Probably your best bet is to use a service like mail chimp to do your bulk mailing. |
|||
|
|
|
You're likely sending from a residential IP block. Does your ISP have a gateway SMTP server you should be using? |
|||
|
|
|
When the users registered for the newsletter, you should have sent an email confirmation to them. This way, as long as people don't mark you as spam, you will be an established contact, so to speak. Since you have already had an email correspondence with these people, Yahoo is less likely to block your mail. If there was no prior communication, Yahoo will assume that a bulk mailer is spam. Also, certain key words in your message will flag the spam-blocker. |
|||
|
|
|
If you are legitimately sending bulk email to yahoo the have a form (go to contact at the top they won't let me directly link) you need to fill out so that your email doesn't get blocked by their anti-spam system. If you have DomainKeys and SPF setup you can get feedback from them on who is marking your newsletter as spam so you can remove them from your mailinglist pro-activly to avoid hitting their spam threshold again. |
|||
|
|
|
Consult the Yahoo Postmaster site. http://help.yahoo.com/l/us/yahoo/mail/postmaster/ |
|||
|
|
|
If you are using Mailman to deliver your newsletters, you might need to configure your SMTP_MAX_RCPTS setting in the mm_cfg.py file. At the bottom of the mm_cfg.py file, type:
This will batch the number of messages sent to one domain at a time, if I recall correctly. By default, the number is 500, I believe. We had problems delivering to Hotmail until we knocked this number down. You can go even further if you like. |
|||
|
|