Quoting Dan Mick (Dan.Mick@West.Sun.COM):
My solution, suggested here, is working fairly well: make them beg for approval by setting a bunch of the right headers to be "suspicious": add
My solution is to run posts through procmail before mailman sees them. I've posted detailed instructions on this before, but I got the original idea from this mailing list before that.
Yup, and if it didn't involve procmail, I'd probably do it too. I despise having two tools for the same job, especially when one of them is a chainsaw with no blade guard or handle. ;)
Someone else posted Perl and Python scripts for prefiltering. Same objection, from my end.
I'd like to see Mailman have an option to "immediately trash" messages of various criteria: From someone@badhost.com, with header "text/html", etc.
Quoting Dan Mick (Dan.Mick@West.Sun.COM):
I've posted detailed instructions on this before, but I got the original idea from this mailing list before that.
Yup, and if it didn't involve procmail, I'd probably do it too. I despise having two tools for the same job, especially when one
Well, then you probably shouldn't be using Unix - that's the whole Unix philosphy: use an existing tool for a job it's good at, rather than trying to reinvent the same functionality.
of them is a chainsaw with no blade guard or handle. ;)
You *definitely* shouldn't be using Unix.
:-)
-- Paul Tomblin, not speaking for anybody. SETI@Home: Finally a *good* way to impress Jodie Foster http://www.setiathome.ssl.berkeley.edu/
Hi, This is what I get when I run check perms. Mailman runs fine...
/home/mailman/mailman-1.1 Traceback (innermost last): File "./check_perms", line 178, in ? checkall() File "./check_perms", line 88, in checkall os.path.walk(mm_cfg.PREFIX, checkwalk, STATE) File "/usr/lib/python1.5/posixpath.py", line 247, in walk func(arg, top, names) File "./check_perms", line 58, in checkwalk print path, 'bad gid (has: %s, expected %s)' % ( KeyError: getgrgid(): gid not found
Any clues as to how to fix this in case I do need check perms?
Regards, Maren.
"MSL" == Maren S Leizaola <maren@leizaola.com> writes:
MSL> This is what I get when I run check perms. Mailman runs
MSL> fine...
MSL> Any clues as to how to fix this in case I do need check
MSL> perms?It means your file has a gid that isn't in your groups database. Here's a patch for check_perms.
-Barry
-------------------- snip snip -------------------- Index: check_perms
RCS file: /projects/cvsroot/mailman/bin/check_perms,v retrieving revision 1.10 diff -c -r1.10 check_perms *** check_perms 1999/11/26 08:51:35 1.10 --- check_perms 1999/12/21 05:32:59
*** 54,62 **** continue raise if gid <> MAILMAN_GID: arg.ERRORS = arg.ERRORS + 1 print path, 'bad gid (has: %s, expected %s)' % ( ! grp.getgrgid(gid)[0], MAILMAN_GRPNAME), if STATE.FIX: print '(fixing)' os.chown(path, -1, MAILMAN_GID) --- 54,66 ---- continue raise if gid <> MAILMAN_GID:
try:groupname = grp.getgrgid(gid)[0]except KeyError:
! groupname, MAILMAN_GRPNAME), if STATE.FIX: print '(fixing)' os.chown(path, -1, MAILMAN_GID)groupname = '<anon gid %d>' % gid arg.ERRORS = arg.ERRORS + 1 print path, 'bad gid (has: %s, expected %s)' % (
Quoting Dan Mick:
I'd like to see Mailman have an option to "immediately trash" messages of various criteria: From someone@badhost.com, with header "text/html", etc.
I agree wholeheartedly. My list admin work tends to be twoactions:
1) Allowing through the relevant posts from non-subscribersand posts from subscribers using other accounts. 2) Automatically rejecting any mail that came in with a suspicious header. There's a REASON I put those headers on that list.
-- CrackMonkey.Org - Non-sequitur arguments and ad-hominem personal attacks LinuxCabal.Org - Co-location facilities and meeting space
participants (5)
-
Barry A. Warsaw -
Dan Mick -
Maren S. Leizaola -
Nick Moffitt -
Paul Tomblin