[Mailman-Developers] Any other NNTP gatewayers out there? SMTP reject bounce processing is broken?

Barry Warsaw barry at python.org
Wed Nov 26 13:54:34 EST 2003

On Wed, 2003-11-26 at 12:01, Brad Knowles wrote:

> >  We've been seeing a very weird behavior where python-list (which is
> >  gated to and from comp.lang.python) suddenly mass bounce disables every
> >  regular delivery member.  The triggering bounce messages always come
> >  from NNTP, never from email.  The problem doesn't appear to affect
> >  digest members.  There are other clues <wink>.
> 	I imagine this is because digest mode results in stripping out 
> the problematic headers that would cause Exim to barf on the message. 
> Since the digest version of the message is sanitized, the digests get 
> through okay, while the unsanitized version of the message is 
> rejected.


> 	I do recall reporting problems whereby we tried to set up the 
> list as "closed" (so that only subscribers could post), and mailman 
> made the mistake of applying this action to incoming NNTP messages as 
> well as incoming SMTP messages, resulting in moderation notices being 
> sent to anyone who posted via NNTP from an address that was not 
> subscribed to the list.

I think that one's been since fixed.  None of the Moderation.py checks
are done on messages from NNTP.  Some of the Hold.py checks are still
done (all but the explicit destination check).

> 	As such, we were forced to turn off this feature.  It would be 
> nice if there was a way to get mailman to apply certain features to 
> messages only coming in via one of these mechanisms.  For example, I 
> would still like to apply the anti-spam methods and MIME format 
> stripping methods to messages coming in via both SMTP and NNTP, but 
> I'd like to be able to apply the posting restrictions only to 
> messages coming in via SMTP.

I agree that it would be nice to have more control over which checks are
done based on the origin of the message.  That's more of a feature
request for future versions though.  But try it again, because Mailman
2.1.3 should be applying mostly the right checks for gated messages.


More information about the Mailman-Developers mailing list