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

Patrick Ben Koetter p at state-of-mind.de
Tue Jul 12 17:23:41 CEST 2011

* Barry Warsaw <barry at list.org>:
> On Jul 12, 2011, at 01:06 PM, Ian Eiloart wrote:
> >Bouncing certainly is suboptimal, since it may create collateral spam. Better
> >to reject the message at SMTP time with a 5xx response than to bounce.
> That's an interesting take on it.  The LMTP server in Mailman could reject
> messages addressed to disabled lists, and that 5xx error should propagate
> through the MTA.

Is disabling a list a temporary measure? If it is, should the server reply a
temporary error?

      421 <domain> Service not available, closing transmission channel
         (This may be a reply to any command if the service knows it
         must shut down)
      450 Requested mail action not taken: mailbox unavailable
         (e.g., mailbox busy)

Or is it permanent?

      550 Requested action not taken: mailbox unavailable
         (e.g., mailbox not found, no access, or command rejected
         for policy reasons)

p at rick

state of mind ()
Digitale Kommunikation


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/20110712/9fd31a86/attachment-0001.pgp>

More information about the Mailman-Developers mailing list