On SCO's 5.0.5 /usr/lib/mail/maildelivery file, I reached 200 lines
containing all spammers that I know of, but as soon as I add more lines,
those lines after line 200 do not execute, it seems there is a 200 line
limit for maildelivery, Is there a way of incrementing the 200 line limit
because I have new spammers everyday ?
Thanks for your help
maildelivery is not a really good place to do this. Get deliver from
ftp.jpr.com/pub. It will open endless possibilities what you can do
Tom Parsons t...@tegan.com
I ran into a similar problem - do an advanced groups.google.com search
in comp.unix.sco.misc, for articles in November 1997, with
".maildelivery" as the search term, and you'll see the discussion of
this and of a limit of 13 words per line in a .maildelivery
file. Both limits appear to be hard-coded.
If you are the system administrator, you might consider moving
at least some of your filtering to the incoming SMTP side - I find
obtuse SMTPD (available precompiled from www.xenitec.on.ca) very
useful for this. This is a better spot for it anyway in many cases.
Stephen M. Dunn <ste...@stevedunn.ca>
>>>----------------> http://www.stevedunn.ca/ <----------------<<<
Say hi to my cat -- http://www.stevedunn.ca/photos/toby/
This limit was removed in 5.0.6a. There is no longer any limit on the number
of rules you can have in a maildelivery file. It's possible that the binary
/usr/mmdf/chans/local from a 5.0.6a system would work on a 5.0.5 system. If
you try it, be sure that the permissions on the executable are preserved.
You could have a full-time job just adding to that list.
I used to add lines daily to 'access' in sendmail, and I'd also
just strip lines out of spam messages to add to that. That got to
be a bit tiring.
Has anyone implemented SpamAssassin in the sendmail on SCO. I
used it on my non-SCO mail system using sendmail and it uses text
analysis to determine spam and doesn't rely on sender addresses
[though you can have it look at blackhole and razor sites if you
With just local rules I find it's getting well over 95% of
the spam identified correctly, and it routes those messages
to another mailbox - so you don't have to worry about losing
anything, and you don't have your regular mailbox cluttered with
messages with a **SPAM** tag in the subject line.
I've been using it about 6 weeks now and I'm completely sold.
100% opensource and is implemented in Perl. You need to build
a new sendmail.cf file for it. That program alone I think is good
reason to move to sendmail from mmdf.
Bill Vermillion - bv @ wjv . com
I'm not using it systemwide yet, but I've been using it for my main mail
address since November. I use a variety of methods (RBLs, .maildelivery and
procmailrc rules, and other stuff) that diverted about 80% of spam from my
mailbox, but that still left me with a raft of spam every day. After
filtering via SpamAssassin, it's the exceptional day that *any* spam shows up
in my mailbox.
>I'm not using it systemwide yet, but I've been using it for my
>main mail address since November. I use a variety of methods
>(RBLs, .maildelivery and procmailrc rules, and other stuff)
>that diverted about 80% of spam from my mailbox, but that still
>left me with a raft of spam every day. After filtering via
>SpamAssassin, it's the exceptional day that *any* spam shows up
>in my mailbox.
My impression exactly. It's rare to find a program that works
better than you had any right to expect. I've even turned
off the razor lookups and just local processing as it processes
things much faster on my slower mail machine without having to
Do you know how to extract that file from the SCO's 5.0.6 installation CD ?
All I see is a lot of VOL's files.
The VOL files are cpio archives, so they're easy to extract from.
I don't know which one that file is in.