Hi, we are generally allowing doxy with the line
# allow anything in docx files
[ qr'.\.(docx)$'i => 0 ], # allow
but recently we had a case where docx documents were banned because they
hit the line
# banned filename extensions (in suggested names) anywhere - long
qr'(?# BLOCK MORE NAME EXTENSIONS )
^ (.*\t)? N= [^\t\n]* \. (
ade|adp|app|bas|bat|chm|cmd|com|cpl|crt|emf|exe|fxp|grp|hlp|hta|
inf|ins|isp|js|jse|lnk|mda|mdb|mde|mdw|mdt|mdz|msc|msi|msp|mst|
ops|pcd|pif|prg|reg|scr|sct|shb|shs|vb|vbe|vbs|
wmf|wsc|wsf|wsh) (\t.*)? $'xmi,
which is BELOW the above line. The complaint was :
BANNED CONTENTS ALERT
Our content checker found
banned name: P=p003,L=1,M=multipart/mixed |
P=p002,L=1/2,M=application/vnd.openxmlformats-officedocument.wordprocessingml.documen,T=zip,N==?utf-8?xyz?=,N=abc.docx
| P=p015,L=1/2/12,T=dat,N=word/media/image4.emf
OK, so it complains about an emf file inside the docx which is detected
as zip due to its container structure.
We would like to allow "more or less everything" inside a docx but not
in normal zip files. How can we achieve that.
Or, alternatively, how can we allow certain extensions to be OK in zip
files (but not all)?
Thank you for a hint,
Jakob Curdes
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
