I have a client whose header filters seemed to have stop working. No matter what I try, it seems none of their header filters are being applied. Other lists on the same server that use header filters, are working fine. This particular header is the subject header. I can duplicate their problem but only with their list. If I create the exact same header on a test list using the exact same subject line, the header filter does its job (moderate). Just not with this one list.
-- Brian Carpenter Harmonylists.com Emwd.com
On January 11, 2021 5:50:04 PM MST, Brian Carpenter <brian_carpenter@emwd.com> wrote:
I have a client whose header filters seemed to have stop working. No matter what I try, it seems none of their header filters are being applied. Other lists on the same server that use header filters, are working fine. This particular header is the subject header. I can duplicate their problem but only with their list. If I create the exact
same header on a test list using the exact same subject line, the header filter does its job (moderate). Just not with this one list.
Is the poster's moderation action or the list's moderation action set to accept? Moderation action accept (rather than default processing) will bypass header filters an many other rules.
-- Mark Sapiro <mark@msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.
On 1/11/21 8:48 PM, Mark Sapiro wrote:
On January 11, 2021 5:50:04 PM MST, Brian Carpenter <brian_carpenter@emwd.com> wrote:
I have a client whose header filters seemed to have stop working. No matter what I try, it seems none of their header filters are being applied. Other lists on the same server that use header filters, are working fine. This particular header is the subject header. I can duplicate their problem but only with their list. If I create the exact
same header on a test list using the exact same subject line, the header filter does its job (moderate). Just not with this one list. Is the poster's moderation action or the list's moderation action set to accept? Moderation action accept (rather than default processing) will bypass header filters an many other rules.
The "Default action to take when a member posts to the list " is set to Default Processing for the problematic list. The list members moderation action is set to "List Default" for the problematic list. I duplicated the same settings using another list. Header filters works fine on the test list, does not on the production list.
-- Brian Carpenter Harmonylists.com Emwd.com
On 1/11/21 6:14 PM, Brian Carpenter wrote:
On 1/11/21 8:48 PM, Mark Sapiro wrote:
On January 11, 2021 5:50:04 PM MST, Brian Carpenter <brian_carpenter@emwd.com> wrote:
I have a client whose header filters seemed to have stop working. No matter what I try, it seems none of their header filters are being applied. Other lists on the same server that use header filters, are working fine. This particular header is the subject header. I can duplicate their problem but only with their list. If I create the exact same header on a test list using the exact same subject line, the header filter does its job (moderate). Just not with this one list.
What's in the X-Mailman-Rule-* headers of the post that should be but isn't held?
Are there other header filter rules besides the one that doesn't work?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/12/21 9:57 PM, Mark Sapiro wrote:
On 1/11/21 6:14 PM, Brian Carpenter wrote:
On 1/11/21 8:48 PM, Mark Sapiro wrote:
On January 11, 2021 5:50:04 PM MST, Brian Carpenter <brian_carpenter@emwd.com> wrote:
I have a client whose header filters seemed to have stop working. No matter what I try, it seems none of their header filters are being applied. Other lists on the same server that use header filters, are working fine. This particular header is the subject header. I can duplicate their problem but only with their list. If I create the exact same header on a test list using the exact same subject line, the header filter does its job (moderate). Just not with this one list.
What's in the X-Mailman-Rule-* headers of the post that should be but isn't held?
Are there other header filter rules besides the one that doesn't work?
Also, on your test list, did you copy/paste the regexp or retype it. If the latter, there is possibly trailing whitespace that breaks it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/13/21 3:05 PM, Mark Sapiro wrote:
On 1/11/21 6:14 PM, Brian Carpenter wrote:
On 1/11/21 8:48 PM, Mark Sapiro wrote:
On January 11, 2021 5:50:04 PM MST, Brian Carpenter <brian_carpenter@emwd.com> wrote:
I have a client whose header filters seemed to have stop working. No matter what I try, it seems none of their header filters are being applied. Other lists on the same server that use header filters, are working fine. This particular header is the subject header. I can duplicate their problem but only with their list. If I create the exact same header on a test list using the exact same subject line, the header filter does its job (moderate). Just not with this one list.
What's in the X-Mailman-Rule-* headers of the post that should be but isn't held?
Are there other header filter rules besides the one that doesn't work? Also, on your test list, did you copy/paste the regexp or retype it. If
On 1/12/21 9:57 PM, Mark Sapiro wrote: the latter, there is possibly trailing whitespace that breaks it.
Thanks Mark. I am currently waiting for feedback from my client.
-- Brian Carpenter Harmonylists.com Emwd.com
Mark Sapiro wrote:
What's in the X-Mailman-Rule-* headers of the post that should be but isn't held? Are there other header filter rules besides the one that doesn't work?
This is what the client provided me:
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-listname.listdomain.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header
On 1/14/21 9:54 AM, Brian Carpenter wrote:
Mark Sapiro wrote:
What's in the X-Mailman-Rule-* headers of the post that should be but isn't held? Are there other header filter rules besides the one that doesn't work?
This is what the client provided me:
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-listname.listdomain.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header
So header-match-listname.listdomain.org-0 and no other header-match rule misses and no rule hits says there is only one header match rule and it missed. Since it hits in your test, I can only guess that the regexp in your test or the specific header in your test was not identical to what was in your test.
I assume you have access to the list settings. Does the offending regexp have trailing white space or something else different from your test? Or perhaps the offending header or regexp has some character which is ascii in one and a visually similar but different unicode in the other.
Also, I think but am not sure that we don't always properly decode RFC2047 encoded headers for header match rules. This would be a bug.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Brian Carpenter -
Mark Sapiro