1. ensure the sending IP has reverse dns correctly configured
2. add spf records (sender id) in to your dns settings
3. implement DomainKeys on your server
4. configure a bounce mana=gement system to remove subscribers who bounce
5. ensure you can =receive 'postmaster@' and 'abuse@' emails addressed to the ='return-path' domain
6. sign up for feedback-loop services from the major mail providers (h=otmail, yahoo, etc)
The next thing I am going to i=mplement is a system to track subscribers who do not engage - i.e. the emai=l appears to be delivered by they never open the email or click on any of t=he contained links. =C2=A0 These subscribers should be removed after a cert=ain period of time as their lack of engagement will affect your 'sender= reputation' and they could also be spam traps.
These guys provide a lot of free advice and white paper=s on deliverability -
http://www.retu=rnpath.net. =C2=A0 I'm happy to share any of the code I use for the= above - I think the bounce management code (modified POP downloader) is al=ready on the list.
Take care
- Tom
--20cf30549e51599eba0494b52a1c--
Associated Messages, from the most recent to the oldest:
--20cf30549e51599eba0494b52a1cContent-Type: text/plain; charset=UTF-8Will,I have done a fair bit of work on email deliverability recently. I don'tthrottle the sending of emails - I have clients sending to lists of up to15000 subscribers and my setup pushes the emails out at about 360 perminute.I bypass the WebDNA emailer and use a shell script to send out emails thathave been written to disk by WebDNA. That also enables me to add a custom'return-path' header for each subscriber.The main things I have focussed on are:1. ensure the sending IP has reverse dns correctly configured2. add spf records (sender id) in to your dns settings3. implement DomainKeys on your server4. configure a bounce management system to remove subscribers who bounce5. ensure you can receive 'postmaster@' and 'abuse@' emails addressed to the'return-path' domain6. sign up for feedback-loop services from the major mail providers(hotmail, yahoo, etc)The next thing I am going to implement is a system to track subscribers whodo not engage - i.e. the email appears to be delivered by they never openthe email or click on any of the contained links. These subscribers shouldbe removed after a certain period of time as their lack of engagement willaffect your 'sender reputation' and they could also be spam traps.These guys provide a lot of free advice and white papers on deliverability -http://www.returnpath.net. I'm happy to share any of the code I use forthe above - I think the bounce management code (modified POP downloader) isalready on the list.Take care- Tom--20cf30549e51599eba0494b52a1cContent-Type: text/html; charset=UTF-8Content-Transfer-Encoding: quoted-printableWill,
I have done a fair bit of work on email deliverabi=lity recently. =C2=A0 I don't throttle the sending of emails - I have c=lients sending to lists of up to 15000 subscribers and my setup pushes the =emails out at about 360 per minute.
I bypass the WebDNA emailer and use a shell script to s=end out emails that have been written to disk by WebDNA. =C2=A0 That also e=nables me to add a custom 'return-path' header for each subscriber.=
The main things I have focussed on are: