Edward Ned Harvey wrote:
Presently, I'm using pipermail. I'm open to suggestions.
This question is pretty complicated, so probably the best answer I
could
possibly get is to know how pipermail gets called, so I can go try
and read
its source and stuff. So I can dig into it myself. At present, I
have no
idea what process generates the html from the mbox.
The archiver consists of the modules in Mailman/Archiver/
The start of the process is the ArchiveMail() method of the Archiver
class defined in Mailman/Archiver/Archiver.py.
Thank you.
In the pipermail archives, he sees this link at the top of the
message:
Joe User joe.user at domain.com
He's going to think, "if I click that link, it's a new message to
Joe User."
This depends on the setting of ARCHIVER_OBSCURES_EMAILADDRS. If
ARCHIVER_OBSCURES_EMAILADDRS is Yes, behavior is as below, but if it
is No, the poster's address isn't munged and the link is to the
poster.
Oh - I misunderstood the meaning of that. Here's what I thought:
I thought if OBSCURES is No, the archiver shows <a href='mailto:[EMAIL PROTECTED]'
>[EMAIL PROTECTED]</a>
I thought if OBSCURES is Yes, the archiver shows <a href='mailto:[EMAIL PROTECTED]'
>joe -at- domain</a>
I think this is cool the way it is, and it was just my misunderstanding.
If he looks closely, he notices the URL of that link is:
mailto:[EMAIL PROTECTED] Interesting
Idea&In-Reply-To=
He's going to think, "if I click that, it's a new message to the
list,
joining this conversation."
Neither of his thoughts are right.
I'm thinking the text of a mailto should always match the url
address.
Otherwise it's misleading, because most people will only see the
blue text.
If you see the link joe.user at domain.com then you think it
generates mail
to joe.user, not to some other address.
Good point.
If I'm making a suggestion for future release... I suggest this:
<strong>Joe User</strong> <a href='mailto:[EMAIL PROTECTED]'>Reply to Joe</
a><br />
<a href='mailto:[EMAIL PROTECTED]&Subject=blahblah'>Reply to list</a>
I'm also thinking it should include the RE: and mimmick the
behavior of an
actual mail client.
?Subject=Re:[Somelist]An Interesting Idea
I'm also thinking there should be a Message-ID in the "In-Reply-To"
These were bugs fixed in Mailman 2.1.10. Prior to that, the Re: was
not
inserted and the In-Reply-To was taken from the In-Reply-To of this
message instead of the Message-ID of this message.
Of course, it's still up to the MUA to honor those fragments in the
mailto URL.
Sure enough, I'm on 2.1.9 (shipped with Centos 5.1). I'll go make an
effort to upgrade.
Is it possible my pipermail is simply misocnfigured somehow? I'd
like to
see this link, or another link, give users the ability to join a
conversation, just by clicking something in the web archive.
Much of what you see is governed by the article.html template. See the
FAQ at <http://wiki.list.org/x/jYA9> for more info on templates.
<snip>
</A><BR>
In other words, I should be able to customize it. :-) Awesome,
thanks. Wish me luck.
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
