Re: [WebDNA] Sending emails

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105929
interpreted = N
texte = --20cf30549e51599eba0494b52a1c Content-Type: text/plain; charset=UTF-8 Will, I have done a fair bit of work on email deliverability recently. I don't throttle the sending of emails - I have clients 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 send out emails that have 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 configured 2. add spf records (sender id) in to your dns settings 3. implement DomainKeys on your server 4. configure a bounce management 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 (hotmail, yahoo, etc) The next thing I am going to implement is a system to track subscribers who do not engage - i.e. the email appears to be delivered by they never open the email or click on any of the contained links. These subscribers should be removed after a certain 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 papers on deliverability - http://www.returnpath.net. I'm happy to share any of the code I use for the above - I think the bounce management code (modified POP downloader) is already on the list. Take care - Tom --20cf30549e51599eba0494b52a1c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Will,

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:

<= /div>
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:

    
  1. RE: [WebDNA] Sending emails ("Will Starck" 2010)
  2. Re: [WebDNA] Sending emails (Tom Duke 2010)
  3. [WebDNA] Sending emails ("Will Starck" 2010)
--20cf30549e51599eba0494b52a1c Content-Type: text/plain; charset=UTF-8 Will, I have done a fair bit of work on email deliverability recently. I don't throttle the sending of emails - I have clients 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 send out emails that have 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 configured 2. add spf records (sender id) in to your dns settings 3. implement DomainKeys on your server 4. configure a bounce management 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 (hotmail, yahoo, etc) The next thing I am going to implement is a system to track subscribers who do not engage - i.e. the email appears to be delivered by they never open the email or click on any of the contained links. These subscribers should be removed after a certain 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 papers on deliverability - http://www.returnpath.net. I'm happy to share any of the code I use for the above - I think the bounce management code (modified POP downloader) is already on the list. Take care - Tom --20cf30549e51599eba0494b52a1c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Will,

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:

<= /div>
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-- Tom Duke

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

WC2b15 File Corruption (1997) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) Migrating to NT (1997) php vs WebCatalog (2000) Is this possible, WebCat2.0 and checkboxes (1997) Bad match! (2002) OT - How to pay commissions to non US affiliates? (2000) Security (1998) banner ad redirection page (1999) OT: Just for a waste of time (2003) Re:Searching for ALL / empty form field (1997) [/application] error? (1997) stripping extra spaces from form fields (2000) [WebDNA] WebDNA developer (2008) RequiredFields template (1997) [protect] on NT? (1997) Introduction/Tutorial/QuickStart (1997) What if SSL server down? MAC (1997) WebCat2 several catalogs? (1997) webmerchant 3.0 questions (1999)