Re: [exim] content type matching acl

トップ ページ
このメッセージを削除
このメッセージに返信
著者: Craig Jackson
日付:  
To: exim-users
題目: Re: [exim] content type matching acl


> -----Original Message-----
> From: exim-users-bounces@???
> [mailto:exim-users-bounces@exim.org] On Behalf Of Phil Pennock
> Sent: Thursday, August 14, 2008 4:36 PM
> To: Craig Jackson
> Cc: exim-users@???
> Subject: Re: [exim] content type matching acl
>
> On 2008-08-14 at 15:51 -0500, Craig Jackson wrote:
> > In the mime acl, there is a condition for catching emails
> with certain
> > content types:
> >
> >
> >
> match{${lc:$mime_content_type}}{\N^(?>.*)(?<=m4a|powerpoint|pp

t|pps|quic
> >
> ktime|msvideo|javascript|midi|zip|wma|jpg|jpeg|gif|png|wmv|mpg
> |mp3|mpeg|
> > mpeg-2|avi|wav|bmp|mov|asf|asx|mpe)\N}
> >
> > However, an email with a gif got through that had a content type as
> > follows:
> >
> > Content-Type: image/gif;
> >     name="image001.gif"

> >
> > Is the final quote the problem? Or is the filename located in the
> > content type the problem? Could this be fixed by adding "?
> to the regex
> > like this?
>
> No; $mime_content_type does not include any options such as "name" so
> that's not being considered. (In theory; I haven't checked source).
>
> If you take a copy of the received message, strip off headers added by
> your system, run "exim -d+acl+expand -bs -bh orig.in.al.ip"
> then do SMTP
> to send the message, you'll (a) not deliver it, so don't worry about
> duplicates and (b) be able to see the ACL logic and the string
> expansions. The string expansion should show you what was in
> $mime_content_type and the ACL debugging logic as a whole will confirm
> that this condition was even being tested.
>
> -Phil
>


I am having this problem with several emails that are getting through
this acl. I ran the test you suggested. The result was ">>
No Content-Type: header - presumably not a MIME message." But the
Content-Type header is clearly there:

Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/related;
    type="multipart/alternative";
    boundary="----_=_NextPart_001_01C90494.E72C586C"
Subject: FW: Funny Felines
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
Date: Fri, 22 Aug 2008 15:23:13 -0500
Content-Transfer-Encoding: 7bit
Message-ID: <02355FF52957E4469532537DB5D75FA1051071@???>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator:



And the mime boundary is also there:

------_=_NextPart_002_01C90494.E72C586C--

------_=_NextPart_001_01C90494.E72C586C
Content-Type: image/jpeg;
    name="ATT13960.jpg"
Content-Transfer-Encoding: base64
Content-ID: <_2_048B7F08048B84A8006E555C862574AD>
Content-Description: ATT13960.jpg
Content-Location: ATT13960.jpg


Why is Exim not seeing the mime part and what can I change to make it
see it?

Thanks for your reply.

Craig