[Mailman-Developers] 2.1b4+ evaluation order glitch.

[Daniel Buchmann]

---------------------- multipart/signed attachment
I'm also having a problem with the evaluation order.
I have messages that get held for approval, even though they would've
been auto-discarded by my sender filters. This is probably because I
have "Must posts have list named in destination (to, cc) field" set to
yes, which is probably evaluated before the sender filters...

On Mon, 2002-11-04 at 17:45, Chuq Von Rospach wrote:
>=20
> Barry --
>=20
> looks like 2.1b4 is evaluating messages slightly out of order. If I get=20
> a large piece of spam (my message limit is 30K, the spam is, say, 60k),=20
> it gets held as too large, before the evaluation can take place that=20
> should reject it as being from a non-subscriber. Seems to me these=20
> evaluations ought to be reversed...
>=20
>=20
> --=20
> Chuq Von Rospach, Architech
> chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/
>=20
> He doesn't have ulcers, but he's a carrier.
>=20
>=20
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
>=20
>=20


---------------------- multipart/signed attachment
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: This is a digitally signed message part
Url : http://mail.python.org/pipermail/mailman-developers/attachments/20021104/ff58b0cf/attachment.bin

---------------------- multipart/signed attachment--