August 28th 2005 PST
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
August 28th 2005 PST
> 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
August 28th 2005 PST
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
August 28th 2005 PST
> 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
August 27th 2005 PST
> 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
August 27th 2005 PST
Frans, That's some major investigating work, I'll look and see what the problem may be; Thanks for the tip; Justin Simoni ...Continue Reading
August 27th 2005 PST
There is a very annoying problem "Messages not removed from POP3 server" when using dada_bridge. I have noticed this problem once before, but could not reproduce it at that time. But last Friday, it showed up again and this time I could reproduce the problem for 100%. So this was my chance to find out what is really going on. 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. I spend many ...Continue Reading
August 27th 2005 PST
Hello Shane, > Obviously, that was the *long* version my templating work. Here's an > abbreviated summary, adaptable for a changelog or release > announcement: That's perfect for me. And I read your last message - very interesting and I really do appreciate all the hard work you've put into this - I'm sure you had fun as well :) I hope my starter HTML code wasn't to kludgy for you - if it is, attempt to try this with 2.8.15 :) One thing I encourage you to do is: > Perhaps Dada Mail 2.11 or 2.12 ...Continue Reading
August 26th 2005 PST
Justin, Obviously, that was the *long* version my templating work. Here's an abbreviated summary, adaptable for a changelog or release announcement: - default CSS file has been simplified and reorganized into meaningful categories, making things easier to find and change - improved XHTML compliance - improved structural markup (many things out of table-based layouts for greater CSS-based design control) - added structural groupings to the templates, following in the footsteps of the CSS Zen Garden , for greatly en ...Continue Reading
August 26th 2005 PST
CSS-Friendly Templates in Dada Mail 2.10 Part 1: The Big Picture Introduction When I first introduced some of the broader (and not just bugfix-specific) benefits of the templating overhaul work I've been doing to Dada Mail in recent weeks, Justin's response, in part, was: > I'd like to encourage you to keep going forth on this type of experimentation. And given the incomplete way I had presented things at that point, this was a *perfectly* reasonable statement for him to make. Bu ...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.