On Oct 15, 2013, at 1:33 PM, AJ Fasano ajfasano@PROTECTED wrote:

I just noticed this thread First the private mailing list functionality would be nice But I would not call is 'Private' I would call it a 'Transactional and Relationship' mailing list, making it clear that use of such a list must conform to the specific sections of the various SPAM laws regarding their use T

I like the idea of using a different name - maybe, but I'm not sure about, "Transactional and Relationship", as "Transactional" email is something else entirely: getting a subscription confirmation, or a moderation message are types of "transactional" email messages This is opposed to a mailing list message, which is the same/similar message that goes out to many That's going to be way confusing People do know the difference between, "public" and, "private", though - which is a good thing

his will help protect you from someone claiming that you created an application for SPAM Bottom line, you have done a great, albeit a tad annoying :) , job of making it so Dada religiously conforms to the laws and adding a 'Private' type list could be confusing

It's pretty scary at the pointy end - as someone who receives angry emails threatening everything under the moon for the actions of someone I can't control, it leads me to not want any of those types of messages Gotta do what I can do

I have been working on Drupal/CiviCRM integration using the existing DaDa RESTful subscription interface

How's that working out, by the way? If you have any simplified examples of clients in some other language other than Perl and JavaScript, I'd love to use them as other examples:

http://dadamailproject
com/d/COOKBOOK-subscriptions
pod
html#example_implementations

It is a slippery slope because if you do, then someone might then want Joomla, and then Drupal, etc Each CMS has rather different integration points My suggestion would be to continue the development of RESTful and other web services that allow external applications to integrate with DaDa Then you can turn around and say DaDa can be integrated with any backend system via these APIs Hell, a mobile app could then be written

Yeah, that's really my thoughts, exactly - it'd be a lot more simpler on my end: Another personal wish list on my end is to make a RESTful interface for administration-type stuff, starting with sending a message, and doing simple administration to your mailing list The major block is just with authentication: I haven't found an out-of-the-box solution in Perl for RESTful stateless authentication that I like… YET, but I'm sure something is out there This may be when moving to a framework like Mojolicious would pay off in spades

The idea of using basically Wordpress/Joomla's/Whatevers user/profile backend as Dada Mail's backend hurts my head too much Is it DOABLE? Yeah - I guess, but it means rewriting a lot of this again:

https://github
com/justingit/dada-mail/blob/master/dada/DADA/MailingList/Subscribers/baseSQL
pm

Not impossible, but not something I'm going to jump at the chance of doing! Fun(?) to do a toy version of this, though