>If I'm understanding this correctly, it would still only protect the uploaded files in wp-content, not actual WP pages. It sounds like it would work for that, but not for also password >protecting the pages that need it (mostly because of the way WP uses rewrites to create pages and posts). Yes, it would only protect the protected files. And using apache aliases, you would not even need to put them under the wordpress install. But, I am curious. You have the DaDa mail .htaccess files protecting wordpress page ...Continue Reading

> 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" > ...Continue Reading

…speaking of APIs, I updated thoroughly the docs on using Amazon SES with Dada Mail. Amazon AWS is in a way very simple, and in other way, very complex, especially when you are working with one little tiny part of their ecosystem: http://dadamailproject.com/d/features-amazon_ses_support.pod.html Users of SES should def. check out their easy DKIM, which allows for DKIM signing on SES's side, relieving you to do it on your side. Pretty neat! http://docs.aws.amazon.com/ses/latest/DeveloperGuide/easy-dkim.html ...Continue Reading

On Oct 15, 2013, at 1:33 PM, AJ Fasano 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 ...Continue Reading

If I'm understanding this correctly, it would still only protect the uploaded files in wp-content, not actual WP pages. It sounds like it would work for that, but not for also password protecting the pages that need it (mostly because of the way WP uses rewrites to create pages and posts). Untitled Document Warm regards, Mary Ann On Oct 16, 2013, at 1:35 PM, AJ Fasano wrote:A symlink in “<shared home dir>/public_html/wp/wp-content/protected_files”   that points to “<shared home dir>/public_html ...Continue Reading

Well, a symlink is basically the unix version of a windows shortcut.  It sounded like you may have been able to keep with a single WP install by linking the protected directory into your original WP install.  Now I don’t have a whole lot of experience with WP so I am not 100% sure where the folder would go. In drupal it would be something like sites/default/files so I am going to guess with WP. For example:DaDa protect:  <shared home dir>/public_html/protected_files  WP install: <shared ...Continue Reading

Um, no. I have no idea what a SymLink is. I'm really just lurking on this list with the occasional comment/question as I am not a developer in any sense of the word. I know just enough hacks to get myself into trouble, to be honest. There is only one private folder (it does have subfolders for downloads) and I just put the second WP install in that directory. The entire install directory is protected and is fed via iframe (I tried to find a more elegant solution but nothing worked and I had to limit the ...Continue Reading

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 ...Continue Reading

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. Untitled Document Warm regards, Mary Ann On Oct 15, 2013, at 3:33 PM, AJ Fasano wrote:Is there a reason you continued to use DaDa Mai ...Continue Reading

> An integration with Wordpress would be phenomenal. >>Someone pony up the funds to comission this! This is a Very Difficult Feature that would take Quite a Bit of Time, I can't commit to doing the dev. on the promise of future Pro Dada sales, 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 section ...Continue Reading