-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter writes:
> On Mon, Jan 10, 2005 at 12:07:39PM -0500, Matt Kettler wrote:
> > It's not tagged because there's no subject header to be tagged. This is a
> > bug in SA 3.0.0 and 3.0.1, but was fixed in SA 3.0.2.
>
> Just because it annoy
On Mon, Jan 10, 2005 at 12:07:39PM -0500, Matt Kettler wrote:
>
> It's not tagged because there's no subject header to be tagged. This is a
> bug in SA 3.0.0 and 3.0.1, but was fixed in SA 3.0.2.
>
> http://bugzilla.spamassassin.org/show_bug.cgi?id=3816
>
To be fair. This was not a bug, but a
On Mon, Jan 10, 2005 at 12:07:39PM -0500, Matt Kettler wrote:
> It's not tagged because there's no subject header to be tagged. This is a
> bug in SA 3.0.0 and 3.0.1, but was fixed in SA 3.0.2.
Just because it annoys me -- this was not a bug. It worked exactly
as it was designed to. However, en
At 10:50 AM 1/10/2005, Damien Kemens - Equinox Development wrote:
I seem to be having a problem that defies SA logic, so there
must be another variable Im not aware of. A message comes through our
network for Undisclosed Recipients. Here are the related headers:
>X-Spam-Checker-Vers
Hi,
I
seem to be having a problem that defies SA logic, so there must be another
variable I’m not aware of. A message comes through our network for
Undisclosed Recipients. Here are the related headers:
>X-Spam-Checker-Version:
SpamAssassin 3.0.0 (2004-09-13) on eq-gw2.ly.ne
