|
lowest mx ipv6 only bad idea
![[dk]](/s/countries/dk.gif) Shadow Hawkins on Sunday, 14 November 2010 01:00:46
I had my lowest mx a ipv6-only adress only, but then one of my mails was delayed:
status=deferred (host jupiter.wyenet.net[195.171.90.8] said: 472 xxx@neland.dk no DNS A-data returned (in reply to MAIL FROM command))
It seems jupiter.wyenet.net does not understand that my first mx-record does not return a A-record, only a AAAA-record.
So I remove that MX, and hope my mail gets out before it is too late; there is probably noone reading mail at sunday anyway.
lowest mx ipv6 only bad idea
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Wednesday, 17 November 2010 12:36:47
I have seen some mail bounce because of this. But I'm not going to fix other people's faulty configuration. What's next, bouncing because the mail headers say "Received: from 6filter.openoffice.nl (6filter.openoffice.nl [IPv6:2a01:4f8:100:50c1::a5])" ?
lowest mx ipv6 only bad idea
Shadow Hawkins on Wednesday, 17 November 2010 23:59:47
Well, I could get the same result of getting my mail delivered by ipv6 if available, by giving the mailserver both an AAAA and an A.
And by changing my mx, the mail got delivered, rather important concidering the sender was my SO :-)
Leif
lowest mx ipv6 only bad idea
![[no]](/s/countries/no.gif) Shadow Hawkins on Wednesday, 29 December 2010 00:34:52
I have deliberatly set up some of my e-mail addresses with a 6-only lowest mx.
A well known isp makes its e-mail server dump core when this happens. They must fix that.
But one side effect is that I get a LOT less spam.
|
Posting is only allowed when you are