Confusion with Allow Filenames
Max Kipness
max at assuredata.com
Fri May 12 17:57:19 IST 2006
> On 12 May 2006, at 12:10, Max Kipness wrote:
>
> > I've been trying to find the answers from archived posts, but I'm
> > still
> > not sure if the following should work or not. I definitely doesn't
> > based
> > on emails with .bmp files attached sent from other mail servers
(that
> > don't block .bmp on outbound mail).
> >
> > In mailscanner.conf:
> > Allow Filenames = /etc/MailScanner/rules/allow.filename.conf
> > Allow Filetypes = /etc/MailScanner/rules/allow.filename.conf
> >
> > In /etc/MailScanner/rules/allow.filename.conf:
> > FromOrTo: myemailaddress at domain.com \.bmp
> > FromOrTo: default
> >
> > There are no errors being produced in the maillog, but the rule is
> > being
> > ignored completely.
> >
> > I saw another reference to creating the allow.filename.conf back to
> > individual filename.rule.conf files per domain, but I'd rather not
> > do it
> > that way unless necessary.
> >
> > Can the above work? Or what am I doing wrong?
>
> A few months ago I created an alternative way of doing all this which
> you may find much easier to use when creating simple sets of
> restrictions for different groups of users. One of the few things you
> cannot do with this new method is to have rules containing any tabs
> or spaces. But that's not a problem most of the time.
>
> First of all these configuration options are considered. If nothing
> matched, then the filename.rules.conf file is used as it always has
> been.
>
> There is course a similar set of options for filetypes as well as
> filenames.
>
> Can someone write some documentation for the wiki pointing out this
> alternative method please?
>
I've read the inline docs, and I'm not clear on how you use a ruleset to
accomplish what I explained above. Does the ruleset have to then point
to different filename.rules.conf files for each user/domain? Or is there
some other way of doing it?
Thanks,
Max
More information about the MailScanner
mailing list