improve flexmail for bulk mailing


improve flexmail for bulk mailing+status
improve flexmail for bulk mailing+priority
improve flexmail for bulk mailing+tag
improve flexmail for bulk mailing+commit

improve flexmail for bulk mailing+issues

Here are the key use cases we need to make wagneerable on

  • Send custom emails to any group of users that can be returned in a wagn query.  This includes:
  • all users
  • all users with a given role (eg. Pack Leaders, Rangers, or Pack Members)
  • all users with a given role in a given territory
  • Send a templated email to invite a new user to look at the site (without automatically creating their account, as currently happens).  So a signed-in user would see an empty "email" box and prepopulated "subject" and "message" boxes.
  • automatic templated email to pledgers after signing up.  Includes additional information specific to rangers if ranger box is checked.

Additional expectations are that Wagn will:

  • handle bulk mail effectively without exposing email addresses to recipients
  • allow (advanced) wagneers to format emails flexibly with HTML






Would be nice for it to be possible (maybe even build in by default) for people to get an email explaining the delay if "sign up" generates an account request rather than giving them an account immediately. If this isn't possible already.

I need a working vocabulary to talk about stuff, so for now:


x+*send = setting pattern card

x+email config (or whatever card referred to by setting pattern card) = email config card

+*to, +*cc, +*message, etc... = email fields (or email field cards).

within email field cards, there are 2 main types:

- email address fields (*to, *from, *cc, etc)

- email text fields (*subject, *message)

then there's *attach, which is a special case. (but no special working term needed for now)



Here are some things we need to test:


1. Does Wagn work with +*email cards? I remember this breaking before, but my automated tests suggest that my cleanup work fixed this. This should actually only work if:

-- the email address field is a collection (pointer, search) that has the *email card as an item

-- the last person to edit the email address field has administrator role (and can therefore read the *email card)


2. Can we make emails look decent if its only email address fields are *bcc and *from. If not, we need to hunt for workarounds.


3. Is it handling blank fields reasonably well?

  --Ethan McCutchen.....Wed Mar 09 11:03:18 -0800 2011

working on general ideas to upgrade email system

  --Ethan McCutchen.....Wed Mar 09 11:21:10 -0800 2011

When submitting (with in +*bcc) got an app error, Hoptoad says: 501 5.1.3 Bad recipient address syntax

  --John Abbe.....Wed Mar 09 14:32:40 -0800 2011

blank fields show up as "Add <field> ". See your Wed, 9 Mar 2011 14:13:57 -0700 (that's your time) email for an example.

  --John Abbe.....Wed Mar 09 15:15:58 -0800 2011

you can't currently use inclusions in address fields. it's not rendered.

  --Ethan McCutchen.....Sat Apr 16 18:42:47 -0700 2011

for the blank fields see add EmailHtmlRenderer

  --Ethan McCutchen.....Sat Apr 16 20:56:13 -0700 2011

so maybe this ticket is ready to close?

  --Ethan McCutchen.....Sun Apr 17 11:58:03 -0700 2011

closing. let's add new tickets if issues emerge.

  --Ethan McCutchen.....Wed May 11 11:18:00 -0700 2011