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@???> (Sa 21 Sep 2019 05:05:03 CEST):
> >
> >     acl_smtp_mime     = check_mime
> >     acl_not_smtp_mime = check_mime

> >
> >     acl_smtp_data = check_data
> >     acl_not_smtp  = check_data

> >
> > And I believe, the actions you'd do on plain text bodies differ from
> > those of mime parts, don't they?
>
> No, I would do the same actions, if I could :-(.
>
> I use the mime acls to search for text in parts of type text/*, it
> is very convenient because I get it already decoded and the whole part
> saved in a file.


In theory a non-MIME message should not contain encoded text, at least
not according the MIME specs. But yes, I remember times where the plain
text used uuencode to get binary stuff through.

> $message_body doesn't do the same thing, I'll have to invent a different


IMHO $message_body does not contain the whole message, only parts of it.
And I do not know, if the DATA ACL would tell you the spool file
name, probably not, as it is considered private.

But the message gets written to the scan/ dir
if you request content inspection (demime, or malware condition),
and demime gives you access to $mime_decoded_filename.

But - maybe I'm totally wrong here, it all are just assumptions (and as
these the mother of all fuckups)

    Best regards from Dresden/Germany
    Viele Grüße aus Dresden
    Heiko Schlittermann
--
 SCHLITTERMANN.de ---------------------------- internet & unix support -
 Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
 gnupg encrypted messages are welcome --------------- key ID: F69376CE -
 ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -