[Mailman3-dev] Flexible data storage

Barry Warsaw barry at python.org
Mon Mar 15 17:20:50 EST 2004

On Mon, 2004-03-15 at 17:09, Erez Zadok wrote:

> On a related note, it's vital that MM3 will be as much as possible a drop-in
> replacement for MM2.  If a configuration/format change is required then I
> don't mind running a script "convert-v2-to-v3.py" but I don't want to have
> to hand-fix or hack my lists for V3.  It'd be even nicer if there were a
> backout option ("convert-v3-to-v2.py").  All these will be crucial for MM3's
> adoption (you don't want to be stuck maintaining both v2 and v3 for years,
> right?)
> I'm reminded that one of the reasons why EXT3 was adopted so quickly was
> that there had always been a simple procedure for converting an EXT2 file
> system to EXT3 -- *and* back(!)

Excellent point.  We should strive for that.

> Yes, well, there's a raging debate where anti-spam/anti-virus things should
> be addressed: the MTA, LDA, per-user, ingress routers, or even congress.  I
> personally think that ultimately the entire Internet will have to move to a
> strongly authenticated form of SMTP -- that seems to me like the most
> appropriate place for such filtering software.  But we're a long way from
> that happening, so for the time being, it'd be nice if MM3 could support it.
> Therefore, it is even more important that the way for supporting anti-spam
> packages in MM3 would be through flexible hooks/APIs.  

The filtering working group of ASRG is trying to flesh out
interoperability standards for headers and such.  I haven't had time to
follow the group closely, but I think that will be relevant here.


More information about the Mailman3-Dev mailing list