-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> X-Virus-Scanned: by amavisd-new at postgresql.org
Since "amavisd" does not appear to be catching the latest worm,
how about filtering on size? Anything, say, over 20K will be held
for approval. Here are the top posts by size to this list recently:
subject | whofrom | size
-
-----------------------------------------------------------+--------------------------------------------------+-------
[GENERAL] Select for update, locks and transaction levels | "Nick Barr" <nick.barr@webbased.co.uk> | 35107
[GENERAL] stacy | scrappy@postgresql.org | 32648
[GENERAL] My photoalbum | scrappy@postgresql.org | 32600
[GENERAL] stacy | scrappy@PostgreSQL.org | 32467
[GENERAL] Weah, hello! :-) | scrappy@postgresql.org | 29462
[GENERAL] Weeeeee! ;))) | scrappy@postgresql.org | 29460
[GENERAL] Hey, ya! =)) | scrappy@PostgreSQL.org | 29428
[GENERAL] :) | scrappy@postgreSQL.org | 29305
[GENERAL] Hokki =) | scrappy@postgresql.org | 28738
[GENERAL] :) | scrappy@PostgreSQL.org | 28667
[GENERAL] help using arrays in a function | "Jennifer Lee" <jlee@scri.sari.ac.uk> | 22774
Note that the first one is not a worm but 4k of message content with about 30k
of unnecessary HTML markup. Filtering such stuff would be alright with me too. :)
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200403040640
-----BEGIN PGP SIGNATURE-----
iD8DBQFARxYmvJuQZxSWSsgRAvn2AJ47YY4gZKaISddB0i3/Ew8bZdPcygCfQOnB
1eknd99Tjp3j5+vwfpJ5NCk=
=coS2
-----END PGP SIGNATURE-----
