Axigen-SpamLevel ???

Siehe hier:

http://www.axigenmailgate.de/f…-kein-spam-doch-spam.html

Zusammengefasst, der Spamscore ist nicht der, den SpamAssassin gewertet hat, Sie haben wohl noch einen anderen aktiviert.

Zur genauen Implementierung kann ich leider nicht viel sagen - die kenne ich nicht.

Der grobe Ablauf ist so, dass AXIGEN die Mail an den SpamAssassin übergibt und dann auf eine Rückmeldung wartet und dies wird dann (wohl mit einem Faktor) als Spamlevel umgesetzt.

Das Ergebnis, das SpamAssassin liefert, gilt. Das kann aber (wenn man mehrere weitere Filter hat, wie Bayes, Wordlists, usw.) unterschiedlich dem sein, was SpamAssassin dann am Ende in den Logs abliefert.

Deaktivieren Sie bitte mal den Filter, den Sie für aktiv halten und schauen sich dann den Spamscore an, ob es noch einen gibt.

Aber die Details können Sie oder wir gerne mit dem Hersteller klären, der kennt die genaue Implementierung - support (bei) axigen.com. Es kann gut sein, dass SpamAssassin und AXIGEN (versionsabhängig?) nicht miteinander harmonieren.

Auch hier noch einmal die Antwort die Entwickler, inklusive der Formel, wie das berechnet wird:

Zitat

Please do not try to correlate the values given by Spamassassin to
the same scale as the Axigen Spam level. The current formula ensures
that the values between the two different scales are properly
translated. Please also consult the related Spamassassin documentation
in order to understand the SA scores:

SpamAssassin: Tests Performed: v3.2.x

Please note that the 0.4 value is not obtained relevant to a scale from
0 to 5 in SA, but in fact the 5 score only means the threshold from
which SA will consider the message as being spam. Also the obtained
X-AxigenSpam-Level of 5 is not a high spam score and should not be
regarded in relation to the Spamassassin required score of 5, as they
are on totally different scales.

As such we do not advise in modifying the current settings unless you
are experiencing issues with the scan results.

However if you require the lowering of spam scores (in relation to the
SA score) we note again that there are two sets of spam
scores/thresholds involved when scanning a message with SpamAssassin:
- the true SpamAssassin score, together with the required_score
- the Axigen score (written in the X-AxigenSpam-Level header),
together with the Axigen Spam thresholds

These score and threshold sets are different (but related) and should
not be confused.

The Axigen score (X-AxigenSpam-Level) is calculated based on the true
SpamAssassin score and required_score, using the following formula:

X-AxigenSpam-Level = { ($1+$2) / [(2*$2)/9] } + 1

where:
$1 = the true SpamAssassin score
$2 = the required_score value you set in local.cf

By increasing the required_score from 5.0 to 7.5, X-AxigenSpam-Level
will start having lower values for each message. When X-AxigenSpam-Level
is lower than or equal to the Spam threshold you set in Axigen Webadmin,
the message is delivered into Inbox.

In order to modify the threshold (for SpamassassinBundled - if you are
using a separate install of Spamassassin please modify the below paths
for the configuration file accordingly), please follow these steps:
1) open the mentioned file (/etc/opt/axigen/spamassassin/conf/local.cf)
in a text editor
2) locate the following section:

# Set the threshold at which a message is considered spam (default:
5.0)
#
# required_score 5.0

3) here, you will need to uncomment (remove the leading '#') and modify
the required_score line. We suggest starting with a basic threshold
score of 7.5. The resulting section should resemble the following:

# Set the threshold at which a message is considered spam (default:
5.0)
#
required_score 7.5

Note that the required_score line now has the leading # removed.

4) save the changes
5) restart SpamAssassinBundeld by issuing the following command:
/etc/init.d/axigenfilters restart
NOTE: If you are using a separate install of Spamassassin restart the
corresponding spamd process.

By increasing the required_score from 5.0 to 7.5, X-AxigenSpam-Level
will start having lower values for each message. When X-AxigenSpam-Level
is lower than or equal to the Spam threshold you set in Axigen Webadmin,
the message is delivered into Inbox.

By observing the amount of legitimate messages delivered into Spam
versus Spam messages delivered into Inbox, you should be able to decide
if it is necessary to apply any further corrections to the
required_score value in local.cf.

Alles anzeigen