Re: New Feature Ideas for the Future: Private Mailing Lists

 
From: "AJ Fasano" <ajfasano@PROTECTED>
Date: October 15th 2013

Mary Anne,

 

My bad. Less than a second after I hit ‘Send’ it dawned on me you might be using DaDa profiles and the account sync back to wordpress would be annoying. Putting the protected directory into the wordpress folder is a hell of a lot easier than hacking one of the Basic Auth plugins or messing with mod_auth_sql ugliness.

 

One other question, did you try putting all the private file folders under a common directory and sym-linking it into the wordpress directory.  Then there may not have been a need to hack the DaDa core and install another wordpress, assuming apache allows FollowSymLinks and/or SymLinksIfOwnerMatch to be overridden.

 

Justin,

 

Mary Ann does bring up an interesting, possible future, feature.  Some kind of authentication plugin system, auth sql query, or something like an open-source application called GLPI has.  In fact, didn’t I see something in the Pro Manual about LDAP? GLPI is an opensource inventory app written in PHP.  One of the authentication options it offers is a request header.  Quite a few SSO applications do that kind of thing including opensource ones like CAS and Shibboleth and commercial ones like WebSeal. And most use the same USERNAME<?> header that apache’s basic auth does. As long as the username in DaDa is the same as the username the authenticator sets in the header, DaDa would allow them in as that user.  Thus making DaDa SSO somewhat compatible. For example, I was able to use that header to integrate GLPI with Google Apps and a google auth apache module.  Of course there are also more complex mechanisms like SAML and oAuth, to name a couple.

 

Just some thoughts..

 

 

 

 

 

 

 

 

From: Mary Ann Kelley [mailto:maryann@PROTECTED]
Sent: Tuesday, October 15, 2013 3:41 PM
To: Dada Mail Developers
Subject: [dadadev] Re: New Feature Ideas for the Future: Private Mailing Lists

 

Hi AJ,

 

I needed the private area to line up with the list subscribers, so if I used WP to manage the content with its authentication, the team members would have had to create yet another profile and login to let the CMS manage the list. They already need the Dada profile to read the message archives, so it was a perfect fit except for WP not liking password protected directories.

Warm regards,

Mary Ann

 

 

On Oct 15, 2013, at 3:33 PM, AJ Fasano wrote:




Is there a reason you continued to use DaDa Mail's private file functionality as opposed to a Wordpress file manager and let the CMS manage content and handle authentication/authorization to that content?

 

Post: mailto:dadadev@PROTECTED

Unsubscribe »

Post: mailto:dadadev@PROTECTED

Unsubscribe »

  • This mailing list is a public mailing list - anyone may join or leave, at any time.
  • This mailing list is a group discussion list (unmoderated)
  • Start a new thread, email: dadadev@dadamailproject.com

This is the developer discussion mailing list for Dada Mail.

If you are just looking for support Dada Mail, consult the message boards at:

https://forum.dadamailproject.com

Documentation for Dada Mail:

https://dadamailproject.com/d

Specifically, see the Error FAQ:

https://dadamailproject.com/d/FAQ-errors.pod.html

To post to this list, send a message to:

mailto:dadadev@dadamailproject.com

All subscribers of this list may post to the list itself.

Topics that are welcome:

  • Constructive critiques on the program (I like, "x", but, "y" needs some work - here's an idea on how to make this better...)
  • Bug/Error reports
  • Bug fixes
  • Request For Comments on any changes to the program
  • Help customizing Dada Mail for your own needs
  • Patches
  • Language Translations
  • Support Documentation/Doc editing, FAQ's, etc.
  • Discussion of any changes that you would like to be committed to the next version of Dada Mail -

Dada Mail is on Github:

https://github.com/justingit/dada-mail/

If you would like to fork, branch, send over PRs, open up issues, etc.

Privacy Policy:

This Privacy Policy is for this mailing list, and this mailing list only.

Email addresses collection through this mailing list are used explicitly to work within this email discussion list.

We only collect email addresses through our Closed-Loop Opt-In system.

We don't use your email address for any other purpose.

We won't be sharing your email address with any other entity.

Unsubscription can be done at any time. Please contact us at: justin@dadamailproject.com for any help regarding your subscription, including removal from the mailing list.

All mailing list messages sent from us will include a subscription removal link, which will allow you to remove yourself from this mailing list automatically, and permanently.

All consent to use your email address for any other purpose stated at the time of the mailing list subscription will also be revoked upon mailing list removal.