spam.whitelist.rules

[Furnish, Trever G]

Ken,

I saved the earlier thread about this and am just getting ready to attempt
it here, but I'm also looking to add detailed log processing and a web
interface for the logs.  Are you by any chance using sql logging and
Mailwatch with this set-up?  I was wondering whether the modified queue-ids
cause any problem for mailwatch...

--
Trever

>-----Original Message-----
>From: Ken Anderson [mailto:ka at PACIFIC.NET]
>Sent: Friday, August 01, 2003 8:59 AM
>To: MAILSCANNER at JISCMAIL.AC.UK
>Subject: Re: spam.whitelist.rules
>
>
>MailScanner looks at the first To address and evaluates the message
>based on that. That's not good for per-user whitelists in MailScanner.
>
>I went through this same process of "how do I really use per user
>whitelists?", and ended up using sendmail to split all messages with
>more than 1 recip into x messages with 1 recipient, so MailScanner only
>sees 1 recip per message. NOTE: This raises the load on your server
>substantially, since x recipients means x messages now, but it works,
>and that's what I needed. :-)
>
>CustomConfig.pm can give you whitelisting per user, and sendmail can
>split messages into 1 recip per message to make the whitelists work as
>they should.
>
>To make sendmail 8.12.x split the messages, you do this:
>
>1) Start the incoming sendmail with a different config file.
>Changes to /etc/rc.d/init.d/MailScanner (from rpm install on redhat)
>make this change to the incoming sendmail command line:
>
>------ snip -------
>
>  $SENDMAIL -bd -OPrivacyOptions=noetrn \
>                       -ODeliveryMode=queueonly \
>                       -OQueueDirectory=$INQDIR \
>                       -OPidFile=$INPID \
>                       -C/etc/mail/sendmail_in.cf
>
>-------- snip --------
>
>2) Make changes to the new sendmail config:
>cp /etc/mail/sendmail /etc/mail/sendmail_in.cf
>
>In sendmail_in.cf, add the following:
>The comment header "QUEUE GROUP DEFINITIONS" should be there already.
>Just add the single line under it.
>
>------- snip --------
>############################
># QUEUE GROUP DEFINITIONS  #
>############################
>
>Qmqueue, P=/var/spool/mqueue.in, F=f, r=1, R=8, I=2m
>
>------- snip --------
>
>
>AND, just above the "Ruleset 3" comment header, add the following:
>(not sure if both lines are required or not...)
>
>--------- snip --------
>
># LOCAL_RULESETS
>Squeuegroup
>R$* @ $*                $# mqueue
>R$*                     $# mqueue
>
>############################################
>###  Ruleset 3 -- Name Canonicalization  ###
>############################################
>
>
>--------- snip ----------
>
>
>Restart sendmail, and things like this start showing up in the log when
>messages with multiple recipients come in:
>
>Jul 17 08:14:31 host sendmail[7183]: h6HFDop8007183: split: maxrcpts=1,
>rcpts=3, count=2, ids=h6HFDop9007183; h6HFDopA007183
>
>
>Ken A
>Pacific.Net
>
>
>
>
>John Rudd wrote:
>
>> What does mailscanner do if a message has multiple recipients, and
>> their per-user settings don't agree with each other?
>>
>>
>> On Thursday, Jul 31, 2003, at 22:10 US/Pacific, Ken Anderson wrote:
>>
>>>
>>> See CustomConfig.pm for an example of how per-domain or per-user
>>> whitelists can be implemented.
>>> Ken A.
>>>
>>>
>>> Alan Fiebig wrote:
>>>
>>>> I'm sorry for my ignorance,  but if this is an answer to
>my question,
>>>> I sure don't understand it:
>>>>
>>>>
>>>>> Hash: SHA1
>>>>>
>>>>> On Thursday 31 July 2003 10:11 am, Kris Zabriskie wrote:
>>>>> To: | From: | FromTo:     *@domain-name.com | user at domainname.com
>>>>> Don't forget
>>>>> FromorTo:
>>>>> - --
>>>>> Lewis Bergman
>>>>> Texas Communications
>>>>
>>>>
>>>>
>>>>
>>>> My question:
>>>>
>>>>
>>>>
>>>>> As I understand the spam whitelist rules, I can whitelist a given
>>>>> sender, or a given recepient.
>>>>>
>>>>> Is there a means to whitelist a given sender/recepient pair?
>>>>>
>>>>> I have a number of customers who request to receive
>emailings from a
>>>>> given company. But not everyone wants the 'mail' being
>sent by this
>>>>> company.
>>>>>
>>>>> If I whitelist the sender, then all my customers are open to their
>>>>> 'junk mail' messages.
>>>>> If I whitelist the customer who wants this company's
>mail, then they
>>>>> get all spam and no filtering.
>>>>>
>>>>> What I need is the ability to create a rule that says
>mail from THIS
>>>>> sender to THIS recepient is whitelisted.
>>>>>
>>>>> Can this be done now?
>>>>> Could it be done?
>>>>>
>>>>> Thanks,
>>>>> -Alan
>>>>
>>>>
>>>>
>>>>
>>
>>
>