Re: [Exim] .forward file

The 'if error_message' stanza prevents standard nondelivery reports
from being processed by the filter. You probably want to read the FQA
on *why* you normally want that.

Nondelivery reports (aka error messages) are identified by having a
null envelope sender. eg: "MAIL FROM: <>" )

Header lines arent allowd to have the null address, so most MTA's
generating bounces put MAILER-DAEMON@??? in the
From: header.

In your case, it looks like you are specifically trying to catch
nondelivery reports, so you might want to use.

if error_message then
save $home/mail/feemde+postmaster
endif

On Mon, 2 Oct 2000, James Ainslie wrote:

>
> Can someone explain this ??
>
> Hiya, as a new member of this list you must forgive me if this has
> appeared before :-)
>
> I have been have much pain with my .foward filters
> Most of them would work, but for some reason some of them just wouldnt,
> the syntax of all the rules was correct and the incoming mail had all the
> correct headers.
>
> my .forward file read as follows:
> -------------------------------------
> # Exim filter
> #
> if error_message then finish endif
> #
> logfile $home/.eximfilter.log
> #
>
> if $h_To: contains "Postmaster@???"
> or $h_From: contains "MAILER-DAEMON@???"
> then save $home/mail/feedme+postmaster
> endif
>
> finnish
> --------------------------------------
>
> What would happen is that the mail would come in and then not filter,
> droping into my default folder. Since the rule above implies a bulk mail
> account - this is beeg problem.
>
> However if I bounced/redirected the mail to me the filter worked ????.
>
> I managed to fix the problem by hashing out the line "if error_message
> then finish endif"...
>
> Why does this work ? to quote the docs :
>
> "Unless there is a good reason for not doing so, it is recommended that
> the above test be left in all filter files"
> (Exim Filter Specification, Testing an installed filter file)
>
> This seems like a good reason... but not good enough. *grin*
>
> Thanks
> James
>
>
>

--