On 12/5/2014 1:19 PM, Gibbs, David wrote:
On 12/5/2014 11:25 AM, John Hardin wrote:
FWIW: here's the rule I came up with ... seems to work adequately.
header __COUNT_SUBJ Subject =~ /.*/
You might want to be a little bit more paranoid and explicitly anchor
that:
header __COUNT_SUBJ Subj
On 12/5/2014 11:25 AM, John Hardin wrote:
FWIW: here's the rule I came up with ... seems to work adequately.
header __COUNT_SUBJ Subject =~ /.*/
You might want to be a little bit more paranoid and explicitly anchor that:
header __COUNT_SUBJ Subject =~ /^.*$/
I know .* is greedy and should
On Fri, 5 Dec 2014, Gibbs, David wrote:
On 12/4/2014 10:22 AM, Gibbs, David wrote:
I've seen a number of spam messages come through with multiple header
lines ... some of them are blank.
Any suggestions for a rule to trap this?
FWIW: here's the rule I came up with ... seems to work adequa
On 12/4/2014 10:22 AM, Gibbs, David wrote:
I've seen a number of spam messages come through with multiple header
lines ... some of them are blank.
Any suggestions for a rule to trap this?
FWIW: here's the rule I came up with ... seems to work adequately.
header __COUNT_SUBJ Subject =~ /.*/
tf
> I've seen a number of spam messages come through with multiple header
> lines ... some of them are blank.
>
> Subject:
>
> =?ISO-8859-1?Q?=20The=20Hotte?==?ISO-8859-1?Q?st=20Sm?==?ISO-8859-1?Q?ar?==?ISO-8859-1?Q?tpho?==?ISO
Folks:
I've seen a number of spam messages come through with multiple header lines ...
some of them are blank.
Subject:
=?ISO-8859-1?Q?=20The=20Hotte?