Quote:
|
Originally Posted by jestep
We are looking for a hosted or server based solution. Depending on sign up percentages, we could be looking at 10K+ per month if even a fraction of visitors sign up for it.
A server side solution would probably be the easiest for us to manage ourselves. Dedicated IP is no problem. Email delivery is important so we aren't sending emails to bad addresses. Beyond that, its not currently an issue.
RSS isn't that important immediately, but I'm sure that it will come up in time.
Thanks for your reply, and I will take a look at the companies that you talked about.
|
A couple of additional comments:
* Since you will be sending requested bulk mail, I would look into publishing a sender policy framework (SPF) record.
(For the details on SPF, read this
article. The article includes links in the footnotes to the formal protocol, along with the resource page Microsoft has set up and a wizard, to aid you in publishing the appropriate record.)
* Given your monthly volumes, you may want to consider a dedicated hosting solution, or at least a solution which ensures you are the only one using the mail server to send mail.
(If you are looking at a shared solution, you will want to ensure that the message headers include a functioning email address for the return path and that the message header properly identifies your IP as the originator and not local host.)
In chosing a solution, make sure the assigned IP is clean and if you are renting space from a data host, you check the AUP to make sure they won't go off the wall, if someone complains.
* If your list is, or you plan on setting it up, so that it is closed loop verified, then look at getting white listed with Yahoo!. Also, look into getting white listed with AOL.
(For the details on Yahoo! go to the help section on bulk mail and for AOL, go to the postmaster page.)
Also, set up a feed back loop with AOL.
* Manage your bounces. You should remove hard bounces right away and soft bounces after no more than 3 attempts.
* Check your message headers to ensure everything is RFC compliant and "clean."
* Run your content through SpamAssassin, to review for issues. You want to have as low as score as possible, with 0 being preferred.
(The benefit of using a "good" third party provider is this type of service is included.)
Another reason why I suggest
Send Studio if you are looking at a server side solution is that:
* The software allows you to generate "clean" headers - the footprint from the software is not known as ratware; and
(This helps with delivery. Some of the "cheaper" software has been used and abused.)
* The software provides you with bounce management capabilities.
(There are other good software programs on the market. Price wise, you are going to be into the $200 to $300 range for anything worth while and that has good support.)
Trusting these additional comments are of assistance.
Regards,
John Glube