Re: [exim] Content scanning and non-MIME messages

Top Page
Delete this message
Reply to this message
Author: Heiko Schlittermann
Date:  
To: exim-users
Subject: Re: [exim] Content scanning and non-MIME messages
Ian Zimmerman via Exim-users <exim-users@???> (Di 24 Sep 2019 14:43:52 EDT):
> On 2019-09-24 13:51, Heiko Schlittermann wrote:
>
> > Isn't that well defined enough?
> > <spool_directory>/scan/<message_id>/<message_id>.eml
> >
> > It gets created on the first malware condition.
> Are you sure?


No, as always, I'm not sure :)

> I have no malware= condition in my configuration now. I had one until
> yesterday, but for a different and unrelated purpose, and I removed it.
> Nevertheless, my dlexpand module, which is called from the MIME acl with
> $mime_decoded_filename is an argument, continues to work. And the spec
> certainly seems to imply that the decoded part files are created only
> if and after the .eml file is created.


From what I understand, the $mime_decoded_filename is unrelated to the
.eml file. As the MIME ACL runs first, before the DATA ACL, and
according to the spec, the first malware condition creates the .eml
file.

So, I'd follow the spec, even if the .eml file gets created as a side
effect of the decode condition inside the MIME ACL.

--
Heiko