>> >> I've upgraded from 3.2.1 to 3.2.5 on gentoo. It appears that dcc is
>> >> broken. My messages no longer get the dcc header:
>> >
>> > First, did you know that 3.3.1 was released? Otherwise, why stop at 3.2.5?
>
> On 04.07.10 07:24, Robert S wrote:
>> 3.3.1 is still marked as "unstable" by g
> >> I've upgraded from 3.2.1 to 3.2.5 on gentoo. It appears that dcc is
> >> broken. My messages no longer get the dcc header:
> >
> > First, did you know that 3.3.1 was released? Otherwise, why stop at 3.2.5?
On 04.07.10 07:24, Robert S wrote:
> 3.3.1 is still marked as "unstable" by gentoo.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/3/10 4:24 PM, Robert S wrote:
> 3.3.1 is still marked as "unstable" by gentoo. I've downgraded back
seriously? I'd take "unstable" over "obsolete" when it comes to
anti-spam and anti-virus tools.
- --
David Morton
Morton Software & Desig
On lør 03 jul 2010 23:24:55 CEST, Robert S wrote
I have a feeling that the /etc/spamassassin/*.pre files are not being
read. A lot of other plugins aren't being read.
Maybe I should (have) put this on gentoo bugzilla.
spamassassin 2>&1 -D --lint | less
--
xpoint http://www.unicom.com/pw/reply
>> I've upgraded from 3.2.1 to 3.2.5 on gentoo. It appears that dcc is
>> broken. My messages no longer get the dcc header:
>
> First, did you know that 3.3.1 was released? Otherwise, why stop at 3.2.5?
>
3.3.1 is still marked as "unstable" by gentoo. I've downgraded back
to 3.2.1 (which was wo
Hi,
> I've upgraded from 3.2.1 to 3.2.5 on gentoo. It appears that dcc is
> broken. My messages no longer get the dcc header:
First, did you know that 3.3.1 was released? Otherwise, why stop at 3.2.5?
Also, it's a national holiday weekend in the US (and in CA?), so it's
likely to be slower on
I've upgraded from 3.2.1 to 3.2.5 on gentoo. It appears that dcc is
broken. My messages no longer get the dcc header:
was: X-Spam-DCC: x.dcc-servers: hostname 104; Body=1 Fuz1=1 Fuz2=1
now: X-Spam-DCC: _DCCB_: _DCCR_
my init.pre contains (and has always contained) the following:
use_dcc
