Am 29.12.2015 um 21:46 schrieb Philip Prindeville:
On Dec 29, 2015, at 1:42 PM, Kevin A. McGrail wrote:
On 12/29/2015 3:38 PM, Philip Prindeville wrote:
Is there a reason that headers are left with leading spaces?
I’ve noticed that I have to write rules as:
Subject =~
On Dec 29, 2015, at 2:14 PM, Kevin A. McGrail wrote:
> On 12/29/2015 3:46 PM, Philip Prindeville wrote:
>> On Dec 29, 2015, at 1:42 PM, Kevin A. McGrail wrote:
>>
>>> On 12/29/2015 3:38 PM, Philip Prindeville wrote:
Is there a reason that headers are
On Dec 29, 2015, at 1:42 PM, Kevin A. McGrail wrote:
> On 12/29/2015 3:38 PM, Philip Prindeville wrote:
>> Is there a reason that headers are left with leading spaces?
>>
>> I’ve noticed that I have to write rules as:
>>
>> Subject =~ /^ Great [Jj]ob [Oo]pportunity/
>>
>>
On Dec 29, 2015, at 2:39 PM, Kevin A. McGrail wrote:
> On 12/29/2015 4:29 PM, Philip Prindeville wrote:
>> On Dec 29, 2015, at 2:14 PM, Kevin A. McGrail wrote:
>>
>>> On 12/29/2015 3:46 PM, Philip Prindeville wrote:
On Dec 29, 2015, at 1:42 PM, Kevin
On 12/29/2015 5:12 PM, Philip Prindeville wrote:
I did recall that I used the patch here:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6360#c4
to be able to debug my rules, using a rule that would match any non-empty subject:
value to dump out what it was (the “> got hit: “…””
On Dec 29, 2015, at 3:15 PM, Kevin A. McGrail wrote:
> On 12/29/2015 5:12 PM, Philip Prindeville wrote:
>> I did recall that I used the patch here:
>>
>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6360#c4
>>
>> to be able to debug my rules, using a rule that would
On 12/29/2015 5:16 PM, Philip Prindeville wrote:
On Dec 29, 2015, at 3:15 PM, Kevin A. McGrail > wrote:
On 12/29/2015 5:12 PM, Philip Prindeville wrote:
I did recall that I used the patch here:
Is there a reason that headers are left with leading spaces?
I’ve noticed that I have to write rules as:
Subject =~ /^ Great [Jj]ob [Oo]pportunity/
because of the leading space… Given the text of RFC-2822:
NO-WS-CTL = %d1-8 / ; US-ASCII control characters
On 12/29/2015 3:46 PM, Philip Prindeville wrote:
On Dec 29, 2015, at 1:42 PM, Kevin A. McGrail wrote:
On 12/29/2015 3:38 PM, Philip Prindeville wrote:
Is there a reason that headers are left with leading spaces?
I’ve noticed that I have to write rules as:
Subject =~ /^
On 12/29/2015 4:29 PM, Philip Prindeville wrote:
On Dec 29, 2015, at 2:14 PM, Kevin A. McGrail wrote:
On 12/29/2015 3:46 PM, Philip Prindeville wrote:
On Dec 29, 2015, at 1:42 PM, Kevin A. McGrail wrote:
On 12/29/2015 3:38 PM, Philip Prindeville
Am 29.12.2015 um 22:14 schrieb Kevin A. McGrail:
On 12/29/2015 3:46 PM, Philip Prindeville wrote:
On Dec 29, 2015, at 1:42 PM, Kevin A. McGrail wrote:
On 12/29/2015 3:38 PM, Philip Prindeville wrote:
Is there a reason that headers are left with leading spaces?
I’ve
On 12/29/2015 3:38 PM, Philip Prindeville wrote:
Is there a reason that headers are left with leading spaces?
I’ve noticed that I have to write rules as:
Subject =~ /^ Great [Jj]ob [Oo]pportunity/
because of the leading space…
I'm at a complete loss. I add plenty of Subject rules with no
Is there a reason that headers are left with leading spaces?
I’ve noticed that I have to write rules as:
Subject =~ /^ Great [Jj]ob [Oo]pportunity/
because of the leading space… Given the text of RFC-2822:
NO-WS-CTL = %d1-8 / ; US-ASCII control characters
Am 29.12.2015 um 21:38 schrieb Philip Prindeville:
Is there a reason that headers are left with leading spaces?
I’ve noticed that I have to write rules as:
Subject =~ /^ Great [Jj]ob [Oo]pportunity/
because of the leading space… Given the text of RFC-2822
no, we have a ton of subject and
14 matches
Mail list logo