Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Date: Thu, 1 Feb 2007 15:48:03 +0100
From: Nahuel ANGELINETTI <nahuel@altnetvision.info>
To: dev@httpd.apache.org
Subject: Re: Patch for mod_mbox
Message-ID: <20070201154803.6b5a7d3f@localhost.localdomain>
In-Reply-To: <8953E334-9BA8-463F-A5F0-E3D562F499D0@bulix.org>
References: <20070201133602.749c3a26@localhost.localdomain>
	<8953E334-9BA8-463F-A5F0-E3D562F499D0@bulix.org>
Organization: Association altNetVision
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Le Thu, 1 Feb 2007 14:52:55 +0100,
Maxime Petazzoni <maxime.petazzoni@bulix.org> a =E9crit :

> Hi,
>=20
> Le 1 f=E9vr. 07 =E0 13:36, Nahuel ANGELINETTI a =E9crit :
>=20
> > We are trying to use mod_mbox with large range of mailing lists, and
> > got some problems, firstly is a problem about spam, if you
> > activate the
> > Antispam option it obfuscate the email adresses on message view
> > but not
> > in raw message, so we done a patch to hide the raw message link
> > ( attached file ).
>=20
> I remember a previous discussion on this point, but I don't recall =20
> the ending. The question is "Do we want a *true* (as in real) raw =20
> message, or just an extended display with headers and without MIME =20
> decoding ?"
>=20
> This is a decision we have to make before starting something because =20
> the second solution may involve user interface improvements (such as =20
> 'hide/show message headers', this kind of things).

I think the best way is like i done, allowing to hide raw message view
( and disable it )

> > Then another problem is with the encoding, we have lots of
> > =3D?iso-8859-1? and others on the mbox files and are not converted by
> > mod_mbox.
>=20
> At the time I worked on mod_mbox (summer 2005 mostly), the apr-iconv =20
> library was not fully functional (or at least not in a easy way with =20
> multibyte characters we encounter in UTF-x encoding). I believe the =20
> situation has changed now and that we could (finally) integrate =20
> charset conversion in mod_mbox.
>=20
> The fact that mod_mbox outputs UTF-8 comes from the ASF mailing list =20
> systems (for which mod_mbox was initially designed), and we know
> that mod_mbox does not really like other charsets. This is
> definitively a point that must be improved in mod_mbox, along with
> Javascript and user experience.

I think it can be possible to integrate easily the use of a library
like iconv or another. We need this feature rapidly and will try to
make it in those days.

> > And then mod-mbox-util parse only mbox with list-post, and if we
> > have some difusion list ( without list-post ) we cannot parse it,
> > what about
> > it ?
>=20
> For the moment, mod-mbox-util relies on the List-Post header to =20
> detect the mailing-list name and stuff, but we could make that more =20
> "intelligent" I guess.

For this stuff too, i'll work on it, list-post is not the main place
where the mailing list name can be found, like List-Id.

> I don't really have the time this week-end to take a look at these =20
> points (I'm leaving to the US on Sunday) but I'll definitively have =20
> some time for this, starting next Monday.
>=20
> Thanks for your interest in mod_mbox,
> - Maxime
>=20
> PS: concerning the attached patch, it is good, but we first have to =20
> decide what to do, regarding the question I asked in this email. =20
> Other mod_mbox users/developers, what are your thoughts ?

I think like I said, the better way is to enable the possibility to
disable feature ( like antispam ).=20
We are firstly users, because we have not only one project, but we can
contribute as we could ;)

Regards,

--=20
Nahuel ANGELINETTI
Association ~altNetVision
Jabber/XMPP : nahuel@ahtna.org