On 02/16/2015 04:46 PM, Reindl Harald wrote:

Am 16.02.2015 um 16:40 schrieb rsmits-l:
On 02/16/2015 04:17 PM, Reindl Harald wrote:

Am 16.02.2015 um 16:09 schrieb rsmits-l:
Also some information. We use an ipv6 --> ipv4 converter.
(ipv6-mx.tudelft.nl [130.161.6.14]

This is not part of our trusted network because we do not have an ipv6
spamchecker in place

than you likely know the reason

SpamAssassin needs to know what hosts are your "trusted_network" and "
internal_networks" to know which is the LASTEXT to fire RBL requests
against

No, i still don't understand. See below :

--------------------------
Received: from emea01-am1-obe.outbound.protection.outlook.com
(ipv6-mx.tudelft.nl [130.161.6.14]) by mailhost2.tudelft.nl
---
Received: from eraora (151.66.59.47) by
AMSPR06MB248.eurprd06.prod.outlook.com
--------------------------

eraora (151.66.59.47) = Foreign user
AMSPR06MB248.eurprd06.prod.outlook.com = Office365 server

then to --> emea01-am1-obe.outbound.protection.outlook.com and that one
delivers it to our mailserver through the ipv6 gateway.

The PBL should only fire when the foreign user submits the E-Mail
directly to our mailserver. This is why the Spamhaus PBL was made. The
IP addresses on this list should use a mailrelay server from their
provider. This one uses AMSPR06MB248.eurprd06.prod.outlook.com. So this
is still no explanation why the PBL is firing?

it does as long "trusted_network" and "internal_networks" are configured
correctly and amavis in your setup is also part of the game you need to
be even more careful with your configuration and make sure whatever
config file you edit is *really* in use

Hello,

WHY don't you add "130.161.6.14" to "trusted_network" and
"internal_networks" and look if it works after that as expected instead
continue to argue?


I have started with this setup in the beginning, but the problem I was facing then is that Amavisd doet not do a spamcheck on the E-Mail because the foreign mailserver is part of our trusted network. Our setup with the ipv6 to ipv4 converter may be the problem. 130.161.6.14 should really be not on the trusted network.

I am going to shutdown the ipv6 converter and look if the PBL rule still fires.

Greetings...

Reply via email to