August 17th 2005 PDT
> I'm sure whoever did will contact you personally, and if not, a > query to > secunia.com should do the job. I doubt it. Usually, if they do, they tell me they've found a security problem - but never give me an example on how this problem could affect the program in the real world (something, anything). This chap didn't even give me that. The worst is when the person gives you an ultimatum - "You have x days to fix this problem or else..." Yeah, thanks. This is even worse. The problem ...Continue Reading
August 17th 2005 PDT
> Hey did anyone report this? Is it possible that "reported by vendor" refers to this?: http://mojo.skazat.com/download/testing_2_10_0_alpha1.html That would be consistent with their recognition/acknowledgement of 2.10 alpha 1's fix. And I'm betting that a daily Google alert for "security bug" or somesuch would be all the company would need to be notified of that page's existence. ...Continue Reading
August 17th 2005 PDT
> Hey did anyone report this? Not I -- my only communication on security stuff has been directly with you, by personal email. I trust this is the usual practice for such things. I'm sure whoever did will contact you personally, and if not, a query to secunia.com should do the job. ...Continue Reading
August 17th 2005 PDT
> Hey did anyone report this? Not me... Alfred ...Continue Reading
August 17th 2005 PDT
Hey did anyone report this? http://secunia.com/advisories/16435/ Cause I didn't - although it says, Provided and/or discovered by: Reported by vendor. Usually, when a so called, "vulnerability" is discovered, I get like, a "heads up" so I can confirm or clarify what's going down. The way this vulnerability is worded wrong. That's all. Anyone? Justin Simoni ...Continue Reading
August 17th 2005 PDT
On Wed, Aug 17, 2005 at 09:35:16PM -0000, Dada Mail (Justin Simoni) wrote: > > The other option is to Wiki the documentation - which wouldn't be the > worst idea - I'm just not really interested in admin'ing it against > bad advice/spam. If we can hook up the Wiki to the Help links, we'd > be in a pretty good spot, as Dada Mail users could help themselves to > documentation. I think a wiki is the best idea. I've seen it work really well for http://wiki.darcs.net/ and http://www.cgi-app.org/ ...Continue Reading
August 17th 2005 PDT
> Seing all these links would make me want to copy all your existing > help > files to a 2.10 subdirectory and change all your links in the new > release to > reflect the new version. Basically what's going to happen. At the moment, the only person who has access to change these help files is me. That's not the best way to go about these things, since it doesn't look like I'm writing new ones for screens/stuff that change, etc. What we should do is put this documentation in CVS in some sort ...Continue Reading
August 17th 2005 PDT
> > HTML's element doesn't use a width attribute > > [width] works in Moz... > But is this non-standard? Officially, yes: http://www.w3.org/TR/REC-html40/interact/forms.html#h-17.6 But we could always ignore that & just browser-test the heck out of it.... ...Continue Reading
August 17th 2005 PDT
> HTML's element doesn't use a width attribute This works in Moz at least: Hello. But is this non-standard? Justin Simoni -- :: is an eccentric artist, living and working in Denver, Colorado :: URL: http://justinsimoni.com :: PHO: 720.436.7701 :: Mailing List - http://justinsimoni.com/mailing_list.html On Aug 17, 2005, at 2:45 PM, Shane Clintberg wrote: > Alfred wrote: > > > instead of: > > > > I prefer: > > > > > Yup, that was the first thing I thought of too! The pr ...Continue Reading
August 17th 2005 PDT
I've now fixed the IE6 menu width bug that was in Dada Mail 2.9.x. The fix is available for 2.10 alpha testers here (rev 1.37), and will appear publicly in Dada Mail 2.10 stable. Anyone wishing to implement this fix retroactively in a working installation of Dada Mail 2.9, 2.9.1 or 2.9.2 should not use the above-linked CVS file, but should do the following instead: 1. Open your version 2.9.x copy of default_css.css , located in the dada/DADA/Template/templates directory. 2a. Find the follow ...Continue Reading
Start a new thread, email: dadadev@dadamailproject.com
This is the developer discussion mailing list for Dada Mail.
If you are just looking for support Dada Mail, consult the message boards at:
https://forum.dadamailproject.com
Documentation for Dada Mail:
Specifically, see the Error FAQ:
https://dadamailproject.com/d/FAQ-errors.pod.html
To post to this list, send a message to:
mailto:dadadev@dadamailproject.com
All subscribers of this list may post to the list itself.
Topics that are welcome:
Dada Mail is on Github:
https://github.com/justingit/dada-mail/
If you would like to fork, branch, send over PRs, open up issues, etc.
This Privacy Policy is for this mailing list, and this mailing list only.
Email addresses collection through this mailing list are used explicitly to work within this email discussion list.
We only collect email addresses through our Closed-Loop Opt-In system.
We don't use your email address for any other purpose.
We won't be sharing your email address with any other entity.
Unsubscription can be done at any time. Please contact us at: justin@dadamailproject.com for any help regarding your subscription, including removal from the mailing list.
All mailing list messages sent from us will include a subscription removal link, which will allow you to remove yourself from this mailing list automatically, and permanently.
All consent to use your email address for any other purpose stated at the time of the mailing list subscription will also be revoked upon mailing list removal.