Kevin W. Gagel wrote:
> - Original Message -
> From: mouss <[EMAIL PROTECTED]>
> To:
> Cc: users@spamassassin.apache.org
> Subject: Re: Duplicate header question
> Date: Tue, 04 Dec 2007 23:47:21 +0100
>
>
>> Kevin W. Gagel wrote:
>>
>>> - Original Message -
>>>
>>>
On Tuesday 04 December 2007 17:05:04 Johnson, S wrote:
> 554 5.6.0 Reject, is=26786-18 - Bad_Header: Duplicate header field:
> "Message-ID"
>
> This nondelivery report was generated by the program amavisd-new at host
> mail.maildomain.com. Our internal reference code for your message is
> 26786-1
- Original Message -
From: mouss <[EMAIL PROTECTED]>
To:
Cc: users@spamassassin.apache.org
Subject: Re: Duplicate header question
Date: Tue, 04 Dec 2007 23:47:21 +0100
>Kevin W. Gagel wrote:
>> - Original Message -
>>
>>> your amavisd-new is configured to reject mail with bad h
Kevin W. Gagel wrote:
> - Original Message -
>
>> your amavisd-new is configured to reject mail with bad headers. as you
>> see, this block legitimate mail.
>>
>> note that since your amavisd-new is sending bounces, you are a potential
>> backscatter source. do not bounce mail after it w
[EMAIL PROTECTED] wrote:
> Hi gurus,
>
> Recently, I've upgraded to spamassassin 3.2.0 called from amavisd-new.
> I've seen that this version is more agressive, and for example it
> detect as spam
> a legitimate email with next score:
>
> X-Spam-Status: Yes, score=4.884 tagged_above=-999 required=3
- Original Message -
>your amavisd-new is configured to reject mail with bad headers. as you
>see, this block legitimate mail.
>
>note that since your amavisd-new is sending bounces, you are a potential
>backscatter source. do not bounce mail after it was accepted by one of
>your servers. o
Johnson, S wrote:
> I just upgraded my Spamassassin/postfix/amavisd/sqlgrey to the current
> version and now have a few users from MSN and Yahoo reporting an error
> similar to this:
>
>
>
> 554 5.6.0 Reject, is=26786-18 - Bad_Header: Duplicate header field:
> "Message-ID"
>
> This nondelivery re
[EMAIL PROTECTED] wrote:
Hi gurus,
Recently, I've upgraded to spamassassin 3.2.0 called from amavisd-new.
I've seen that this version is more agressive, and for example it
detect as spam
a legitimate email with next score:
X-Spam-Status: Yes, score=4.884 tagged_above=-999 required=3.5
test
Hi gurus,
Recently, I've upgraded to spamassassin 3.2.0 called from amavisd-new.
I've seen that this version is more agressive, and for example it detect
as spam
a legitimate email with next score:
X-Spam-Status: Yes, score=4.884 tagged_above=-999 required=3.5
tests=[MIME_BASE64_TEXT=2.796,
At 08:05 AM 12/4/2007, Johnson, S wrote:
I just upgraded my
Spamassassin/postfix/amavisd/sqlgrey to the
current version and now have a few users from
MSN and Yahoo reporting an error similar to this:
554 5.6.0 Reject, is=26786-18 Bad_Header:
Duplicate header field: Message-ID
This nondel
I just upgraded my Spamassassin/postfix/amavisd/sqlgrey to the current
version and now have a few users from MSN and Yahoo reporting an error
similar to this:
554 5.6.0 Reject, is=26786-18 - Bad_Header: Duplicate header field:
"Message-ID"
This nondelivery report was generated by the program a
Okay thx for the help with my sa-update problem yesterday.
now i am a step further and get the next error .-)
Here is the Dump, error is at the end
[1722] dbg: logger: adding facilities: all
[1722] dbg: logger: logging level is DBG
[1722] dbg: generic: SpamAssassin version 3.2.3
[1722] dbg: co
Hi
> Thx so far. Yes thats it. Its our DNS on the Router. In all other cases it
> works fine but it don't like 3.2.3.updates.spamassassin.org.
> Can i somehow tell sa-update to use another (global) DNS Server?
Yes, you can. The first choice probably would be the DNS servers of your ISP.
However,
mozafar rowshan schrieb:
Hi friends!
I've installed SpamAssassin 3.2.3 in CentOS 5, now for testing
purposes. I've checked SA (spamc/d) and It works for package spam and non-spam
sample files.
As far as I remember, I did not play with SA settings, so the
configuration is default.
An
ram writes:
> Almost all of the phising mails I can see have
> (!__ENV_AND_HDR_FROM_MATCH)
>
> Can I simple give a high score to all mails whose header from and env
> from dont match
>
> I will have to whitelist all mailing lists , yahoogroups etc. But is
> there any other issue with this
it
Thx so far. Yes thats it. Its our DNS on the Router. In all other cases it
works fine but it don't like 3.2.3.updates.spamassassin.org.
Can i somehow tell sa-update to use another (global) DNS Server?
PS.: I've got the newest version of the updates because i manually built
the directories and cop
16 matches
Mail list logo
