This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/

[ipv6-wg] Real-world IPv6 SMTP experience

Previous message (by thread): [ipv6-wg] Real-world IPv6 SMTP experience
Next message (by thread): [ipv6-wg] New IPv6 Address Block Allocated to the RIPE NCC

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Pim van Pelt pim at ipng.nl
Wed Dec 21 17:22:27 CET 2005

Hi,
	
| So if I understand this correctly, having a v4-only backup MX should
| solve all problems commonly experienced?
Yes. Note that BIT has not seen any MTA problems, even though BIT may 
be somewhat bolder than most. We have our MX records pointing to:
bit.nl mail is handled by 100 mx1.bit.nl.
bit.nl mail is handled by 200 mx2.bit.nl.
bit.nl mail is handled by 300 mx3.bit.nl.

... and each of these has an IPv4 and an IPv6 address.

-- 
---------- - -    - - -+- - -    - - ----------
Pim van Pelt                 Email: pim at ipng.nl
http://www.ipng.nl/             IPv6 Deployment
-----------------------------------------------

Previous message (by thread): [ipv6-wg] Real-world IPv6 SMTP experience
Next message (by thread): [ipv6-wg] New IPv6 Address Block Allocated to the RIPE NCC

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]