MailScanner blocking Docx files

alanoco79 · 09-17-2010, 04:08 AM

My MailScanner running on CentOs is blocking docx files, saying "The original e-mail attachment "****.docx"
is on the list of unacceptable attachments for this site and has been
replaced by this warning message.

I've tried adding it the list of allowed files:

/etc/MailScanner/filename.rules.conf:

allow \.docx$ - -

but it still blocks them.

I've also tried manually coping the message file from the /var/spool/MailScanner/quarantine/ directory into
/var/spool/postfix/incoming

but this did not result in the mail being delivered.

I desperately need these mails released, and docx files to be allowed unconditionally. Anyone know why the above isn't working?
Failing that, can all file blocking be turned off? I'd rather have virus relayed than legitimate mails blocked.

smoker · 09-18-2010, 06:18 AM

I don't know what version of MailScanner you're using, but in version 4.67.* you can add the Allow Filenames entry directly to the main MailScanner.conf

http://www.filewatcher.com/p/MailSca...nf.sample.html

Quote:

#
# Attachment Filename Checking
# ----------------------------
#

# To simplify web-based configuration systems, there are now two extra
# settings here. They are both intended for use with normal rulesets
# that you would expect to find in %rules-dir%. The first gives a list
# of patterns to match against the attachment filenames, and a filename
# is allowed if it matches any of these patterns. The second gives the
# the equivalent list for patterns that are used to deny filenames.
# If either of these match at all, then filename.rules.conf is ignored
# for that filename.
# So you can easily have a set like this:
# Allow Filenames = \.txt$ \.pdf$
# Deny Filenames = \.com$ \.exe$ \.cpl$ \.pif$
# which is a lot simpler than having to handle filename.rules.conf!
# It is far simpler when you want to change the allowed+denied list for
# different domains/addresses, as you can use the filename of a simple
# ruleset here instead.
# NOTE: The filename and filetype rules are separate, so if you want to
# allow executable *.exe files you will need at least
# Allow Filenames = \.exe$
# Allow Filetypes = executable
# to make it pass both tests. If either test denies the attachment
# then it will be blocked.

# Allow any attachment filenames matching any of the patterns listed here.
# If this setting is empty, it is ignored and no matches are made.
# This can also be the filename of a ruleset.
Allow Filenames =

# Deny any attachment filenames matching any of the patterns listed here.
# If this setting is empty, it is ignored and no matches are made.
# This can also be the filename of a ruleset.
Deny Filenames =

Also, read about quarantine management.