-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Mason wrote:
> there's a rule that matches them in 3.1.x sa-update, fwiw.
>
>
Really? Mine is up to date & they still get through...
One thing I've noticed is the envelope return path... Watching this
morning, they all seem to be from 'debora@
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nigel Frankcom wrote:
> I'm not sure what you've done there, I didn't realise it was
> possible to mix collation types in the same table. Have you checked
> that all tables are the same type? MyISAM or Inno? If they are all
> the same, I'd be inclined
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nigel Frankcom wrote:
> I'm not sure what you've done there, I didn't realise it was
> possible to mix collation types in the same table. Have you checked
> that all tables are the same type? MyISAM or Inno? If they are all
> the same, I'd be inclined
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I keep getting the following from spamassasin (Running under amavisd
debug-sa). Any ideas what I've done wrong this time?
The database is mysql. SpamAssassin is 3.1.4 (It also did the same
with 3.1.3).
[12172] dbg: bayes: database connection establi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Hill wrote:
> On Monday 07 August 2006 00:02, wrote:
>> | 2250 0733.com
>
>> Here are my numbers from last week:
>>
>> 5006 0451.com 3845 53.com
>
> Not seeing anywhere near as high, but this is only on my personal
> server: 440733.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gino Cerullo wrote:
>
> On 27-Jul-06, at 4:32 PM, Hamish wrote:
>
>> On Wednesday 26 July 2006 17:25, Marc Perkel wrote:
>>> Benny Pedersen wrote:
On Tue, July 25, 2006 18:51, Marc Perkel wrote:
> SPF breaks email forwarding. My users use forw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John D. Hardin wrote:
> On Thu, 27 Jul 2006, Hamish wrote:
>
>> Forwarding should (IMO) be implemented in such a way as the
>> FORWARDING mailbox should be used as the new return-path (Just
>> like if you forwarded an email from your MUA rather than wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hamish Marson wrote:
> Loren Wilton wrote:
>>>> Yeah, I know about the SPF checks... But I meant does SA
>>>> currently do anything with digital signatures to verify that
>>>> the sender really is the sender &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton wrote:
>> Yeah, I know about the SPF checks... But I meant does SA
>> currently do anything with digital signatures to verify that the
>> sender really is the sender & apply a -ve score.
>
> Other than the SPF type header checks I don't be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Mason wrote:
> Hamish Marson writes:
>> Justin Mason wrote:
>>> Hamish writes:
>>>> On Wednesday 28 June 2006 08:48, Ralf Hildebrandt wrote:
>>>>> * [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Mason wrote:
> Hamish writes:
>> On Wednesday 28 June 2006 08:48, Ralf Hildebrandt wrote:
>>> * [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Given that airline messages are important, are related to
meney, and recipients dont want to get for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm having a wee problem with load orders of config files & plugins on
SA3.1.1.
After updating from 3.0.4 to 3.1.0 and then trying also 3.1.1 I've
found that the config files get loaded before the plugins. This
wouldn't normally be a problem except th
On Tue, 2006-02-28 at 16:51 -0800, jdow wrote:
> From: "Hamish Marson" <[EMAIL PROTECTED]>
>
> > On Tue, 2006-02-28 at 17:55 +, Hamish Marson wrote:
> >> I have a problem... Got aload of complaints about emails not coming
> >> through. On inves
On Tue, 2006-02-28 at 17:55 +, Hamish Marson wrote:
> I have a problem... Got aload of complaints about emails not coming
> through. On investigating, I have discovered that we're getting rules
> such as MISSING_SUBJECT hit, where an email clearly has a subject: line
> in
I have a problem... Got aload of complaints about emails not coming
through. On investigating, I have discovered that we're getting rules
such as MISSING_SUBJECT hit, where an email clearly has a subject: line
in the headers. Also missing recieved header, no from_or_to etc..
So I can spamassassin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I'm having continuing (& getting worse) false positives with japanese
emails... There are lots of SARE hits for them, but I'm also getting
stuff like OBSCURED_EMAIL which the test page says is "Message seems
to contain rot13ed address", but it's j
16 matches
Mail list logo
