4.29.7: whitelist syslog chatter

Jeff Earickson jaearick at COLBY.EDU
Fri Apr 2 17:38:27 IST 2004


On Fri, 2 Apr 2004, Peter Bonivart wrote:

> Date: Fri, 2 Apr 2004 00:11:57 +0200
> From: Peter Bonivart <peter at UCGBOOK.COM>
> Reply-To: MailScanner mailing list <MAILSCANNER at JISCMAIL.AC.UK>
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: Re: 4.29.7: whitelist syslog chatter
>
> Jeff Earickson wrote:
> > Julian,
> >    Just upgraded from 4.29.3 to 4.29.7, and started noticing
> > a lot of:
> >
> > Message i31KrCIA028385 from 137.146.197.203 ... is whitelisted
> >
> > and I found this feature improvement noted in the ChangeLog.
> >
> > Since I have a whitelist entry for my class B netblock, ie
> >
> > From:   137.146.    yes
> >
> > then this new feature will generate a ton of meaningless chatter
> > to my syslog.  Err, what was the motivation for this feature?
> > Any way to shut it up???
>
> Do you whitelist so outgoing mail will not be marked as spam? If so, why
> not use the ruleset on "Spam Checks" instead and you will save some
> resources?

Yes, I don't want outbound email ever marked as spam.  If I go this
route of a Spam Checks ruleset, I would guess that it would be the inverse
of my whitelist rule, like:

#---don't spamcheck anything from my own netblock
From:   137.146.        no
#---do spamcheck everything else
From:   default         yes

Is this right (or a good idea)?

Jeff Earickson
Colby College



More information about the MailScanner mailing list