• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

spamassassin_psa dynamic IP and RBL`s

OliverG

New Pleskian
I have the following problem with false positive spams.

I send a mail with a dynamic IP over STMP Port 25 to mailserver 1.
Mailserver 1 delivers the mail to the receipient on mailserver 2.
Mailserver 2 marks the mail als spam.

The Header-Code:
-----------------------------------------------------------------------------
Received: (qmail 13819 invoked from network); 18 Jan 2011 14:39:52 +0100
Received-SPF: none (no valid SPF record)
Received: from mailserver1.domain.tld (87.230.xx.xx)
by mailserver2.domain.tld with (DHE-RSA-AES256-SHA encrypted) SMTP; 18 Jan 2011 14:39:51 +0100
Received: (qmail 9777 invoked from network); 18 Jan 2011 14:39:51 +0100
Received: from tmo-104-162.customers.d1-online.com (HELO ?10.210.142.130?) (80.187.104.162)
by mailserver1.domain.tld with SMTP; 18 Jan 2011 14:39:51 +0100
-----------------------------------------------------------------------------

The spamassassin result:
-----------------------------------------------------------------------------
3.0 NIX_SPAM RBL: Listed in NIX_SPAM DNSBL (thanks to heise.de)
[80.187.104.162 listed in ix.dnsbl.manitu.net]
2.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?80.187.104.162>]
2.5 RCVD_IN_PSBL RBL: Sender is listed in PSBL
[80.187.104.162 listed in psbl.surriel.com]
-0.2 AWL AWL: From: address is in the auto white-list
-----------------------------------------------------------------------------

The mail is sent from the dynamic IP 80.187.104.162 and scanned by spamassassin.
How can I reach that only the last IP from the "received from headers" will be scanned?

Thanks

Olli
 
it simply - just edit spamassassin rule(s), usually it in /usr/share/spamassassin ;)
 
Back
Top