[Mailman-Developers] MM3: list disabling/enabling?

[Patrick Ben Koetter]

* Barry Warsaw <barry at list.org>:
> >OTOH, I can imagine that for some purposes you might want a different
> >status code, and I don't see any good reason for making that
> >configurable and then restricting it to 5xx.  Rather, document it as
> >"this SHOULD be a 5xx code (in the RFC 2119 sense, ie, with
> >sufficient reason it could be a 4xx code, but we don't know of any
> >examples offhand :-)."
> 
> Do you really think it needs to be configurable?  I mean, if we can't think of
> a reason to not make it 5xx, why not just wait for the first wishlist bug
> report?  :)

A configurable reply could provide a hint along the 550 like this:

        550 See: http://list.example.com/550/listname

The listname ressource could inform why the list was retired e.g. because it
was relocated or closed or where to find the retired lists archives ...

p at rick

-- 
state of mind ()

http://www.state-of-mind.de

Franziskanerstraße 15      Telefon +49 89 3090 4664
81669 München              Telefax +49 89 3090 4666

Amtsgericht München        Partnerschaftsregister PR 563

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20110715/8d19ca81/attachment.pgp>