[Mailman-Developers] ANNOUNCE: GNU Mailman 3.0a1 (Leave ThatThing Alone)

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Apr 12, 2008, at 3:06 PM, Mark Sapiro wrote:
> Barry Warsaw wrote:
>> On Apr 11, 2008, at 9:30 AM, Ian Eiloart wrote:
>>
>>>> IIRC, this is going to be called when the "\r\n.\r\n" terminator to
>>>> the
>>>> DATA command is seen.  That might be an interesting place to hook  
>>>> in
>>>> content filtering.
>>>
>>> Yes, that's the earliest opportunity to filter content. It also
>>> allows the LTMP server to accept the message for some lists, but not
>>> others. It doesn't help the local SMTP server, though, since it's
>>> too late for an SMTP server to selectively reject.
>>>
>>> Some admins may prefer this though. For example, I monitor my SMTP
>>> server queues more closely than my Mailman queues.
>>
>> So you mean that most SMTPd's will have accepted the message by they
>> time they issue the DATA to the LMTP?  If that's the case, then does
>> it even make sense to do content filtering at that step in LMTP,  
>> given
>> that we'll still be doing the full-blown rule matching in the  
>> incoming
>> runner?
>
> I don't think that's what Ian is saying. The key word is  
> 'selectively'.
> I.e. the SMTP server can still reject the incoming message, but once
> it has seen the DATA, it can only reject the entire message; it can't
> reject a subset of RCPTs.


Ah, right, on the SMTP side.  LMTP can reject individual RCPTs, but  
the SMTP upstream of it can't.

Thanks,
- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkgBC9cACgkQ2YZpQepbvXGxpwCgnIYYZNTyI0JGRyJ6xCbfCwxU
FJIAnju+uzmG6QKjPHbFRIvGM0Ol7vMH
=fPWI
-----END PGP SIGNATURE-----