Re: [Exim] $message_filename ?

Top Page
Delete this message
Reply to this message
Author: W M Brelsford
Date:  
To: exim-users
Subject: Re: [Exim] $message_filename ?
On Tue Nov 19 2002 at 09:42 AM +0000, Philip Hazel wrote:
> On Sun, 17 Nov 2002, W M Brelsford wrote:
>
> > Is the name of the temp file containing the current message
> > available so I can use it in a filter (.forward) file? E.g.,
> >
> >    if "${run{bogofilter <$message_filename}{y}}" is y

> >
> > Or is there a way to pass the message on standard input to $run?
>
> The current message is not in a single file. See chapter 48 of the
> manual for a description of the two files that are used.


I realized that after sending the message (happens too often..).

> But it is not really intended that these files should be read by users'
> filters.[*] The whole filtering mechanism has got pushed rather far
> beyond its original conception. My design was that if users wanted to
> process files on delivery, they should redirect to a pipe and do all the
> processing completely independently of Exim.


> [*] With a normal configuration, the files are in any case only readable
> by exim or root.


I've considered doing it with procmail. But keeping it within Exim
has more advantages -- including simpler logging to keep track of
where the message went. I've found Exim's filtering to be powerful
(probably because it "got pushed rather far beyond its original
conception"), yet easy to set up and maintain. A "$run_stdin"
command would be nice here, but I can get by with the spool files
accessed through a small setuid program.

> But of course, users never use one's programs the way you intend
> them to. I should know that after 30 years...


Of course. And I bet it didn't take you 30 years to realize it..

Thanks.. Bill

--
Bill Brelsford
k2di2@???