Barry said:
We should certainly do everything we can to make sure that Richard's
ht:dig solution is nearly trivial to integrate, but I'm not sure we
should distribute it with Mailman.
Sorry, I guess I wasn't clear -- I just meant for him to look at both
Python and non-Python solutions, before
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 6, 2006, at 1:56 PM, Brad Knowles wrote:
Barry said:
We should certainly do everything we can to make sure that Richard's
ht:dig solution is nearly trivial to integrate, but I'm not sure we
should distribute it with Mailman.
Sorry, I
* Need to convert rfc8222 to xml/html
I haven't found anything substantial via searching. My next step is to
go spelunking in MailManager code and other python-webmail packages. If
anyone knows good trees in this forest, please clue me in.
Do you mean 2822? or 822? 8222 doesn't exist. Any
If mailman would be able to write an xml representation of
each message to a separate file, that would be wonderful.
Then one would be able to use xlst stylesheets to make
custom archives. I hacked something like this together for
an on-line class. The workflow was:
(1) mailman writes each
On Tue, 2006-07-04 at 15:44 -0400, emf wrote:
In order to provide interfaces to archives, I believe I must perform
some intermediary manipulation; my goal is to get the information
contained within the .mbox files mailman generates into ElementTrees and
other objects so as to represent them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 4, 2006, at 3:44 PM, emf wrote:
Here's where I'm at, grouped functionally:
* Need to convert rfc8222 to xml/html
I haven't found anything substantial via searching. My next step is to
go spelunking in MailManager code and other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 4, 2006, at 5:33 PM, Brad Knowles wrote:
Don't ignore non-Python solutions.
My main problem with non-Python solutions /as a default for Mailman/
is that it complicates distribution and packaging. It means that
we'll have additional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 5, 2006, at 10:01 AM, Hans G. Ehrbar wrote:
If mailman would be able to write an xml representation of
each message to a separate file, that would be wonderful.
Then one would be able to use xlst stylesheets to make
custom archives.
It's
On 7/5/06 4:30 PM, Barry Warsaw [EMAIL PROTECTED] wrote:
I'm thinking something along the lines of sha1 hashing Message-ID and
perhaps Date. RFC 2822 $3.6 says that the only required headers are
the origination date (Date:) and originator address fields (From: and
possibly Sender: and
Dearest mail manipulating macaques and perambulating python
prestidigitators,
I have been blessed by the grace of Google and so am working full-time
on improving Mailman's web UI:
http://wiki.list.org/display/DEV/Summer+of+Code
In order to provide interfaces to archives, I believe I must
Ethan said:
In the interest of not reinventing the wheel, I'm looking for existing
python (or other!) code that does the things I need. I'm also putting
out a call for anybody who likes this sort of thing to help me out (see
below).
Don't ignore non-Python solutions. In particular, you
Brad Knowles wrote:
Ethan said:
I plan on using [2] to generate mbox thread indexes for rapid navigation
of lists. Any suggestions for more robust variants would be welcome;
feedback on how to handle threading for message-id-less messages would
also be welcome.
All messages should have
12 matches
Mail list logo
