How to properly whitelist.
Julian Field
mailscanner at ecs.soton.ac.uk
Tue Dec 10 09:15:08 GMT 2002
At 22:41 09/12/2002, you wrote:
>Forgot one thing, now that I'm all excited about wildcards:
>
>There is a very nice set of reports and messages in various languages
>included in MailScanner.
>Could we make a rules list that would return a report in the senders
>language based on the domain they are sending it from (or possibly even
>the encoding of the message)?
>
>It wouldn't work 100% because you cannot set a default language for a .com
>or .net other than English but with a .se it would be nice to include
>something in Swedish. Maybe even include an English report as well
>together with the foreign language report for completeness?
>
>Would be kinda neato :)
For example:
MailScanner.conf contains:
Sender Virus Report = /etc/MailScanner/rules/sender.virus.rules
and then sender.virus.rules contains lines like this:
From: *@*.de /etc/MailScanner/reports/de/sender.virus.report.txt
From: *@*.dk /etc/MailScanner/reports/dk/sender.virus.report.txt
From: *@*.uk /etc/MailScanner/reports/en/sender.virus.report.txt
From: *@*.es /etc/MailScanner/reports/es/sender.virus.report.txt
From: *@*.fr /etc/MailScanner/reports/fr/sender.virus.report.txt
From: *@*.it /etc/MailScanner/reports/it/sender.virus.report.txt
From: *@*.nl /etc/MailScanner/reports/nl/sender.virus.report.txt
From: *@*.br /etc/MailScanner/reports/bt_pr/sender.virus.report.txt
From: *@*.ro /etc/MailScanner/reports/ro/sender.virus.report.txt
From: *@*.sk /etc/MailScanner/reports/sk/sender.virus.report.txt
FromOrTo: default
/etc/MailScanner/reports/en/sender.virus.report.txt
And don't even ask how the MailScanner.conf file knows you gave the
filename of a ruleset rather than the name of a report file, it just
does... :-)
>On Mon, 9 Dec 2002, Remco Barendse wrote:
>
> > Yes, I did read all the pages about the rules. The problem is that there
> > are lots of rules that you could make for every possibility. I've been
> > trying to play around with sendmail for a while but couldn't get anything
> > done because of the extremely hard to understand syntax.
> >
> > I think indeed one or two example rules with wildcards like
> > *@somedomain.com and *@*.somedomain.com would be helpful especially if
> > you're trying to set things up the first time. If you get the hang of it
> > it sort of appears obvious but until that time you just get frustrated
> > with things being (not) marked as they should and trying to figure out why
> > :)
> >
> > > >What would I need to add to get a wildcard like *@*.klm.com ?
> > >
> > > Exactly that:
> > > *@*.klm.com
> > >
> > > >Maybe it's a good idea to give ample examples in the rules list that is
> > > >included in mailscanner by default as there seem to be quite a few
> > > >questions about it?
> > >
> > > It's okay once you get the hang of it :-)
> > > But point taken. Have you read the "EXAMPLES" and "README" files in the
> > > rules directory provided in the distribution? Did they help? All
> > > contributions of things to add to these files would be most welcome.
> > > --
> > > Julian Field
> > > www.MailScanner.info
> > > MailScanner thanks transtec Computers for their support
> > >
> > >
> >
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> > Mailscanner thanks transtec Computers for their support.
> >
>
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
>Mailscanner thanks transtec Computers for their support.
--
Julian Field
www.MailScanner.info
MailScanner thanks transtec Computers for their support
More information about the MailScanner
mailing list