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

Barry Warsaw barry at list.org
Tue Jul 12 22:39:55 CEST 2011

On Jul 12, 2011, at 08:52 PM, Patrick Ben Koetter wrote:

>   550  Requested action not taken: mailbox unavailable (e.g., mailbox
>         not found, no access, or command rejected for policy reasons)
>         <http://www.rfc-editor.org/rfc/rfc5321.txt, section 4.2.3.  Reply
>         Codes in Numeric Order>

That would be my preference too.  I recently had a use case for something like
this.  The import-sig on python.org was retired a few years ago, but I just
resurrected it for the PEP 382 discussion.  I probably would have used this
feature for these sigs.

It does lead me to think that "retired" might be a better term, and it makes
me wonder whether actions like subscribing to a retired list would still be

But maybe the OP has a different use case in mind and we could have a need for
both a long-term, permanently failing retired lists, and shorter term,
temporarily failing disabled lists.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20110712/44461036/attachment.pgp>

More information about the Mailman-Developers mailing list