         ....
|
Guardian Digital Inc. >
InfoCenter >
Mailing List Archives >
Amavis
Amavis Mailing List Archive
haha, old one. have you set @local_domains_maps? otherwise Recipient is not
considered local, spam-related header fields are only inserted for local recipients
also, with sendmail-milter it works in no way, never. is because of a
restriction in milter.
is in the FAQ somewhere
georg
Bill Landry wrote:
> Sorry to be replying to my own post, but I just realized that the bad part
> about this is that the "X-Spam-Status:" header is missing. If I test this
> with: "spamassassin -t < test.msg", the output includes:
> =====
> X-Spam-Prev-Subject: Message subject removed
> X-Spam-Flag: YES
> X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on
> mgw1.pointshare.com
> X-Spam-Level: *******************
> X-Spam-Status: Yes, score=20.0 required=6.0 tests=DCC_CHECK,DIGEST_MULTIPLE,
> FH_HAS_X_UIDL,PYZOR_CHECK,RANDOMWORDS_07,RAZOR2_CF_RANGE_51_100,
> RAZOR2_CHECK,SARE_MSGID_DBL_AT,X_MESSAGE_INFO autolearn=spam
> version=3.0.1
> X-Spam-Report:
> * 6.6 FH_HAS_X_UIDL FH_HAS_X_UIDL
> * 1.0 SARE_MSGID_DBL_AT Message ID has two at signs
> * 6.6 X_MESSAGE_INFO Found a X-Message-Info header
> * 0.5 RANDOMWORDS_07 BODY: string of 7+ random words
> * 1.5 RAZOR2_CF_RANGE_51_100 BODY: Razor2 gives confidence level
> above 50%
> * [cf: 100]
> * 0.1 RAZOR2_CHECK Listed in Razor2 (http://razor.sf.net/)
> * 2.0 PYZOR_CHECK Listed in Pyzor (http://pyzor.sf.net/)
> * 1.4 DCC_CHECK Listed in DCC (http://rhyolite.com/anti-spam/dcc/)
> * 0.2 DIGEST_MULTIPLE Message hits more than one network digest
> check
> =====
>
> However, it appears that this information is not getting included when
> amavisd-new writes its headers - the only amavisd-new message header added
> is the "X-Virus-Scanned:" header. Here are the amavis.log header entries at
> log_level 5:
> =====
> headers CLUSTERING: NEW CLUSTER <billing@healthknowledge.com>: hits=9.978,
> tag=0, tag2=0, subj=0, subj_u=0, local=0, bl=
> header: X-Virus-Scanned: by amavisd-new at mgw1.pointshare.com\n
> headers CLUSTERING: done all 1 recips in one go
> =====
>
> Here are my amavisd.conf SA entries:
> =====
> $sa_tag_level_deflt = undef; # add spam info headers if at, or above that
> level
> $sa_tag2_level_deflt = 6.0; # add 'spam detected' headers at that level
> $sa_kill_level_deflt = 6.0; # triggers spam evasive actions
> $sa_dsn_cutoff_level = undef; # spam level beyond which a DSN is not sent
> =====
>
> Since we will eventually migrating all of our RedHat 9 servers to Fedora
> Core 3, I would really like to get this resolved before making this
> migration. Ideas or suggestions?
>
> Thanks,
>
> Bill
> ----- Original Message -----
> From: "Bill Landry" <billl@pointshare.com>
> To: <amavis-user@lists.sourceforge.net>
> Sent: Monday, December 13, 2004 5:42 PM
> Subject: [AMaViS-user] Logging conundrum...
>
>
>
>>I've just setup a new Fedora Core 3 server with basically the same
>>configuration as a current RedHat 9 server, the only difference being the
>
> OS
>
>>and Perl version. Here are the configurations, and a snippet from each
>>amavisd.log file:
>>
>>=====
>>RedHat 9
>>Postfix 2.1.5
>>amavisd-new-2.2.0 (20041102)
>>SpamAssassin 3.0.1
>>Perl version 5.8.3
>>---log snippet:
>>LMTP::10024
>>Checking:
>>p001 1 Content-Type:
>>SPAM,
>>SPAM-TAG,
>>FWD via SMTP: [127.0.0.1]:10025
>>Passed SPAM,
>>TIMING
>>=====
>>Fedora Core 3
>>Postfix 2.1.5
>>amavisd-new-2.2.0 (20041102)
>>SpamAssassin 3.0.1
>>Perl version 5.8.5
>>---log snippet:
>>LMTP::10024
>>Checking:
>>p001 1 Content-Type:
>>SPAM,
>>FWD via SMTP: [127.0.0.1]:10025
>>Passed SPAM,
>>TIMING
>>=====
>>
>>I have copied the amavisd.conf file from the RedHat server to the Fedora
>>server and the only change made was to the "myhostname" entry. However, I
>>noticed that the log output (as shown about) is different in that the
>
> Fedora
>
>>logs do not include the "SPAM-TAG" entry. I had thought that this entry
>
> was
>
>>redundant anyway, but I am really curious as to why this is happening,
>
> since
>
>>the amavisd.conf files on both servers are basically identical. In fact,
>
> I
>
>>would like to suppress the "SPAM-TAG" entry on my RedHat servers, as well.
>>
>>Any ideas? Thanks!
>>
>>Bill
>>
>>
>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now.
>>http://productguide.itmanagersjournal.com/
>>_______________________________________________
>>AMaViS-user mailing list
>>AMaViS-user@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/amavis-user
>>AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
>>AMaViS-HowTos:http://www.amavis.org/howto/
>>
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> AMaViS-user mailing list
> AMaViS-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amavis-user
> AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
> AMaViS-HowTos:http://www.amavis.org/howto/
>
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
|
