One of the challenges of writing a blog for 5 years is making sure we’re providing information our readers really want. I figure the easiest way to do that is to have you ask us questions about the things you want to know.
You can ask questions in the comments here, send them to laura-questions@wordtothewise.com or tweet them to me @wise_laura.
We’re back from our overseas adventures. I’m still wrapping my head around getting back to work. We had a great trip and did tons of fun stuff, including carrying torches through the streets of Edinburgh. I took almost 1000 photos which I’m slowly going through and posting on flickr.
I’ll get back to posting about email, but thought I’d share a couple of photos from Edinburgh behind the cut.
Over the years I’ve picked up a lot of useful and relevant information about email delivery. I’ve shared a lot of information here on the blog, and while that’s great, a blog is not a great format for a reference. The ISP information page was an initial pass at creating a reference. I realized that just linking to the ISP provided information didn’t communicate very much about how to deliver email even to those ISPs that were explicitly mentioned.
Enter the Word to the Wise Delivery Wiki to fill the need for a publicly accessible reference on email delivery. The cornerstone of the site is the ISP Information page. This page contains summary information about a number of ISPs, including known connection and sending limits. Each ISP mentioned on that page also has a individual page with more detailed information on delivering to that ISP. The information is as accurate as I could make it, and in many cases have been reviewed by representatives of the ISPs.
I welcome contributions from the general community. I will also be continuing to add content. My goal is to have a community resource for people handling email and delivery issues.
I don’t have a published comment policy. Most people around here are polite enough I don’t think one is needed. There are a couple things I feel I should say, though.
Read More