office 2007 files being treated as archives

[Alex Neuman van der Hans]

Julian Field wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> Alex Neuman van der Hans wrote:
>   
>> Scott Silva wrote:
>>     
>>> Alex Neuman van der Hans spake the following on 9/6/2007 9:04 PM:
>>>       
>>>> Julian Field wrote:
>>>>         
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> Add a new line to filename.rules.conf (somewhere near the top) that 
>>>>> says this:
>>>>> allow   \.xml\.rel$   -   -
>>>>> Make sure the 4 "words" are separated with tab characters and not 
>>>>> spaces. This (along with its partner filetype.rules.conf) is the 
>>>>> only place where tab characters must be used, as the regular 
>>>>> expression matching the filename, and the reports (which are just 
>>>>> "-" for an "allow" rule) could also contain spaces.
>>>>>
>>>>>   
>>>>>           
>>>> This could work - but I've already had other problems with Office 
>>>> 2007 files. I don't recall exactly what right now - I implemented 
>>>> something to get it out of the way and forgot about it, but I think 
>>>> it was similar. It would be a good thing if anybody else comes out 
>>>> and mentions any details regarding this so we can take proper action.
>>>>
>>>> Anybody here know why these files are treated as archives? Any other 
>>>> light that could be shed on the subject might help to better deal 
>>>> with these files, since we're all going to be finding them more 
>>>> often as people start "upgrading" to Office 2007.
>>>>         
>>> If you look at the spec they are an archive. Multiple files in a 
>>> container which I believe is a zip file.
>>>
>>>       
>> And as such, susceptible to misinterpretation - I think I got one 
>> saying the file was "too compressed to be a real archive", which to me 
>> sounds like some part of MailScanner or clam or something (I'm still 
>> trying to remember the specifics) thought it was like one of those 
>> "42.zip" type problems.
>>     
> That's not a MailScanner error message.
>
>   
I know it's not "specifically", but I *did* see MailScanner's indication 
of some subcomponent's misconception about the file. I haven't been able 
to reproduce the problem and I don't recall the details of the specific 
case, but I *will* definitely share anything on the subject as soon as 
it presents itself again.
> Jules
>
> - -- 
> Julian Field MEng CITP
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> MailScanner customisation, or any advanced system administration help?
> Contact me at Jules at Jules.FM
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> For all your IT requirements visit www.transtec.co.uk
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP Desktop 9.6.2 (Build 2014)
> Charset: ISO-8859-1
>
> wj8DBQFG4cRTEfZZRxQVtlQRAuXIAKCLK/osbTYq7/H1UqUEsC3X0Ur9bwCfVhhK
> 0doP5h+dtBmT6oCGTrtr1RE=
> =rgcV
> -----END PGP SIGNATURE-----
>
>