On 02/16/2015 06:21 PM, RW wrote:
On Mon, 16 Feb 2015 16:40:53 +0100
rsmits-l wrote:
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 tr
On Mon, 16 Feb 2015 16:40:53 +0100
rsmits-l wrote:
> 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 networ
Am 16.02.2015 um 18:03 schrieb Benny Pedersen:
On 16. feb. 2015 16.11.14 rsmits-l wrote:
Also some information. We use an ipv6 --> ipv4 converter.
(ipv6-mx.tudelft.nl [130.161.6.14]
put this ip in trusted_networks in sa, if it forwards mails to amavisd
This is not part of our trusted net
On 16. feb. 2015 16.42.57 "Kevin A. McGrail" wrote:
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 +
missing in msa_networks ?
On 2/16/2015 12:03 PM, Benny Pedersen wrote:
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 );
same ips added to spamassassin ?
Good question as I have no real-world experience with amavisd
On 16. feb. 2015 16.11.14 rsmits-l wrote:
Also some information. We use an ipv6 --> ipv4 converter.
(ipv6-mx.tudelft.nl [130.161.6.14]
put this ip in trusted_networks in sa, if it forwards mails to amavisd
This is not part of our trusted network because we do not have an ipv6
spamchecker in
On 16. feb. 2015 16.02.26 rsmits-l wrote:
A late reply, but this week I started investigating why this happens. I
have edited a sample. If someone can take a look why the PBL is firing
here is would be great.
http://pastebin.com/xxFAPTay
10 RCVD_IN_PBLRBL: Received via a rela
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 tr
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
s
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.16
On 02/16/2015 04:15 PM, Kevin A. McGrail wrote:
On 2/16/2015 10:01 AM, rsmits-l wrote:
On 02/09/2015 01:53 PM, Kevin A. McGrail wrote:
On 2/9/2015 7:43 AM, rsmits-l wrote:
I have been reading some threads on the Internet about problems with
the field "X-Originating-IP" and the Spamhaus PBL lis
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
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 ho
On 2/16/2015 10:01 AM, rsmits-l wrote:
On 02/09/2015 01:53 PM, Kevin A. McGrail wrote:
On 2/9/2015 7:43 AM, rsmits-l wrote:
I have been reading some threads on the Internet about problems with
the field "X-Originating-IP" and the Spamhaus PBL list. We are also
having this problem. I have instal
On 02/16/2015 04:01 PM, rsmits-l wrote:
On 02/09/2015 01:53 PM, Kevin A. McGrail wrote:
On 2/9/2015 7:43 AM, rsmits-l wrote:
I have been reading some threads on the Internet about problems with
the field "X-Originating-IP" and the Spamhaus PBL list. We are also
having this problem. I have insta
On 02/09/2015 01:53 PM, Kevin A. McGrail wrote:
On 2/9/2015 7:43 AM, rsmits-l wrote:
I have been reading some threads on the Internet about problems with
the field "X-Originating-IP" and the Spamhaus PBL list. We are also
having this problem. I have installed a workaround for this but is not
wor
On 09.02.15 13:49, Reindl Harald wrote:
X-Originating-IP is a header which *for sure* must not be fired
against RBL's as any other remote header since they are untrustable
It *can* be *for sure* checked. It just must not be checked for
_negative-scoring_ lists cause that would cause FNs, but if
rsmits-l skrev den 2015-02-09 13:43:
I am wondering if there is a permanent solution for this ? I am
running : SpamAssassin version 3.3.1
running on Perl version 5.10.1
amavisd-new : amavisd-new-2.8.0 (20120630)
sendmail mta ?, or postfix ?, if later make sure postfix use
xforward/xclient, so
On 2/9/2015 7:43 AM, rsmits-l wrote:
I have been reading some threads on the Internet about problems with
the field "X-Originating-IP" and the Spamhaus PBL list. We are also
having this problem. I have installed a workaround for this but is not
working bulletproof.
I am wondering if there is
X-Originating-IP is a header which *for sure* must not be fired against
RBL's as any other remote header since they are untrustable
i fear you need to describe the evidence of whatever problem
Am 09.02.2015 um 13:43 schrieb rsmits-l:
I have been reading some threads on the Internet about probl
Hello,
I have been reading some threads on the Internet about problems with the
field "X-Originating-IP" and the Spamhaus PBL list. We are also having
this problem. I have installed a workaround for this but is not working
bulletproof.
I am wondering if there is a permanent solution for this
21 matches
Mail list logo
