[exim] FW: content type matching acl

Top Page
Delete this message
Reply to this message
Author: Craig Jackson
Date:  
To: exim-users
Subject: [exim] FW: content type matching acl
Sorry about this post. Please remove from list. Thanks.

> -----Original Message-----
> From: Craig Jackson
> Sent: Monday, August 25, 2008 4:04 PM
> To: 'exim-users@???'
> Subject: RE: [exim] content type matching acl
>
> Ya back? We had cake & ice cream. Ugh.
>
> > -----Original Message-----
> > From: Phil Pennock [mailto:exim-users@spodhuis.org]
> > Sent: Monday, August 25, 2008 1:00 PM
> > To: Craig Jackson
> > Cc: exim-users@???
> > Subject: Re: [exim] content type matching acl
> >
> > On 2008-08-25 at 10:48 -0500, Craig Jackson wrote:
> > > 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"

> >
> > The code (in Exim 4.69) iterates over all headers. It skips those
> > marked deleted (headers_remove) and check those left to match
> > "Content-Type:", case-insensitive.
> >
> > Are you sometimes deleting headers, and possibly matching
> > Content-Type?
> > Are these the top-level headers, not those from inside a multipart
> > message missing the MIME type at the top level?
> >
> > If the answers are "no" and "yes", then please actually provide the
> > debug logs. If you ask for help (ie, can't figure it out
> > yourself) and
> > are asked to provide debug logs, then *not* providing the
> logs because
> > you parsed out the content you think appropriate is really
> making life
> > harder for those trying to help you. Too much so.
> >
> > -Phil
> > .
> >