Am 30.09.2011 17:11, schrieb Robert Schetterer: > Hi , > > i have i.e. > warning: Unable to look up MX host mailin.v6.t-online.de > this seems ok, cause we dont have any ip4 con yet > also using > > smtp_address_preference = ipv4 > inet_protocols = ipv4 > > > dig -t mx t-online.de > > ; <<>> DiG 9.7.0-P1 <<>> -t mx t-online.de > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17919 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 4, ADDITIONAL: 11 > > ;; QUESTION SECTION: > ;t-online.de. IN MX > > ;; ANSWER SECTION: > t-online.de. 3531 IN MX 10 mx03.t-online.de. > t-online.de. 3531 IN MX 10 mailin.v6.t-online.de. > t-online.de. 3531 IN MX 10 mx00.t-online.de. > t-online.de. 3531 IN MX 10 mx01.t-online.de. > t-online.de. 3531 IN MX 10 mx02.t-online.de. > > ;; AUTHORITY SECTION: > t-online.de. 75270 IN NS dns00.btx.dtag.de. > t-online.de. 75270 IN NS dns02.btx.dtag.de. > t-online.de. 75270 IN NS dns50.t-ipnet.de. > t-online.de. 75270 IN NS pns.dtag.de. > > ;; ADDITIONAL SECTION: > mx00.t-online.de. 83214 IN A 194.25.134.8 > mx01.t-online.de. 83214 IN A 194.25.134.72 > mx02.t-online.de. 83214 IN A 194.25.134.9 > mx03.t-online.de. 83214 IN A 194.25.134.73 > mailin.v6.t-online.de. 75270 IN AAAA 2003:2:2:10:fee::32 > mailin.v6.t-online.de. 75270 IN AAAA 2003:2:2:10:fee::33 > > > i guess the warning is based by lookup done for using i.e > check_sender_mx_access cidr:/etc/postfix/bogon_networks.cidr > > .0.0.0/8 REJECT IP address of MX host is a bogus address > 127.0.0.0/8 REJECT IP address of MX host is a loopback address > 224.0.0.0/12 REJECT IP address of MX host is a multicast address > 255.0.0.0/8 REJECT IP address of MX host is a bogus address > 10.0.0.0/8 REJECT IP address of MX host is a RFC1918 address > 169.254.0.0/16 REJECT IP address of MX host is a RFC1918 address > 192.0.2.0/24 REJECT IP address of MX host is a RFC1918 address > 240.0.0.0/12 REJECT IP address of MX host is a reserved address > > is there a way to get out of the log warning.. > or should i simply ignore this ? > mails pass in anyway >
answering myself perhaps it could be done with i.e a check_client_access pcre table matching all ip6 adresses OK before using check_sender_mx_access it should work ( i have no idea what the pcre must look like ) but seems too lot, only in avoiding warnings but however i could match the ipv6 host itself with DUNNO, i guess, but in future , there may rise more ipv6 hosts, whitelisting each makes no sense, so a match all solution might be better anyone comments? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
