Justin wrote: > here's a problem I have when I try to apply an > already designed site's HTML/CSS to Dada Mail's CSS: > One of the things that Dada Mail > defines in its stylesheet is the body of the page itself... > This has a tendency to break the design of some HTML pages, which > haven't defined anything for the body of the html message. I believe I've now solved this problem and would *really* appreciate my solution being tested widely. However, I was expecting a second alpha release rather than ...Continue Reading

Congrats for you too, Simon! However, there is a typo inside dada_bridge plugin which lead to mal-function of the script: From the log file: Can't use bareword ("li") as a HASH ref while "strict refs" in use at dada_bridge.pl line 855. line 855: if($li->{group_list} == 1 && li->{mail_discussion_message_to_poster} != 1){ You forgot the '$' before 'li'. Frans ----- Origineel bericht ----- Van: "Dada Mail (Justin Simoni)" Datum: donderdag, augustus 25, 2005 11:30 Onderwerp: ...Continue Reading

Here are the docs: http://mojo.skazat.com/download/testing_2_10_0_beta1.html Congrats everyone! -- Justin Simoni .: Dada Mail "Write Once - Distribute Everywhere" Email Communication Software url: http://dadamail.org ph: 720.436.7701 aolim: leaddadaist ...Continue Reading

> > While I think could be a good idea, I respectfully submit that it > > should not be a priority /right now./ > > Then it has to be written down somewhere. If it's not, it'll be lost. ...Roadmap? :-) > Like I said, the JS functions, /as it stands now/ could be much > better engineered to not be a requirement, but an optional feature > that anyone that has JS turned on could use - which hopefully is a > large majority of the users of the program. And I agree with that in the long term, ...Continue Reading

>>> I'm reminded that for list discussions, it's nice to have the >>> option >>> (either globally or per-user) to not get messages to the list that >>> you >>> sent yourself. > If "globally" means "not optionally" then I'm agin it. Har har. :) This feature is now an option in dada_bridge.pl and can be turned on and off per list. Justin Simoni ...Continue Reading

I just realized that if you use the dada_bridge.pl plugin and: * check: Make this list a discussion list ( Messages from addresses that are allowed to post to this list should: ) * uncheck: be sent to the Subscription List. * and check: have a copy of the original message forwarded to: * and plug in an address (that's secret to you), any messages that go to the list email will be scanned to see if it's a subscriber and will only be forwarded to you if it is. This way, the subscription list acts like a whit ...Continue Reading

OK, should be fixed now - look for ver 1.38 of dada_bridge.pl in CVS. I've attached a diff file for geek points. Justin Simoni ...Continue Reading

That was a tricky one indeed! You probably have too change the line: if($li->{group_list} == 1){ into: if($li->{group_list} == 1 && $errors->{msg_not_from_list_owner} ){ which means there is no need to verify whether the from address is on the list or not. Will be more efficient too. Have a nice lunch, I go for a sleep now! > > Hmm, > > It's still working for me, I'm suspecting that this line (703 or so): > > [snip] > > foreach(keys %$errors){ > $status = 0 i ...Continue Reading

> So, back to the list switch widget - can some one whip up some code > that will allow the onSubmit select box to work if JS is enabled, but > show a submit button if no JS is available? And be standards > compliant? If someone can, I can work with that and place it into > Dada Mail, where ever it needs to go; If we're targeting the submit > button to be used on constrictive environments like text-based > browsers, or perhaps a handheld PDA, I don't think pixel perfect > layout is absolutely ne ...Continue Reading

Hmm, It's still working for me, I'm suspecting that this line (703 or so): [snip] foreach(keys %$errors){ $status = 0 if $errors->{$_} == 1; last; } [/snip] is incorrect. Since hashes are fetched semi-randomly, whichever key you get first, will tell the fate of what status is set to and for whichever reason, it's a different order than me. It should probably read: [snip] foreach(keys %$errors){ if($errors->{$_} == 1){ $status = 0 ; last; } } [/snip] ...Continue Reading