[Exim] exim bug? .forward filter always firing even for non-…

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Frank S. Bernhardt
Datum:  
To: Exim Users List
Betreff: [Exim] exim bug? .forward filter always firing even for non-spam
This is a multi-part message in MIME format.
--
I reported this problem a week ago but have had no response. It's
getting serious now as it's now happening at a customer's site.

We're running exim 4.22 with exiscan and spamassassin 2.63.

Everything was working pretty well for a while and then one day most of
the e-mail was being placed into the spam folder by .forward even though
the X-Spam-Status was set to No.

I ran a lot of tests, even ran debug but could see no reason for this. I
switched back to SA 2.43 and everything worked fine again.

I ran exim under debug for both 2.43 and 2.63 and compared the output.
They were pretty much identical but under 2.63 exim delivered the e-mail
into the spam folder (as confirmed by mainlog) but under 2.43 exim
delivered it to the user mailbox. I gave up and switched myself back to
2.43.

This morning I got a call from a customer complaining that they weren't
getting e-mail. Guess what? The e-mail was all going into the spam
folders. But not all the e-mail. I checked and saw that some e-mail was
dribbling through, but only a couple. No changes had been made to
their configuration since April 19th.

If I remove the .forward file all the e-mail goes through (even the spam
flagged, of course).

Is there a bug in exim that could be causing this?

Any help would be appreciated.

--

Regards

Frank S. Bernhardt
b.c.s.i.
14 Halton Court
Markham, ON. Canada
L3P 6R3

905-471-1691 Voice
905-471-3016 FAX

frank@???

Registered Linux-User #312398 with the Linux Counter, http://counter.li.org.
--
# Exim filter
if
$h_X-Spam-Status: contains "Yes"
or
"${if def:h_X-Spam-Flag {def}{undef}}" is "def"
then
save $home/spam
finish
endif
--