On Jul 27, 2006, at 5:25 PM, Bruce Kallick wrote: > > The two alternatives seem to me to be logically equivalent -- what > am I > missing? One happens when you create a new list, one happens while you're at the list you want to copy from. They equivalent, just where should the functionality lay? If there's a better idea than either of my ideas, please anyone, feel free to chime in, I just want to make this easy to use, if it does become a feature. > >> whether what you just filled out ...Continue Reading

The two alternatives seem to me to be logically equivalent -- what am I missing? >whether what you just filled out on the, "Create a New List" form >would be override by the information you just filled out. Huh? I can't seem to parse that. ...Continue Reading

Hello everyone, First off, thanks for all the input on the Config.pm pod stuff - I'm still not sure what I'm going to do in future realease, but I may create a test version of the Config.pm w/o pod and see what people think - the current opinion wasn't unanimous either way, so I'm going to be siding conservatively on this issue, at this time. Another issue: Many, many people are interested in using one list's settings as a default for a new list - if you're interested in this feature, do you think: * th ...Continue Reading

That sounds good, and would surely make it easier to read. On 24 Jul 2006 07:21:06 -0000, Dada Mail (Justin Simoni)* < dada@PROTECTED> wrote:On Jul 23, 2006, at 9:55 AM, Joe Rizza wrote: --Post:    <mailto:dadadev@PROTECTED>Unsubscribe:     <http://mojo.skazat.com/cgi-bin/dada/mail.cgi/u/dadadev/ >List Information:     <http://mojo.skazat.com/cgi-bin/dada/mail.cgi/list/dadadev>Archive:         < ...Continue Reading

On 24 Jul 2006 07:17:13 -0000 "Dada Mail \(Justin Simoni\)" wrote: > On Jul 23, 2006, at 12:45 AM, Andreas Grau wrote: > > I vote for leaving it *in* the file. It is part of the documentation, > > OK - one vote for leaving it in :) :) > > > Personlly, I can't see why it should be difficult to wait with > > changing until one sees a =cut. People obviously read the file and then > > *spontaneously* decide to change the file. > > Well, the problem is, if you don' ...Continue Reading

On Jul 23, 2006, at 8:30 PM, wrote: ...Continue Reading

On Jul 23, 2006, at 9:55 AM, Joe Rizza wrote: ...Continue Reading

On Jul 23, 2006, at 12:45 AM, Andreas Grau wrote: > > I vote for leaving it *in* the file. It is part of the documentation, > pod's are invented and used for reason, and people wanting to dig > deeper into things need it. OK - one vote for leaving it in :) > Personlly, I can't see why it should be difficult to wait with > changing > until one sees a =cut. People obviously read the file and then > *spontaneously* decide to change the file. Difficult ? Yes ! Difficult > people ! ;-) Well, ...Continue Reading

Hello Everyone, 2.10.10 alpha 1 has been released. Here are the direct links to download: *tar.gz: http://prdownloads.sourceforge.net/mojomail/dada-2_10_10_alpha_1.tar.gz?download * zip: http://prdownloads.sourceforge.net/mojomail/dada-2_10_10_alpha_1.zip?download This release *only* contains bug fixes (described below) and contains no new features - making this a pretty solid, but fairly untested-in- the-wild release. I'm releasing it as an alpha not because I don't think it's a stable release, just that ...Continue Reading

Here is a Logical idea which may make everyone happy   My main concern is that the Bigger the page, the more cpu time is used even if most of the page is commented, the cpu still needs to read line by line to verify this.   Please read ALL of this before commenting.   What not have a seperate Online HTLM File (or even off-line HTML file)   eg (V = version | X = version number) www.xyz.com/kb/DadaVX.htm   Sort of like this www.xyz.com/kb/DadaV2-10-9.htm etc etc   Then, IN THE act ...Continue Reading