SOLVED IPv6 enabled sendmail does not send to domains with IPv4 only MX which results in “config error:...
I encountered a strange problem after enabling IPv6 on my sendmail. BTW, reverse resolution is fine for my domain A and AAAA wise.
Sending mail to a domain with MX A and AAAA records switched now from IPv4 to IPv6. e.g with gmail:
sm-mta[42339]: wBE9nxJl042337: to=<example@gmail.com>, ctladdr=<user@myserver> (1001/1001), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30389, relay=gmail-smtp-in.l.google.com. [IPv6:2a00:1450:400c:c06:0:0:0:1b], dsn=2.0.0, stat=Sent
but sending mail to a domain with only MX A records does not take that IPv4 address for the relay but replaces it with my own servers IPv6 address which results in the "config error: mail loops back to me (MX problem?)" error.
e.g. with gmx.net:
sm-mta[42369]: wBE9oqO5042367: to=<example@gmx.net>, ctladdr=<user@myserver> (1001/1001), delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=30390, relay=mx00.emig.gmx.net. [IPv6:myservers_IPv6_Address!!!here should be the IPv4 address of the mx00.emig.gmx.net!!!], dsn=5.3.5, stat=Local configuration error
which furthermore leads to the "loops back to me" error.
That's what I added to sendmail.mc:
DAEMON_OPTIONS(`Name=MTA-v6, Family=inet6')
How can a IPv4 and IPv6 enabled sendmail communicate with IPv4 only MX of a foreign domain? Why doesn't it resolve the MX's IPv4 address but instead uses it's own IPv6 address? DNS resolv works fine.
sendmail
asked Dec 14 '18 at 10:43
ThorstenThorsten
11
add a comment |
I encountered a strange problem after enabling IPv6 on my sendmail. BTW, reverse resolution is fine for my domain A and AAAA wise.
Sending mail to a domain with MX A and AAAA records switched now from IPv4 to IPv6. e.g with gmail:
sm-mta[42339]: wBE9nxJl042337: to=<example@gmail.com>, ctladdr=<user@myserver> (1001/1001), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30389, relay=gmail-smtp-in.l.google.com. [IPv6:2a00:1450:400c:c06:0:0:0:1b], dsn=2.0.0, stat=Sent
but sending mail to a domain with only MX A records does not take that IPv4 address for the relay but replaces it with my own servers IPv6 address which results in the "config error: mail loops back to me (MX problem?)" error.
e.g. with gmx.net:
sm-mta[42369]: wBE9oqO5042367: to=<example@gmx.net>, ctladdr=<user@myserver> (1001/1001), delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=30390, relay=mx00.emig.gmx.net. [IPv6:myservers_IPv6_Address!!!here should be the IPv4 address of the mx00.emig.gmx.net!!!], dsn=5.3.5, stat=Local configuration error
which furthermore leads to the "loops back to me" error.
That's what I added to sendmail.mc:
DAEMON_OPTIONS(`Name=MTA-v6, Family=inet6')
How can a IPv4 and IPv6 enabled sendmail communicate with IPv4 only MX of a foreign domain? Why doesn't it resolve the MX's IPv4 address but instead uses it's own IPv6 address? DNS resolv works fine.
sendmail
asked Dec 14 '18 at 10:43
ThorstenThorsten
11
Is this specific to sendmail, or do you get the same output from other software, e.g.getent ahostsv6 ipv4only.arpaorgetent ahostsv6 mx00.emig.gmx.net?
– grawity
Dec 14 '18 at 12:21
Thanks for the hint. Yes, it seems not to be sendmail related. It generates an IPv6 record like mx00.emig.gmx.net.myown.domain although mx00.emig.gmx.net does not have an AAAA DNS record. Will look further into it.
– Thorsten
Dec 14 '18 at 13:37
Can you reproduce this with DNS-specific tools likehostordig, or does it only happen when using the system resolver via getent? (If it's specific to the system resolver, it will be a module in /etc/nsswitch.conf.) And, most importantly, can you reproduce this withgetent ahostsv6 mx00.emig.gmx.net.with the trailing dot added?
– grawity
Dec 14 '18 at 13:51
I already resolved the problem. My hostname was with with domain "hostname.my.domain" so the resolver in search for the non-existent AAAA of mx00.emig.gmx.net returned mx00.emig.gmx.net.my.domain which resolved to my local IPv6 address and sendmail tried to send the mail to itself. Thanks again a lot!!! ;-)
– Thorsten
Dec 14 '18 at 13:55
Welcome to Super User. If you resolved the problem, please post an actual answer explaining the solution, and accept it. Thanks.
– fixer1234
Dec 14 '18 at 20:42
add a comment |
I encountered a strange problem after enabling IPv6 on my sendmail. BTW, reverse resolution is fine for my domain A and AAAA wise.
Sending mail to a domain with MX A and AAAA records switched now from IPv4 to IPv6. e.g with gmail:
sm-mta[42339]: wBE9nxJl042337: to=<example@gmail.com>, ctladdr=<user@myserver> (1001/1001), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30389, relay=gmail-smtp-in.l.google.com. [IPv6:2a00:1450:400c:c06:0:0:0:1b], dsn=2.0.0, stat=Sent
but sending mail to a domain with only MX A records does not take that IPv4 address for the relay but replaces it with my own servers IPv6 address which results in the "config error: mail loops back to me (MX problem?)" error.
e.g. with gmx.net:
sm-mta[42369]: wBE9oqO5042367: to=<example@gmx.net>, ctladdr=<user@myserver> (1001/1001), delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=30390, relay=mx00.emig.gmx.net. [IPv6:myservers_IPv6_Address!!!here should be the IPv4 address of the mx00.emig.gmx.net!!!], dsn=5.3.5, stat=Local configuration error
which furthermore leads to the "loops back to me" error.
That's what I added to sendmail.mc:
DAEMON_OPTIONS(`Name=MTA-v6, Family=inet6')
How can a IPv4 and IPv6 enabled sendmail communicate with IPv4 only MX of a foreign domain? Why doesn't it resolve the MX's IPv4 address but instead uses it's own IPv6 address? DNS resolv works fine.
sendmail
asked Dec 14 '18 at 10:43
ThorstenThorsten
11
I encountered a strange problem after enabling IPv6 on my sendmail. BTW, reverse resolution is fine for my domain A and AAAA wise.
Sending mail to a domain with MX A and AAAA records switched now from IPv4 to IPv6. e.g with gmail:
sm-mta[42339]: wBE9nxJl042337: to=<example@gmail.com>, ctladdr=<user@myserver> (1001/1001), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30389, relay=gmail-smtp-in.l.google.com. [IPv6:2a00:1450:400c:c06:0:0:0:1b], dsn=2.0.0, stat=Sent
but sending mail to a domain with only MX A records does not take that IPv4 address for the relay but replaces it with my own servers IPv6 address which results in the "config error: mail loops back to me (MX problem?)" error.
e.g. with gmx.net:
sm-mta[42369]: wBE9oqO5042367: to=<example@gmx.net>, ctladdr=<user@myserver> (1001/1001), delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=30390, relay=mx00.emig.gmx.net. [IPv6:myservers_IPv6_Address!!!here should be the IPv4 address of the mx00.emig.gmx.net!!!], dsn=5.3.5, stat=Local configuration error
which furthermore leads to the "loops back to me" error.
That's what I added to sendmail.mc:
DAEMON_OPTIONS(`Name=MTA-v6, Family=inet6')
How can a IPv4 and IPv6 enabled sendmail communicate with IPv4 only MX of a foreign domain? Why doesn't it resolve the MX's IPv4 address but instead uses it's own IPv6 address? DNS resolv works fine.
sendmail
sendmail
asked Dec 14 '18 at 10:43
ThorstenThorsten
11
asked Dec 14 '18 at 10:43
ThorstenThorsten
11
edited Dec 14 '18 at 13:59
Thorsten
asked Dec 14 '18 at 10:43
ThorstenThorsten
11
asked Dec 14 '18 at 10:43
ThorstenThorsten
11
asked Dec 14 '18 at 10:43
ThorstenThorsten
11
11
Is this specific to sendmail, or do you get the same output from other software, e.g.getent ahostsv6 ipv4only.arpaorgetent ahostsv6 mx00.emig.gmx.net?
– grawity
Dec 14 '18 at 12:21
Thanks for the hint. Yes, it seems not to be sendmail related. It generates an IPv6 record like mx00.emig.gmx.net.myown.domain although mx00.emig.gmx.net does not have an AAAA DNS record. Will look further into it.
– Thorsten
Dec 14 '18 at 13:37
Can you reproduce this with DNS-specific tools likehostordig, or does it only happen when using the system resolver via getent? (If it's specific to the system resolver, it will be a module in /etc/nsswitch.conf.) And, most importantly, can you reproduce this withgetent ahostsv6 mx00.emig.gmx.net.with the trailing dot added?
– grawity
Dec 14 '18 at 13:51
I already resolved the problem. My hostname was with with domain "hostname.my.domain" so the resolver in search for the non-existent AAAA of mx00.emig.gmx.net returned mx00.emig.gmx.net.my.domain which resolved to my local IPv6 address and sendmail tried to send the mail to itself. Thanks again a lot!!! ;-)
– Thorsten
Dec 14 '18 at 13:55
Welcome to Super User. If you resolved the problem, please post an actual answer explaining the solution, and accept it. Thanks.
– fixer1234
Dec 14 '18 at 20:42
add a comment |
Is this specific to sendmail, or do you get the same output from other software, e.g.getent ahostsv6 ipv4only.arpaorgetent ahostsv6 mx00.emig.gmx.net?
– grawity
Dec 14 '18 at 12:21
Thanks for the hint. Yes, it seems not to be sendmail related. It generates an IPv6 record like mx00.emig.gmx.net.myown.domain although mx00.emig.gmx.net does not have an AAAA DNS record. Will look further into it.
– Thorsten
Dec 14 '18 at 13:37
Can you reproduce this with DNS-specific tools likehostordig, or does it only happen when using the system resolver via getent? (If it's specific to the system resolver, it will be a module in /etc/nsswitch.conf.) And, most importantly, can you reproduce this withgetent ahostsv6 mx00.emig.gmx.net.with the trailing dot added?
– grawity
Dec 14 '18 at 13:51
I already resolved the problem. My hostname was with with domain "hostname.my.domain" so the resolver in search for the non-existent AAAA of mx00.emig.gmx.net returned mx00.emig.gmx.net.my.domain which resolved to my local IPv6 address and sendmail tried to send the mail to itself. Thanks again a lot!!! ;-)
– Thorsten
Dec 14 '18 at 13:55
Welcome to Super User. If you resolved the problem, please post an actual answer explaining the solution, and accept it. Thanks.
– fixer1234
Dec 14 '18 at 20:42
Is this specific to sendmail, or do you get the same output from other software, e.g.
getent ahostsv6 ipv4only.arpa or getent ahostsv6 mx00.emig.gmx.net?– grawity
Dec 14 '18 at 12:21
Is this specific to sendmail, or do you get the same output from other software, e.g.
getent ahostsv6 ipv4only.arpa or getent ahostsv6 mx00.emig.gmx.net?– grawity
Dec 14 '18 at 12:21
Thanks for the hint. Yes, it seems not to be sendmail related. It generates an IPv6 record like mx00.emig.gmx.net.myown.domain although mx00.emig.gmx.net does not have an AAAA DNS record. Will look further into it.
– Thorsten
Dec 14 '18 at 13:37
Thanks for the hint. Yes, it seems not to be sendmail related. It generates an IPv6 record like mx00.emig.gmx.net.myown.domain although mx00.emig.gmx.net does not have an AAAA DNS record. Will look further into it.
– Thorsten
Dec 14 '18 at 13:37
Can you reproduce this with DNS-specific tools like
host or dig, or does it only happen when using the system resolver via getent? (If it's specific to the system resolver, it will be a module in /etc/nsswitch.conf.) And, most importantly, can you reproduce this with getent ahostsv6 mx00.emig.gmx.net. with the trailing dot added?– grawity
Dec 14 '18 at 13:51
Can you reproduce this with DNS-specific tools like
host or dig, or does it only happen when using the system resolver via getent? (If it's specific to the system resolver, it will be a module in /etc/nsswitch.conf.) And, most importantly, can you reproduce this with getent ahostsv6 mx00.emig.gmx.net. with the trailing dot added?– grawity
Dec 14 '18 at 13:51
I already resolved the problem. My hostname was with with domain "hostname.my.domain" so the resolver in search for the non-existent AAAA of mx00.emig.gmx.net returned mx00.emig.gmx.net.my.domain which resolved to my local IPv6 address and sendmail tried to send the mail to itself. Thanks again a lot!!! ;-)
– Thorsten
Dec 14 '18 at 13:55
I already resolved the problem. My hostname was with with domain "hostname.my.domain" so the resolver in search for the non-existent AAAA of mx00.emig.gmx.net returned mx00.emig.gmx.net.my.domain which resolved to my local IPv6 address and sendmail tried to send the mail to itself. Thanks again a lot!!! ;-)
– Thorsten
Dec 14 '18 at 13:55
Welcome to Super User. If you resolved the problem, please post an actual answer explaining the solution, and accept it. Thanks.
– fixer1234
Dec 14 '18 at 20:42
Welcome to Super User. If you resolved the problem, please post an actual answer explaining the solution, and accept it. Thanks.
– fixer1234
Dec 14 '18 at 20:42
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383545%2fsolved-ipv6-enabled-sendmail-does-not-send-to-domains-with-ipv4-only-mx-which-re%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383545%2fsolved-ipv6-enabled-sendmail-does-not-send-to-domains-with-ipv4-only-mx-which-re%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is this specific to sendmail, or do you get the same output from other software, e.g.
getent ahostsv6 ipv4only.arpaorgetent ahostsv6 mx00.emig.gmx.net?– grawity
Dec 14 '18 at 12:21
Thanks for the hint. Yes, it seems not to be sendmail related. It generates an IPv6 record like mx00.emig.gmx.net.myown.domain although mx00.emig.gmx.net does not have an AAAA DNS record. Will look further into it.
– Thorsten
Dec 14 '18 at 13:37
Can you reproduce this with DNS-specific tools like
hostordig, or does it only happen when using the system resolver via getent? (If it's specific to the system resolver, it will be a module in /etc/nsswitch.conf.) And, most importantly, can you reproduce this withgetent ahostsv6 mx00.emig.gmx.net.with the trailing dot added?– grawity
Dec 14 '18 at 13:51
I already resolved the problem. My hostname was with with domain "hostname.my.domain" so the resolver in search for the non-existent AAAA of mx00.emig.gmx.net returned mx00.emig.gmx.net.my.domain which resolved to my local IPv6 address and sendmail tried to send the mail to itself. Thanks again a lot!!! ;-)
– Thorsten
Dec 14 '18 at 13:55
Welcome to Super User. If you resolved the problem, please post an actual answer explaining the solution, and accept it. Thanks.
– fixer1234
Dec 14 '18 at 20:42