On Fri, Sep 18, 2009 at 3:48 PM, Kevin <[email protected]> wrote: > > Not really looking so much at newletters themselves as I already have > a number of mail list apps (Majordomo, Mailman, Constant Contact, > ElectricMail) in heavy use now.
One reason I wrote BoltWire was my difficulty interfacing between the website and the mailing list. Or a lack in features. Esp not being able to fully style the mailing list software to match my site, and the like. Probably just lacked the programming skills back then. 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. :) > I am also very reluctant to allow normal clients to play with email > without knowing first what and why they are doing it. Having spam > sent from a production RFC complaint mail server that has hundreds > domains that depend on solid mail delivery can be a huge issue very > quickly. No one should be able to send emails without you specifically creating a site.auth.email page. If you prefer we could add a config option that can shut down all emailing, or a mode that automatically makes it active mode (as per DM's suggestion above). That would be a good idea--I'll look into adding that into the next release. > 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])] On 3.14 this should output a full display of the email with all the hearders and everything for analysis. I welcome your feedback. I'm not an expert on email technologies. > However, I will have a REAL interest in the mail features of Boltwire > as I am going to be digging in real good this weekend on forms > processing and sending email from those though as I have a pressing > need for that at work now. Purpose is to provide forms with required > information for reporting issues, requesting lan drops, firewall > changes etc... I had planned on doing this in PHP, but now seeing > what Boltwire can do, I am switching tracks even though the learning > curve is a bit more. Make sure you get a handle on how templates work in emails. Put {+field} in the body wherever you want to insert various data from the form. You can put /* [[#mail]] field1: {+field1} field2: {+field2} [[#fend]] */ on the same page as the mail function and you don't even need the body parameter. It will find this automatically and do your field replacements. > We already have a help desk ticket system, but getting a ticket that > says, "user reports getting spam" is a waste of my time. We have > other departments that get similar info lacking messages all day long. You should be able to force all kinds of drop down menus and generate a nicely templated email--complete with info from their user profile if they are logged in. Direct to the right department, whatever. Quite cool. I've do some very nice things with my online store along these lines for quite awhile. Let me know if you get stuck. 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 -~----------~----~----~----~------~----~------~--~---
