how to run exim that work only with ipv6 ?
- Thread starter ccirco
- Start date
no every one for answer too me?
i study this links but i can not config exim for work only by ipv6
http://www.exim.org/exim-html-current/doc/html/spec_html/ch-main_configuration.html
http://www.exim.org/exim-html-curre...daemon_and_the_use_of_network_interfaces.html
http://help.directadmin.com/item.php?id=353
i study this links but i can not config exim for work only by ipv6
http://www.exim.org/exim-html-current/doc/html/spec_html/ch-main_configuration.html
http://www.exim.org/exim-html-curre...daemon_and_the_use_of_network_interfaces.html
http://help.directadmin.com/item.php?id=353
nobaloney
NoBaloney Internet Svcs - In Memoriam †
Generally if no one replies it's because no one knows the answer. It's doubtful that anyone here has experience with running Exim only to send mail on IPv6, because if exim would only send email on IPv6, then no other server not supporting IPv6 could receive mail from, or send email to, your server. Is that really what you want?
If your server only connects through IPv6, then the exim install will only work on IPv6. Exim by default uses the main server IP# as the outbound IP#.
However you cannot set the main server IP# as IPv6 because DirectAdmin's licensing system doesn't support IPv6, which means that DirectAdmin must use an IPv4 IP# as the main server IP#.
Perhaps this guide will help you; have you tried using your IPv6 IP# instead of the IPv4 IP# listed in this guide?
Perhaps this wiki (github.com) will have some useful information.
Otherwise you could probably create special rules in your firewall to refuse all inbound traffic on ports 25 and 443 of any IPv4 IP#, and to also route any outbound traffic from the server to any other server on port 25 or 443, to send email through one o fyour IPv6 ip#s.
Note these are just thoughts. Untried, untested, and only spent about fifteen minutes thinking about it.
Jeff
If your server only connects through IPv6, then the exim install will only work on IPv6. Exim by default uses the main server IP# as the outbound IP#.
However you cannot set the main server IP# as IPv6 because DirectAdmin's licensing system doesn't support IPv6, which means that DirectAdmin must use an IPv4 IP# as the main server IP#.
Perhaps this guide will help you; have you tried using your IPv6 IP# instead of the IPv4 IP# listed in this guide?
Perhaps this wiki (github.com) will have some useful information.
Otherwise you could probably create special rules in your firewall to refuse all inbound traffic on ports 25 and 443 of any IPv4 IP#, and to also route any outbound traffic from the server to any other server on port 25 or 443, to send email through one o fyour IPv6 ip#s.
Note these are just thoughts. Untried, untested, and only spent about fifteen minutes thinking about it.
Jeff
thank you dear jeff.
but when according this text. >> http://help.directadmin.com/item.php?id=152
insert my ipv6 in Forward interface =
exim send exit emails by main ipv4 server .
i seting my ipv6 in direct admin and it have ping too me.
please help my for send emails by ipv6 in exim and with direcadmin control panel.
nobaloney
NoBaloney Internet Svcs - In Memoriam †
When exim sends email on IPv4 it's likely because the lowest-value MX record for the domain is for an IPv4 IP#. Exim (in fact every properly designed MTA) will always presume that the lowest-value MX record points to the IP# on which the recipient server prefers to get email, and won't try any other unless the mail server at that IP# isn't available.
Exim can't talk to an IPv4 IP# from it's IPv6 IP# (this is a limitation of how IP routing works). For more information, see this article(cisco.com), and also RFC 6144.
Since exim knows it can't connect to anIPv4 network from an IPv6 port, if the MX record is an IPv4 address, then exim will follow the rules in RFC #2821 (tools.ietf.org), Section 5. so if there's an IPv4 interface available, exim must use it because otherwise it cannot deliver the email, and it's primary job is to deliver the email.
As I wrote previously, a workaround would be to break the rules yourself, in your firewall, in which case exim will end up returning the email as undeliverable.
I'm still not sure why you want to deliver email only to servers connecting through IPv6. Of course that's your decision. If you do you wn't be able to reach a lot of people on the Internet. Including me.
Jeff
Exim can't talk to an IPv4 IP# from it's IPv6 IP# (this is a limitation of how IP routing works). For more information, see this article(cisco.com), and also RFC 6144.
Since exim knows it can't connect to anIPv4 network from an IPv6 port, if the MX record is an IPv4 address, then exim will follow the rules in RFC #2821 (tools.ietf.org), Section 5. so if there's an IPv4 interface available, exim must use it because otherwise it cannot deliver the email, and it's primary job is to deliver the email.
As I wrote previously, a workaround would be to break the rules yourself, in your firewall, in which case exim will end up returning the email as undeliverable.
I'm still not sure why you want to deliver email only to servers connecting through IPv6. Of course that's your decision. If you do you wn't be able to reach a lot of people on the Internet. Including me.
Jeff