Thanks for the follow-ups guys, its much appreciated. I'm building
and testing furiously :)
On Apr 11, 2006, at 6:05, Matt Kettler wrote:
Dan wrote:
Follow up question (even more odd than weight limits):
I want to flag all messages as spam, then configure various rules as
exceptions, ma
Dan wrote:
> Follow up question (even more odd than weight limits):
>
> I want to flag all messages as spam, then configure various rules as
> exceptions, marking them as ham. But how do I universally mark
> messages one way in SpamAssassin and then unmark them in the other?
>
> I realize this is
> I want to flag all messages as spam, then configure various rules as
> exceptions, marking them as ham. But how do I universally mark
> messages one way in SpamAssassin and then unmark them in the other?
>
> I realize this is unorthodox, but I would appreciate any suggestions.
>From experience
> So you're saying 307 integers and 15 decimals?:
307 total digits if you happen to have the decimal point on the right. The
first 15 of those will be non-zero, all the rest will be zero.
Or alternately 280+ leading zeros and 15 trailing digits if you go to the
right of the decimal point.
> The total range for the mantissa of a double-precision float is 52-bits,
with 1
> bit for sign. This means that the range between your most significant and
least
Minor quibble: the number of mantissa bits stored is 52, but as the mantissa
is assumed to be normalized except in some very special c
Dan wrote:
> Follow up question (even more odd than weight limits):
>
> I want to flag all messages as spam, then configure various rules as
> exceptions, marking them as ham. But how do I universally mark
> messages one way in SpamAssassin and then unmark them in the other?
>
> I realize this is
Follow up question (even more odd than weight limits):
I want to flag all messages as spam, then configure various rules as
exceptions, marking them as ham. But how do I universally mark
messages one way in SpamAssassin and then unmark them in the other?
I realize this is unorthodox, but I
No, I'm saying 15 digits. That's *total* combined between integer
and decimal
places.
However, because the floating point is stored in a scientific
notation, you can
add a bunch of extra zeros to push those 15 digits around.
So you can have:
(15 digits) + (307 zeros).0
or
0.(307 zeros) +
Dan wrote:
>> The total range for the mantissa of a double-precision float is
>> 52-bits, with 1
>> bit for sign. This means that the range between your most significant
>> and least
>> significant digit of the final summed answer cannot be greater than
>> 2^51, or
>> you'll loose precision.
>>
>>
The total range for the mantissa of a double-precision float is 52-
bits, with 1
bit for sign. This means that the range between your most
significant and least
significant digit of the final summed answer cannot be greater than
2^51, or
you'll loose precision.
The total range for the expone
Dan wrote:
> Good approach Herb, thanks
>
>
> To anyone:
>
> 1) What is the highest weight value (in number of digits) supported by
> SpamAssassin?
>
> 2) What is the smallest weigh value (in decimal places) supported by
> SpamAssassin?
In current practice, the range is 1000 to 0.0001. The cod
Good approach Herb, thanks
To anyone:
1) What is the highest weight value (in number of digits) supported
by SpamAssassin?
2) What is the smallest weigh value (in decimal places) supported by
SpamAssassin?
These might look like:
10
.01
Thanks,
Dan
Dan wrote:
> Thanks guys,
> > There isn't a lot of description of this because most people don't
> > want to
> > do this - most f the value of SA comes in the rules packaged with
> > it that
> > have been tested to hit current spam.
> Must be to many years of building legos, one brick at a ti
Thanks guys,
There isn't a lot of description of this because most people don't
want to
do this - most f the value of SA comes in the rules packaged with
it that
have been tested to hit current spam.
The main reason why you're finding little documentation about
"starting
from the groun
Dan wrote:
> Newbie here,
>
> I've filtered email for years with Declude and am adding SpamAssassin
> to my arsenal. I want to build something from scratch and am having
> problems getting started.
Before we get further: I'd really suggest starting off playing with SA's
default setup for a while,
There isn't a lot of description of this because most people don't want to
do this - most f the value of SA comes in the rules packaged with it that
have been tested to hit current spam.
That said, you probably these days need an init.pre to enable som plugins
and a local.cf with some minimal conf
Newbie here,
I've filtered email for years with Declude and am adding SpamAssassin
to my arsenal. I want to build something from scratch and am having
problems getting started. Thing is, all the guides (books, manual,
web pages) seem to be geared toward using the standard configuration
17 matches
Mail list logo
