Greetings all! Over the last few months, I have been getting more and more frustrated. I am at the end of my ability to solve problems and find a need to bring in some bigger guns, which is the purpose of this message. I have a client that is using Dada Mail 3.0.2 for their church website. There are two lists. One is a prayer list, which is set as a discussion list and the other is an announcement list, which is set to allow emails only from selected people (authorized senders). For the most part, everyth ...Continue Reading

You must have subscribed to the dadaMail developers mailing list? on 6/2/2009 08:54, Dan wrote: > > Why did I get this e-mail? > On 1-Jun-09, at 5:06 PM, WhatsNet wrote: ...Continue Reading

Why did I get this e-mail? On 1-Jun-09, at 5:06 PM, WhatsNet wrote: > > My host has Dada Mail installed but the Clickthrough_tracking.cgi > does not appear to be setup properly. > There is nothing showing up in the admin menu nor does the tracking > work. > I was hoping possibly someone could take a look or advise. > Great program though-Has much of what Lyris List Manager has. > regards > Richard Baron > -- > > > > -- > > Post: > > Unsubscribe: > > & ...Continue Reading

My host has Dada Mail installed but the Clickthrough_tracking.cgi does not appear to be setup properly. There is nothing showing up in the admin menu nor does the tracking work. I was hoping possibly someone could take a look or advise. Great program though-Has much of what Lyris List Manager has. regards Richard Baron ...Continue Reading

OK, I fixed it and it seems to be working - now I have a database permissions issue but that is a hosting issue.See below...On Wed, May 27, 2009 at 4:50 AM, Justin J <justin@PROTECTED> wrote: In the newest versions of Dada Mail, all these variables should be simply, "SQL", for any of the SQL flavors: MySQL, PostgreSQL, SQLiteSetting it to MySQL still works also - left over from the old version I guess.  The key/value you want to pay attention to is, "dbtype":         ...Continue Reading

Here's the correct capitalization: > In my config file, I have the following: > $SUBSCRIBER_DB_TYPE = 'MySQL'; $ARCHIVE_DB_TYPE = > 'MySQL'; $SETTINGS_DB_TYPE = 'MySQL'; > $SESSION_DB_TYPE = 'MySQL'; > In the newest versions of Dada Mail, all these variables should be simply, "SQL", for any of the SQL flavors: MySQL, PostgreSQL, SQLite I don't know when this changeover happened, where stating only "SQL" happened, but it's been at least a ...Continue Reading

I figured it out ... I think.The lines below need to have a type that matches in DADA::MailingList::STORED_ITEM::DBTYPE which is proper capitalization. $SUBSCRIBER_DB_TYPE        = 'MySQL'; $ARCHIVE_DB_TYPE           = 'MySQL'; $SETTINGS_DB_TYPE          = 'MySQL'; $SESSION_DB_TYPE           = 'MySQL'; $BOUNCE_SCORECARD_DB_TYPE  = 'MySQL'; (Yes, I know this one was not in my prevoius messages)However, the entry ...Continue Reading

Also, I went back through the installation instructions to make sure that I didn't miss anything (in case things have changed in 3.0.3) and I found an issue:On http://dadamailproject.com/installation/configuration-sql_backend.html, it says that: $SUBSCRIBER_DB_TYPE        = 'MySQL'; $ARCHIVE_DB_TYPE           = 'MySQL'; $SETTINGS_DB_TYPE          = 'MySQL'; $SESSION_DB_TYPE           = 'MySQL';should all be "= 'S ...Continue Reading

I have been using dada for several years on one server.  I am now migrating it to a different host and I had issues connecting to the MySQL Server.I received the following error: install_driver(MySQL) failed: Can't locate DBD/MySQL.pm in @INC (@INC contains: ../../ ../../perllib /sw/lib/perl5/5.8.6/darwin-thread-multi-2level /sw/lib/perl5 ../../DADA/perllib ./ ../ ../../../ ./../../DADA ../../DADA ../DADA ../DADA/perllib ./DADA ./DADA/perllib ../../../perl ../../../perllib /usr/local/lib/perl5/5.8.9/BSDPAN /usr/lo ...Continue Reading

On May 19, 2009, at 6:51 PM, Dave Leffler wrote: > I'm running into a problem with partial sending. I have NO profiles > set up, > but would expect partial sending to work similar to v3.03. I've > looked > through the code and the problem seems to be that the SQL statement in > MailingList::Subscribers:baseSQL.pm now uses profile.email vs > subscriber.email. Sounds like you're working with 3.1 - it's pretty alpha quality code. I'd assume you'd hit a snag or two - it may be what you're deta ...Continue Reading