On 2/16/2015 10:09 AM, rsmits-l wrote:
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. Our amavisd config reads :
@mynetworks = qw ( 127.0.0.0/8 !130.161.6.14/32 130.161.0.0/16
131.180.0.0/16 192.87.166.0/24 10.200.12.0/24 10.200.20.0/24 );
So reading the received headers in reverse order:
*Exempted from trusted network:*
Received: from mailhost2.tudelft.nl ([127.0.0.1])
by localhost (tudelft.nl [127.0.0.1]) (amavisd-new, port 10026)
with ESMTP id Y8TTFFqyl0bj for <u...@mailboxcluster.tudelft.net>;
Fri, 13 Feb 2015 12:18:49 +0100 (CET)
*Exempted from trusted network??: Since this hits on your exact
inclusion/exclusion*, does amavisd support the same syntax for
mynetworks that spamassassin does? According to what I read, it uses
Postfix's syntax which is
http://www.postfix.org/postconf.5.html#mynetworks. I tested with SA and
the syntax you have works for SA for trunk at least. Anyway, this is
where I would focus my attention since it's what leads to that IP as the
external received header:
Received: from emea01-am1-obe.outbound.protection.outlook.com
(ipv6-mx.tudelft.nl [130.161.6.14])
by mailhost2.tudelft.nl (Postfix) with ESMTP id 7E01A46003E
for <u...@student.tudelft.nl>; Fri, 13 Feb 2015 12:18:49 +0100
(CET)
*This then becomes the first external header...*
Received: from eraora (151.66.59.47) by
AMSPR06MB248.eurprd06.prod.outlook.com
(10.242.95.24) with Microsoft SMTP Server (TLS) id 15.1.87.18; Fri, 13 Feb
2015 11:18:42 +0000
Regards,
KAM
