On Jun 22, 2007, at 1:24 PM, John ORourke wrote:
The database idea has some good uses - I run 120 shop sites and of
course they're constantly sending out account confirmations, order
updates, etc. Currently there's no way of easily tracking what
happened to an email or finding out when, for example, hotmail
decides to completely ignore a password confirmation request. If
each email (or a representation of it) were stored, a status field
could easily be updated by something processing the mail server logs.
Of course, all that could be wrapped up as one of several email
sending methods.
you could put a guid in the email headers, and log that to the
database along with metadata about the message sending.
if the message bounces, or there's an error at the mta level, you'll
get the guid back. you could do it in the message body too, but
thats messy to the user.
some smtp servers will give you their own guid for the message if you
set stuff up right-- but thats not standard across systems.
// Jonathan Vanasco
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| CEO/Founder SyndiClick Networks
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| Founder/CTO/CVO
| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
