Hi Claudio,

We faced a similar issue and I remember struggling with it. To be safe, I added 
the exception right at the top of our definitions:

$banned_filename_re = new_RE(
# qr'^UNDECIPHERABLE$',  # is or contains any undecipherable components
 [ qr'^etp\.dat$'               => 0 ], # allow RIM messages

  # block certain double extensions anywhere in the base name
  qr'\.[^./]*\.(exe|vbs|pif|scr|bat|cmd|com|cpl|dll)\.?$'i,

...

We also took away the () brackets. Don't quote me on it, but I think the quotes 
might call the file(1) utility to determine the filetype, rather than trusting 
the extension. If that doesn't do the trick after reloading amavisd-new to 
re-read the config, give us a shout and I'll try to dig through my old notes a 
bit further.

Cheers,

________________________________

Hugo Slabbert

Website: www.i-worx.ca

making I.T. work for you

________________________________

-----Original Message-----
From: Claudio Kuenzler [mailto:[email protected]] 
Sent: Tuesday, September 22, 2009 7:43 AM
To: [email protected]
Subject: [AMaViS-user] Exclude certain files from Amavis/Virus-Scanning

Hello

I'm in need to have an exclusion for a certain filetype for a certain file.
It's a file sent from the BlackBerry servers and it always has the same
name: ETP.DAT

This is the content of the banned e-mail notification:

No viruses were found.



Banned name: application/octet-stream,.exe,ETP.DAT

Content type: Banned

Internal reference code for the message is 03754-02/KdLPJqVuzfHo



First upstream SMTP client IP address: [93.186.17.11]

  c17-011.eu.blackberry.net

According to a 'Received:' trace, the message apparently originated at:

  [93.186.17.11], etp2108.rly2.ad0.blackberry etp2108.etp2.blackberry

  [172.25.129.24]



Return-Path: <[email protected]>

From: [email protected]

Message-ID: <[email protected]>

Subject: RIM_bca28a80-e9c0-11d1-87fe-00600811c6a2

The message has been quarantined as: banned-KdLPJqVuzfHo



The message WAS NOT relayed to:

So I added this dat extension to the whitelist, to allow this extension:

# [ qr'^\.(Z|gz|bz2)$'           => 0 ],  # allow any in Unix-compressed
  [ qr'^\.(rpm|cpio|tar)$'       => 0 ],  # allow any in Unix-type archives
  [ qr'^\.(dat)$'               => 0 ],  # allow dat files
# [ qr'^\.(zip|rar|arc|arj|zoo)$'=> 0 ],  # allow any within such archives

But this doesnt work. The mail still gets banned.
Did I do a misconfiguration or is there another solution I should consider?

Thanks in advance.
------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; 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&#45;12, 2009. Register now&#33;
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/ 

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; 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&#45;12, 2009. Register now&#33;
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/ 

Reply via email to