I have DoMSGIDsig set to block which seems to be blocking most of the
messages I previously sorted out.
I have one or two messages that seem to still be getting past the
filters, for some reason these seem to be scored rather than blocked.
Are there any other settings that would cause a
ASSP development mailing list assp-test@lists.sourceforge.net schrei
bt:
017 X-Assp-Spam: YES
018 X-Spam-Status:yes
062 X-Assp-Spam-Reason: MSGID-sig check failed for bounce sender
Then header are saying, that the mail was caught and considered Spam.
Why do you think, it went through?
On 20/10/2012 13:03, Fritz Borgstedt wrote:
ASSP development mailing list assp-test@lists.sourceforge.net schrei
bt:
017 X-Assp-Spam: YES
018 X-Spam-Status:yes
062 X-Assp-Spam-Reason: MSGID-sig check failed for bounce sender
Then header are saying, that the mail was caught and
ASSP development mailing list assp-test@lists.sourceforge.net schrei
bt:
The subject was tagged as [ Possibly Spam ] and the message let past
ASSP into my Exim queues. So, the headers are saying that the message
should have been blocked when it wasn't.
The tag is Possibly . This is normally
Based on my own experience and that of others (looking at the postings
including the current MSGID discussion), I can help but wonder if ASSP
configuration has gotten too complex.
I'm not suggesting we drop features, but maybe the who way it is configured
needs to be rethought!? Instead of
