Nigel et al.,
It was set up this way back in the dim and distant past as a q+d hack
when there were a lot less recipients of the message under Exim 2.xx or
3.xx. Still pretty inexcusable though.
I'll try your suggestion on the development server as it is obviously a
far more superior solution.
As for what went wrong this time: mail was getting through where it
shouldn't.
Here are two examples. The former shows the filter working at 7:17am
yesterday:
Working:
2003-07-09 07:17:30 19a8Gg-0007PZ-00 <= mailing@???
H=anchor-fallback-94.mail.demon.net [194.217.242.94] P=esmtp S=3783
id=E19ZXko-0006gU-00@???
2003-07-09 07:17:30 19a8Gg-0007PZ-00 cancelled by system filter: This
message has been rejected because it has it been forwarded\n an
invalid MTA 194.217.242.94 and has probably been falsly relayed\n If
you have any further queries please contact:\n
mailto:postmaster@eduserv.org.uk
2003-07-09 07:17:30 19a8Gg-0007PZ-00 Completed
Failing to filter:
2003-07-09 14:45:57 19aFGf-0006h6-00 <= mailing@???
H=orion.uk.insnet.net (relay.mail.insnet.cw.net) [194.177.170.11]
P=esmtp S=3379 id=E19ZXko-0006gU-00@???
2003-07-09 14:46:06 19aFGf-0006h6-00 ** helen@???
<mail-list@???>: Unrouteable address
[.....]
Also, for the former an entry was made in the filter logfile, for the
latter nada.
Nic (Apologies for the poor formatting - having to use Outlook which I
don't know how to use).
