On tis 5 nov 2013 02:16:37, Alex wrote:
> Hi,
>
> I'm sorry to resurrect a month-old thread, but I'm still having a
> problem and it hasn't yet been fixed upstream.
>
> If you recall this thread, the problem is with 'file' misidentifying
> docx files with [trash]/0001.dat files in them as ARCHIVES
Hi,
I'm sorry to resurrect a month-old thread, but I'm still having a
problem and it hasn't yet been fixed upstream.
If you recall this thread, the problem is with 'file' misidentifying
docx files with [trash]/0001.dat files in them as ARCHIVES,
potentially resulting in them being tagged as a vir
On fre 6 sep 2013 01:35:30, Alex wrote:
> Hi,
>
>>> Running latest file, will not return ARCHIVE and amavis will not
>>> extract it and .dat or .dat (catche-all) will not trigger, so update
>>> file and your magics.
>>>
>>> thats how i solved it.
>>>
>>> eg:
>>> file ./test1.docx
>>> ./test1.docx:
Hi,
>> Running latest file, will not return ARCHIVE and amavis will not
>> extract it and .dat or .dat (catche-all) will not trigger, so update
>> file and your magics.
>>
>> thats how i solved it.
>>
>> eg:
>> file ./test1.docx
>> ./test1.docx: Microsoft Word 2007+
>
> Can you confirm what versio
Hi,
> Running latest file, will not return ARCHIVE and amavis will not
> extract it and .dat or .dat (catche-all) will not trigger, so update
> file and your magics.
>
> thats how i solved it.
>
> eg:
> file ./test1.docx
> ./test1.docx: Microsoft Word 2007+
Can you confirm what version that's wor
On Wed, 04 Sep 2013, Alex via amavis-users wrote:
> Hi,
>
> >> $ file \[trash\]/0001.dat
> >> [trash]/0001.dat: DOS executable (block device driver)
> >>
> >> Is this normal for a docx file? I'm sure the original sender had no
> >> idea this file contained a device driver. Is there something the
Patrik Båt via amavis-users schrieb am Thursday, den 05. September 2013:
> On 2013-09-04 15:55, Martin Fuxa via amavis-users wrote:
> > btw I have same problem with XLSB
> > http://lists.amavis.org/pipermail/amavis-users/2011-May/000367.html
> >
> >
>
> file ./test1.xlsb
> ./test1.xlsb: Microsoft
On 2013-09-04 15:55, Martin Fuxa via amavis-users wrote:
> btw I have same problem with XLSB
> http://lists.amavis.org/pipermail/amavis-users/2011-May/000367.html
>
>
file ./test1.xlsb
./test1.xlsb: Microsoft Excel 2007+
same with XLSB update file and its magics.
signature.asc
Description: Op
On 2013-09-05 01:15, Mark Martinec via amavis-users wrote:
> Alex,
>
>> Does anyone know if my suggestion to modify the $banned_filename_re
>> will work? Mark? :-)
>>
>> $banned_filename_re = new_RE(
>> [ qr'^\[trash\]/0001\.dat$' => 0 ],
>>
>> );
> Yes, I think it would work,
> but I'
Alex,
> Does anyone know if my suggestion to modify the $banned_filename_re
> will work? Mark? :-)
>
> $banned_filename_re = new_RE(
> [ qr'^\[trash\]/0001\.dat$' => 0 ],
>
> );
Yes, I think it would work,
but I'd have to try it on your document to make sure.
Better just get the fi
Hi,
>> $ file \[trash\]/0001.dat
>> [trash]/0001.dat: DOS executable (block device driver)
>>
>> Is this normal for a docx file? I'm sure the original sender had no
>> idea this file contained a device driver. Is there something the
>> sender needs to do to avoid this in the future?
>>
>> Is there
Hi,
>> >> $ file \[trash\]/0001.dat
>> >> [trash]/0001.dat: DOS executable (block device driver)
>> >>
>> >> Is this normal for a docx file? I'm sure the original sender had no
>> >> idea this file contained a device driver. Is there something the
>> >> sender needs to do to avoid this in the futu
On Wed, 04 Sep 2013, Alex wrote:
> Hi,
>
> >> $ file \[trash\]/0001.dat
> >> [trash]/0001.dat: DOS executable (block device driver)
> >>
> >> Is this normal for a docx file? I'm sure the original sender had no
> >> idea this file contained a device driver. Is there something the
> >> sender needs
btw I have same problem with XLSB
http://lists.amavis.org/pipermail/amavis-users/2011-May/000367.html
--
Regards Martin
Hi,
> We had a complaint from a user that an email with a .docx file was
> rejected. We have an amavisd policy where .exe binaries are rejected.
>
> Upon further inspection, the docx file contained a number of
> individual files, one of which was a dat file which appears to be some
> kind of binar
Alex via amavis-users schrieb am Tuesday, den 03. September 2013:
> Hi,
>
> We had a complaint from a user that an email with a .docx file was
> rejected. We have an amavisd policy where .exe binaries are rejected.
>
> Upon further inspection, the docx file contained a number of
> individual fil
Hi,
We had a complaint from a user that an email with a .docx file was
rejected. We have an amavisd policy where .exe binaries are rejected.
Upon further inspection, the docx file contained a number of
individual files, one of which was a dat file which appears to be some
kind of binary:
$ unzip
17 matches
Mail list logo
