> -----Original Message-----
> From: exim-users-bounces@???
> [mailto:exim-users-bounces@exim.org] On Behalf Of Phil Pennock
> Sent: Friday, February 08, 2008 3:41 PM
> To: Craig Jackson
> Cc: exim-users@???
> Subject: Re: [exim] Mime + filename matching
>
> On 2008-02-08 at 10:10 -0600, Craig Jackson wrote:
> > condition = ${if or { \
> > {
> >
> match{${lc:$mime_filename}}{\N^(?>.*)(?<=zip|emz|iso|wma|jpg|j
peg|pps|pp
> > t|gif|png|wmv|mpg|mp3|mpeg|avi|wav|bmp|mov|asf|asx|mpe)\N}} \
> > {
> >
> match{${lc:$mime_content_type}}{\N^(zip|emz|iso|wma|jpg|jpeg|p
ps|ppt|gif
> > |png|wmv|mpg|mp3|mpeg|avi|wav|bmp|mov|asf|asx|mpe)\N}} \
> > }{1}{0}}
> > set acl_m7 = 1
> >
> > This acl works perfectly except for certain emails and I'm not smart
> > enough to figure out how to get Exim to work to work with
> those emails.
>
> > --____RAAJBJVHFFDKGUUJDDWU____
> > Content-ID: <LTPCYOQCHLLK.GW}00014.BMP>
> > Content-Type: image/BMP
> > Content-Transfer-Encoding: base64
> >
> > Seems to me that the acl should have seen that MIME boundary and set
> > acl_m7 to 1. Can someone please tell me why it didn't?
>
> The match condition does a regexp comparison; unlike 'regexp
> as an item
> in a list' it doesn't default to case-insensitive.
>
> $ exim -be
> > ${if match{foo}{\N^f[aeiou].$\N} {w00t}{bah}}
> w00t
> > ${if match{FOO}{\N^f[aeiou].$\N} {w00t}{bah}}
> bah
> > ${if match{foo}{\N(?i)^f[aeiou].$\N} {w00t}{bah}}
> w00t
> > ${if match{FOO}{\N(?i)^f[aeiou].$\N} {w00t}{bah}}
> w00t
> >
>
> By putting "(?i)" in the regexp before the literal
> characters, you make
> sure that they're interpreted in a case-insensitive manner.
>
> "man pcrepattern" and "INTERNAL OPTION SETTING".
>
> -Phil
Thanks for relying, Phil.
Case did occur to me, so that's why I used ${lc:$mime_filename}
Wouldn't that take care of case?
(?<=zip%7Cemz%7Ciso%7Cwma%7Cjpg%7Cj%0A>%20peg%7Cpps%7Cpp%0A>%20>%20>%20%0A>%20>%20match%7B%24%7Blc:%24mime_content_type%7D%7D%7B%5CN%5E(zip%7Cemz%7Ciso%7Cwma%7Cjpg%7Cjpeg%7Cp%0A>%20ps%7Cppt%7Cgif%0A>%20>%20>%20%0A>%20>%20>%20This%20acl%20works%20perfectly%20except%20for%20certain%20emails%20and%20I'm%20not%20smart%0A>%20>%20>%20enough%20to%20figure%20out%20how%20to%20get%20Exim%20to%20work%20to%20work%20with%20%0A>%20>%20those%20emails.%0A>%20>%20%0A>%20>%20>%20--____RAAJBJVHFFDKGUUJDDWU____%0A>%20>%20>%20Content-ID:%20<LTPCYOQCHLLK.GW%7D00014.BMP>%0A>%20>%20>%20Content-Type:%20image/BMP%0A>%20>%20>%20Content-Transfer-Encoding:%20base64%0A>%20>%20>%20%0A>%20>%20>%20Seems%20to%20me%20that%20the%20acl%20should%20have%20seen%20that%20MIME%20boundary%20and%20set%0A>%20>%20>%20acl_m7%20to%201.%20Can%20someone%20please%20tell%20me%20why%20it%20didn't?%0A>%20>%20%0A>%20>%20The%20match%20condition%20does%20a%20regexp%20comparison;%20unlike%20'regexp%20%0A>%20>%20as%20an%20item%0A>%20>%20in%20a%20list'%20it%20doesn't%20default%20to%20case-insensitive.%0A>%20>%20%0A>%20>%20%20%24%20exim%20-be%0A>%20>%20%20>%20%24%7Bif%20match%7Bfoo%7D%7B%5CN%5Ef%5Baeiou%5D.%24%5CN%7D%20%7Bw00t%7D%7Bbah%7D%7D%0A>%20>%20%20w00t%0A>%20>%20%20>%20%24%7Bif%20match%7BFOO%7D%7B%5CN%5Ef%5Baeiou%5D.%24%5CN%7D%20%7Bw00t%7D%7Bbah%7D%7D%0A>%20>%20%20bah%0A>%20>%20%20>%20%24%7Bif%20match%7Bfoo%7D%7B%5CN(?i)%5Ef%5Baeiou%5D.%24%5CN%7D%20%7Bw00t%7D%7Bbah%7D%7D%0A>%20>%20%20w00t%0A>%20>%20%20>%20%24%7Bif%20match%7BFOO%7D%7B%5CN(?i)%5Ef%5Baeiou%5D.%24%5CN%7D%20%7Bw00t%7D%7Bbah%7D%7D%0A>%20>%20%20w00t%0A>%20>%20%20>%20%0A>%20>%20%0A>%20>%20By%20putting%20%22(?i)%22%20in%20the%20regexp%20before%20the%20literal%20%0A>%20>%20characters,%20you%20make%0A>%20>%20sure%20that%20they're%20interpreted%20in%20a%20case-insensitive%20manner.%0A>%20>%20%0A>%20>%20%22man%20pcrepattern%22%20and%20%22INTERNAL%20OPTION%20SETTING%22.%0A>%20>%20%0A>%20>%20-Phil%0A>%20%0A>%20Thanks%20for%20relying,%20Phil.%20%0A>%20%0A>%20Case%20did%20occur%20to%20me,%20so%20that's%20why%20I%20used%20%24%7Blc:%24mime_filename%7D%0A>%20Wouldn't%20that%20take%20care%20of%20case?%0A>%20%0A>%20 "Reply to this message")