Re: New pending queue GUI

On Wed, Nov 08, 2006 at 08:50:36AM -0700, Jason R. Mastaler wrote:

> I think I know what the problem is - I had to glance at the source. My
> pending queue is a Maildir, and it looks like you are manipulating the

Um, okay...why? I thought the pending queue was just a directory with
files in it. AFAICT, it shouldn't make any difference if your pending
cache is nested a gazillion directories deep inside
Maildir/foo/curr/*msg or whatever; all it wants to do is read the
directory and its files wherever they are, and doesn't even care about
file extensions except to strip them off.

You can set the PendingCache variable to *any* directory; it just
happens to default to ~/.tmda/pending since that's what the TMDA
installation docs recommend.

Right now, the best way to fix it is to remove any existing ~/.qbrowserc
file, and set the correct path in the user-definable defaults at the top
of the script. If that still doesn't work, give me an example of what
your maildir holds, and I'll try code around it.

> TMDA.Queue libs, or the tmda-pending command to generate indexes and

tmda-pending won't output full headers (in particular, the subject line
in "tmda-pending -bT" is truncated) and has no way to non-interactively
dump the entire message. So, while the script uses tmda-pending for
batch commands (whitelist, blacklist, and release), it wants to read the
messages directly to do its own parsing and raw-message display.

My Python-fu is rather limited, and I'm not too excited about rewriting
the whole thing in wxPython right now, although that might be a fun
project for the future. Meanwhile, if you can think of a more portable
way to read in the needed data, I'm open to it.

-- 
Unabashedly littering the information superhighway with detritus like
this for over 15 years now.