On Sep 18, 1:35 pm, The Editor <[email protected]> wrote: > On Fri, Sep 18, 2009 at 3:48 PM, Kevin <[email protected]> wrote: > BoltWire's newsletter does pretty good, but it doesn't process > bouncing or rejected messages yet. There is an inbox plugin (email to > wiki) with pretty advanced handling of incoming emails that could do > this quite nicely with a bit of work. Maybe one of these days. Now > that I figured out how the return-path header looks, I'll probably > have a good incentive to fix it. Specifically hundreds of bounced > emails next time I send my 5000 member mailing list. :)
Bounces can be a royal pain because where and how the bounce gets back to you may not indicated to whom you actually sent the message to. If it is rejected when your mail server tries to deliver it, you normally get back good details, but if the remote mail server accepts it and generates a bounce later (something they really shouldn't do), what you get back may not be anything decipherable in trying to figure out who it was originally sent to. This is especially true now days where people get email and then forward it to another email address or worse, forward it to a group of other non-subscribed users. Then many times you get a bounce for someone that was not even on the list. The best way to deal with this is the use what is called VERP style addressing where the envelope sender is converted to a unique address that when you get back tells you who the message was sent to. This can be done simply by taking the senders email and including it like [email protected] or more complete by making a unique id and storing that somewhere for lookup if you get it back. You have to get your mail server to accept that type of format though and know what to do with it. In simple cases, you just forward the bounces to a mailbox so you can look at them. > > From a mail admin stand point, it will be interesting to see the > > output of the headers... looking forward to see what that looks like. > > Just create a page with something like this: > > [(mail [email protected] [email protected] subject="whatever" > body=some.page#mail html=true bcc=group.editors [email protected] > [email protected])] RFC complaint mail will have: From:_ To:_ Date:_ MessageID:_ (unique) Many host mail servers will supply Date and MessageID if they are missing (but should only do so for the first hop) but a lot of systems look at those to determine spam and it easy to look at and see if they were generated properly. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
