Executable vs Binary

[Kevin Miller]

I was fighting that a while back.  Actually, I still am.  See the "filename/filetype not working properly" thread in the archives.  Long story short, one person said that a newer version of /usr/bin/file fixed the issue.  I haven't verified that yet.

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4500
Registered Linux User No: 307357 


> -----Original Message-----
> From: MailScanner [mailto:mailscanner-bounces at lists.mailscanner.info] On
> Behalf Of Jerry Benton
> Sent: Thursday, April 16, 2015 11:46 AM
> To: MailScanner Discussion
> Subject: Executable vs Binary
> 
> Has anyone dealt with this? I can’t decide if I should mod the source or
> just change the configs:
> 
> - Microsoft document comes through with some sort of dat file embedded.
> While MS see that dat file as text/plain, the character set is binary,
> so it nails it as an executable.
> - Allowing executables will allow the file.
> 
> So, there’s the rub. Under the current code we have to allow executables
> for these “newer” types of Microsoft documents to get through. This
> isn’t restricted to just Microsoft. There are several other file formats
> that make MailScanner fire on this.
> 
> 
> Ideas?
> 
> -
> Jerry Benton
> www.mailborder.com
> 
> 
> 
> 
> 
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/listinfo/mailscanner