It's gone through some revisions. Probably needs better documentation.
I use it for a large mailing list of 5000 people, sending them out at
a throttled rate over 24 hours or so. Works very nicely. Can do
direct mail merge with member accounts and use member id or email or a
mixture even. But if I sent out with a bunch of BCC's it would take
minutes instead of ours.
Still adding some basic bcc functionality to the core would be very
cool. Right now I'm thinking of using site.auth.email.bcc, and
requiring that that page be created in order to get the functionality.
Then I could set permissions to a group @class and dynamically set
memberships in each class if in the roster. Instant multiple mailing
list system for each group. And using bcc is very fast.
By the way you can already do the equivalent of a cc to the mailing
list by simply inserting a csv list into the To: field... Which
BoltWire can generate nicely like this: [(mail to='{(list some.page
fmt=csv)}' from... ...)]. Of course the more usual use would be a
form...
Cheers,
Dan
On Fri, Sep 18, 2009 at 5:02 AM, DrunkenMonk <[email protected]> wrote:
>
> I tried to get newsletters working a long time ago, but could never
> get mail to send, so I put the project on hold and upgraded the
> interface to postfix lists on my server.
>
> It would be nice to get it working sometime, but I don't have time
> now.
>
> On Sep 18, 1:48 am, The Editor <[email protected]> wrote:
>> Is anyone using BoltWire for newsletters and the like? I find it's
>> mailing list capabilities quite good (esp with the newsletter plugin),
>> but I just discovered a way to improve it.
>>
>> I was researching how to get the Return-Path header correct. Easy
>> enough. In the process, I noticed how easy it would be to send CC and
>> BCC emails. For example, suppose you used the logging function to
>> allow members to add their email address (from their profile) to a
>> list somewhere. Then in the mail function you simply do BCC=some.list.
>> Automatic, instant sending out to everyone on the list. Or better
>> still, how about group=editor, and your email goes to automatically
>> (BCC) to everyone in the editors group. For the latter, you just need
>> to retrieve each email from their profile. The code is trivial.
>>
>> The problem is security. How do I limit this kind of functionality?
>> One idea is to only allow admins access to the group or CC/BCC
>> functions. Or we could rely on current authorizations controls,
>> perhaps with an added site.auth.email.cc or site.auth.email.bcc.
>> Perhaps a config flag that has to be flipped on to allow. Or should it
>> be left strictly for a plugin--perhaps via a simple hook? For that
>> matter, should the newsletter plugin be modified somehow so it has an
>> option to send out bulk email much faster. IE, 25 BCC at a shot,
>> rather than one at a time. The mail merge is nice, but not critical
>> usually.
>>
>> Just thinking out loud, But the possibilities excite me. I do a lot of
>> stuff with emails and groups (classes) and newsletters and the like.
>> So while really simple in terms of code, it's a pretty big
>> breakthrough for me. Feedback on the security issue is welcome.
>>
>> 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
-~----------~----~----~----~------~----~------~--~---
