When I use the "check all" link at the archive menu, and push the Delete button, nothing happens! It even looks like the form is not submitted at all. There are about 100 archived messages. Maybe there is a restriction on the amount of form fields in Internet Explorer 6.0 (Win98) which can be send in one form? I just tried to check the messages manually, so not using the uncheck link. But the same result: nothing happens when pushing the Delete button. ...Continue Reading

> Bug #1: In 2.9.2, tables and textareas extended beyond the screen > edge in Internet Explorer for Windows Oh good, you figured this out - I just had a client tell me about this - I don't have Win/IE, so I had no idea what was going on in their screenshots. > Bug #2: The "logo" in the header (".:Dada Mail" by default) > couldn't be styled independently in 2.9.2 Here's another issue that may be partly related: Right now, the title (for example) says: .: Dada Mail ...Continue Reading

> > To my surprise, it is calling _lock_db at the end. But I would > > expect it > > calls _unlock_db. What do you think? > > Whoa. Yes. It definitely should say, "_unlock_db" and not, "_lock_db" > > Does making that tweak change you situation? Yes it does! the lock file is removed properly now, and the messages are deleted from the POP3 box also! So it looks like both bugs are solved. Unfortunately, I do not have a satisfactory explanation why the messaged are remove ...Continue Reading

> As we've since discussed on this list, I'll make sure to > communicate better > about where I'm at, so Justin has the info he needs to coordinate > things. In > the meantime: ...seriously, J, you can stop trying to butter me up > now! > Alright? Not only is it /particularly/ embarrassing under the > circumstances > described above...but it's also quite undeserved. Alright. Umm... get.. back to work! Get... me some coffee! Hmm... that doesn't work - I need an intern 'round here. ...Continue Reading

[Note: Even if you have no desire to read through this, please check out "Bug #4" at the bottom: it's currently unfixed, and I'd like your opinion on which way we should do so!] CSS-Friendly Templates in Dada Mail 2.10 Part 2: Things Fixed Along the Way   Part 1 explained the general reasons why default_list_template.tmpl, default_admin_template.tmpl, and default_css.css look so different between 2.9.2 and 2.10, even though they still work much the same. (Yes, there are good reasons; a quick-and ...Continue Reading

Justin wrote: > Not getting paid and working on > this should at the very least be fun and educational. And it has been, without qualification. It's been a *great* experience throughout, I have no complaints whatsoever, and I'd recommend Justin's even-handed approach to things here to *anyone* who's even the least bit interested in becoming further involved. ...My own approach, however, could still use some work.With the clarity of hindsight, the bump in the road earlier in the past week was me seeing the roll ...Continue Reading

> To my surprise, it is calling _lock_db at the end. But I would > expect it > calls _unlock_db. What do you think? Whoa. Yes. It definitely should say, "_unlock_db" and not, "_lock_db" Does making that tweak change you situation? Justin Simoni ...Continue Reading

Justin, When destructor DESTROY is called when removing $la, method _close_db() is called. When I look at this function inside GenericDBFile.pm, this function is listed as follows: sub _close_db { my $self = shift; untie %{$self->{DB_HASH}} or warn "untie didn't work: $!"; delete $self->{DB_HASH}; $self->_lock_db; } To my surprise, it is calling _lock_db at the end. But I would expect it calls _unlock_db. What do you think? Frans ...Continue Reading

> One thing that may help is to explicitly destroy the list settings > and list archive objects in the archive() subroutine of > dada_bridge.pl - ala place: > > undef $ls; > undef $la; > > At the end of the archive() subroutine. > > destroying these objects should unlock the lock file for you; so the > next time you archive a message, a new object has to be created. They > *should* be removed automatically, because they're out of scope after > the subroutine is done - b ...Continue Reading

> The strange thing is that the problem only shows up when 2 or more > messages > are in the POP3 box. And only the first 2 messages are sent and > archived, > the rest is ignored. One thing that may help is to explicitly destroy the list settings and list archive objects in the archive() subroutine of dada_bridge.pl - ala place: undef $ls; undef $la; At the end of the archive() subroutine. destroying these objects should unlock the lock file for you; so the next time you archive a messa ...Continue Reading