On Fri, Sep 18, 2009 at 4:54 PM, Kevin <[email protected]> wrote: > > On Sep 18, 1:35 pm, The Editor <[email protected]> wrote: > 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.
Mailing lists are very important to me. I'd like to enhance this side of BoltWire at some point. This is a great suggestion. > 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. Where do you put this (in one of the header fields?), and how would it look in a real example. I'd have to double check the inbox plugin, but I'm almost sure it already extracts all the headers... No doubt I could use it to parse the return messages to get the original emails... If you could give me a little help with the details, I'm motivated to make it work. > 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. Right, I was thinking I could send it to a special mail box, then the inbox plugin can scan that automatically and process the emails, dropping the appropriate emails from my mailing list automatically, or upon request. It would take a bit of tinkering, but the hard part is all ready up and working. As you can see from all the spam here: http://www.boltwire.com/index.php?p=inbox :) >> > 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. Ah, this might help me. I have a fair number of people registering new accounts on my site say they are not getting their email. Particularly with gmail. This is a possible cause. I haven't seen the RFC specs, but it would be easy enough to include in the function. Can you tell me what format the date should be and what kind of MessageID I need. While I'm on the subject, the newsletter plugin allows for multi-part mime text & html messages. How important is that? It seems most people have roughly html compliant email programs don't they? Or do we really need both? Really glad for your expertise on this subject Kevin. Cheers, Dan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
