Steve Bertrand writes:
I've added debugging code to new_dns_packet() and bgsend()
(DnsResolver.pm) to print out $host, $type and $class to a log file.
What I found is that the mapped address entries are not even seen by
DnsResolver.pm at all, hence, there is no DNS lookup even attempted
SpamAssassin doesn't perform DNS lookups on the Received headers if
at all possible -- it's assumed that your MTA will do that in advance.
Thanks for that. I found this out late last night, and I believe I've
got the issue resolved.
Regards,
Steve
Greg Troxel wrote:
In my SA stats, the majority (+90%) of email inbound is classified as
rdns_none.
I have a suspicion that this is due to the IPv6-IPv4 mapped address
being written into the headers when I am speaking to a non-native IPv6
MTA:
Received: from unknown (HELO
Received: from unknown (HELO mail.apache.org) (:::140.211.11.2)
by pearl.ibctech.ca with SMTP; 28 May 2008 09:13:00 -
Can someone inform me if this is an SA thing, and if so, where to
begin looking/testing with the source to correct this issue?
The Received headers are parsed in
Hmmm...just out of curiosity, what is the first entry below used for, if
Resolver.pm is used for header checks?
pearl# locate Resolver.pm
/usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/DnsResolver.pm
/usr/local/lib/perl5/site_perl/5.8.8/mach/Net/DNS/Resolver.pm
...nevermind, sorry
I've added debugging code to new_dns_packet() and bgsend()
(DnsResolver.pm) to print out $host, $type and $class to a log file.
What I found is that the mapped address entries are not even seen by
DnsResolver.pm at all, hence, there is no DNS lookup even attempted on them.
I'm off to find
Steve Bertrand wrote:
I've added debugging code to new_dns_packet() and bgsend()
(DnsResolver.pm) to print out $host, $type and $class to a log file.
What I found is that the mapped address entries are not even seen by
DnsResolver.pm at all, hence, there is no DNS lookup even attempted on
First, I would advise you not to use mapped addresses unless you really
need to use them. On BSD, there's a sysctl to control whether v4
connections will match v6 sockets:
net.inet6.ip6.v6only = 1
Best practice seems to be to have daemons open a v4 and v6 socket
separately, and avoid mapped
Hi everyone,
This may not be the appropriate list, but I'm hoping someone can help me.
I have an email server based on Matt Simerson's mail toaster
(http://www.tnpi.biz/internet/mail/toaster/) that I've managed to get
IPv6 compliant.
However, I'm having a very hard time determining exactly
Hi Steve,
At 06:28 28-05-2008, Steve Bertrand wrote:
This may not be the appropriate list, but I'm hoping someone can help me.
It is the appropriate list.
I have an email server based on Matt Simerson's mail toaster
(http://www.tnpi.biz/internet/mail/toaster/) that I've managed to
get IPv6
In my SA stats, the majority (+90%) of email inbound is classified as
rdns_none.
I have a suspicion that this is due to the IPv6-IPv4 mapped address
being written into the headers when I am speaking to a non-native IPv6
MTA:
Received: from unknown (HELO mail.apache.org)
Greg Troxel wrote:
In my SA stats, the majority (+90%) of email inbound is classified as
rdns_none.
(I presume you are trying to make this server IPv6 only instead of dual
stack. When my machine had a globally routable v6 address I got some
mail over v6 and some over v4, but didn't used
12 matches
Mail list logo
