Hello,
On Thu, Dec 14, 2006 at 06:55:03PM +0000, exim@??? wrote:
> On Thu, Dec 14, 2006 at 09:57:55AM +0100, Matthias Waffenschmidt wrote:
> > > When this happens the message hangs out in the queue (waiting for a retry
> > > timer to exipre?). But it seems as though the recipient of the message is
> > > still set to the original recipient, rather than the new recipients
> > > specified by the deliver command, because if a queue run starts, the message
> > > is delivered to its original recipient:
> >
> > This is a wild guess because you have only showed us parts of your
> > filter file, but it would explain the behaviour you are experiencing:
> >
> > Does your filter test for first_delivery earlier and not even reach
> > the deliver commands?
>
>
> Hi,
>
> Thanks for the response. No, I don't test for first_delivery anywhere in
> the system filter (I didn't include the entire filter because its really
> long and confusing), but I do have the following at the top of the filter
> way before the deliver commands that I'm having problems with:
>
> if $h_to: matches
> "(?:scam@???|admin@???|reports@???|pirt@???|reportphishing@???|abuse@)"
> then finish endif
>
> I change the To: header in the scam message that I'm redirecting via the
> deliver command to include the address of the recipients - so it would
> match the condtion.
OK, with the additional information you gave (including the contents
of the spool file), I think that you have indeed found a bug.
Exim should delete the original recipient from the recipient list if
the system filter has set up a significant delivery and the filter
completed successfully, no matter if the delivery succeeds or not.
Maybe you should file the bug into the bugzilla system.
--
Gruss / Best regards | LF.net GmbH | fon +49 711 90074-411
Matthias Waffenschmidt | Ruppmannstr. 27 | fax +49 711 90074-33
mw@??? | D-70565 Stuttgart | http://www.lf.net
