This problem seems to also create another side effect. It triggers the
SUBJECT_ENCODED_TWICE rule incorrectly.
If it is putting one at the end and the others at the front I think it
would
be a problem and worht opening a ticket. If the way it is will work with
DomainKeys then it is probably more an annoyance than a problem.
It always does exactly that and it is annoying as you say. I haven't
been able to verify if this creates a problem with DomainKeys yet
though (I upgraded 12 hours ago). I 'll open a ticket for this one
then.
Since everything moved up in SA 3.1 (it will take time to get
used to this one) shouldn't also X-Spam-Prev-Subject move up
there with the rest of X-Spam-...? IMHO, I find it more
Sounds like a bug to me if they aren't all in the same place.
Nope, they are not. In fact, I am not sure I ever saw
X-Spam-Prev-Subject with the other X-Spam headers. Shall I
open bugzilla report then?
