On Sep 17, 2007, at 1:00 AM, Dada Mail ((Justin Simoni)) wrote: >> 1. It took me a few minutes to figure out that I needed to uncheck >> the >> first option on the page that disables the plugin. A mention of that >> step in the INSTALLATION section would have saved me a bit of >> searching. > > > OK, someone remind me, or put it in the features request on > sourceforge Nevermind - I got it handled ;) Thanks again for the feedback. My net connection was (and still is) v ...Continue Reading

On Sep 11, 2007, at 4:55 AM, Bruce Scherzinger wrote: > The schemas look fine, but what are you changing in terms of > content/format? I will need to know if there is breakage in the > Joomla bridge and, if so, plan a coordinated release. > Check out the schemas in the 2.10.15 release - many many of the fields were of the type, "text" - this is just basically paring them down to what exactly they need. As far as coordination, I've only made the changes in the 2.11 features stuff, whic ...Continue Reading

On Sep 11, 2007, at 8:56 AM, Mariano Absatz wrote: > Well... FWIW, I did the checks manually (diff'ing the output of > 'SELECT' vs. 'SELECT DISTINCT') and it turned out that most duplicates > had to do with addresses which had uppercase characters... it seems > older versions of dada allowed this, so that, if I got > 'El.Baby@PROTECTED' in the database and then tried to insert > 'el.baby@PROTECTED' I'd succeed ('cause now the verification process > is always done in lowercase)... For quite some ti ...Continue Reading

What's probably happening is that the clickthrough tracker embeds the full url in the URL of the clickthrough tracker - which is failing some sort of filter. I do have plans to replace that with something else: http://mojo.skazat.com/support/documentation-dada-2_10_15/ projects.pod.html#click_through_tracking_enhancements I haven't gotten to it, but help would help :) ...Continue Reading

> 1. It took me a few minutes to figure out that I needed to uncheck the > first option on the page that disables the plugin. A mention of that > step in the INSTALLATION section would have saved me a bit of > searching. OK, someone remind me, or put it in the features request on sourceforge > 2. I use an external configuration file (.dada_config) and do not > see a > way to amend the ADMIN_MENU arrayref to include the plugins. I was > able > to modify captcha settings using the LIST_SE ...Continue Reading

Hi Justin, I finally got around to testing dada_bridge.pl last night. Nice job! Along the way, a few questions came up that I didn't find answered in the documentation. 1. It took me a few minutes to figure out that I needed to uncheck the first option on the page that disables the plugin. A mention of that step in the INSTALLATION section would have saved me a bit of searching. 2. I use an external configuration file (.dada_config) and do not see a way to amend the ADMIN_MENU arrayref to include the plugins. I was ...Continue Reading

FYI-- Odd thing. I just sent a newsletter on behalf of a paying client out to my list of 22,000+. He got real panicky when he got several replies from his potential customers that said that the email about his function contained a fraud warning.  I do not know who these customers are  so I cannot learn what email software they are using, but one thing I do know is they are using 'Mail Scanner."  http://www.mailscanner.info/ They just released a new version that generates a warning when the actual ...Continue Reading

I browsed the source in order to look a bit at the queries and see what indexes could be added... I did NOT profile the code AT ALL... On 9/11/07, Dada Mail (Justin Simoni) wrote: > > I was helping a client with a slow Dada Mail and we were thinking > that the SQL table schema could do with an overhaul. Here are the > current optimized schemas - most of the changes have been to manage > the data type a bit more finely. Any one see any problems? Anyone add > any useful indexes? > > (MySQL) > ...Continue Reading

Well... FWIW, I did the checks manually (diff'ing the output of 'SELECT' vs. 'SELECT DISTINCT') and it turned out that most duplicates had to do with addresses which had uppercase characters... it seems older versions of dada allowed this, so that, if I got 'El.Baby@PROTECTED' in the database and then tried to insert 'el.baby@PROTECTED' I'd succeed ('cause now the verification process is always done in lowercase)... I simply did the following: UPDATE dada_subscribers SET email=lower(email) WHERE BINARY emai ...Continue Reading

On 9/11/07, Henry Hughes wrote: > > Mariano, > > The table that holds the email address can contain more than one list, > that the same email address may be subscribed to: I know that (in fact, I *do* have a couple of lists that have subscribers in common). > > > CREATE TABLE dada_subscribers ( > email_id int4 not null primary key auto_increment, > email text(320), > list varchar(16), > list_type varchar(64), > list_status char(1) > ); > > Therefo ...Continue Reading