-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
>> Most likely, it got caught in the spamfilter. Anything that comes
>> through the bug report form is just sent to pgsql-bugs@, so it'll pass
>> through both the maia filters and potentially through moderation as well.
> I think the problem is that there aren't enough moderators for
> pgsql-bugs (and a bunch of other lists as well).
There is no "potential": all bug reports from the form are filtered for
moderation, as they should be, due to the amount of form spam. However,
the real problem with that lists (and the others) is not so much the
lack of moderators, but the hassle the existing ones have to go through,
due to the very limited spam filtering done on the lists. I've raised
this problem a few times, but this time I'll make links instead of posting
the sample spam itself, to prevent further filtering.
Here is the most recent message sent to pgsql-bugs. Note the total lack of
any spam hits (see lines 28 and 29), despite the many freely available
spamassassin recipes that should have caught this:
http://privatepaste.com/35TMBvAiHz
Here's an interesting one that just came in to -announce:
http://privatepaste.com/96hmnRRrlK
Note the multiple greylisting, and the fact that this spam at least
hit one of the spam tests, but at 1.37 for the DCC check, with a
final criteria of 5, it's unlikely to ever be effective.
My recomendations? Add a lot more SA tests, lower the overall threshhold
to under 5, and tweak the numbers on some of the existing tests
(I recall that some of the tests are at .01 or some useless number)
- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200901072134
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAkllZnIACgkQvJuQZxSWSshTVQCg7Km8fzMUftTGIqyEBabA+BqM
c1EAoJAR5LgJ/4aNmprc1dS1rkSkrFlM
=AMK8
-----END PGP SIGNATURE-----
