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] Disband IPv6 WG
- Previous message (by thread): [ipv6-wg] Disband IPv6 WG
- Next message (by thread): [ipv6-wg] Disband IPv6 WG
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Thu Oct 3 14:03:24 CEST 2019
On Thu, Oct 3, 2019 at 13:57 Jens Link <lists at quux.de> wrote: > Andreas Härpfer <ah at v6x.org> writes: > > >> On 3. Oct 2019, at 13:16, Antonio Prado via ipv6-wg <ipv6-wg at ripe.net> > wrote: > > > No worries, looking at the headers and seeing that nearly all > > received-by mail hops in the original mail use IPv6 addresses > > -- and considering that IPv6 doesn't work anyway -- the whole > > email obviously must have been a complete and utter illusion … > > Thanks for noticing. A new mail server setup is on my todo list, running > a dual stack system is too much work to ipv6 will go away. Even worse, delivering email over ipv6 to the mail giants is a far worse experience than via ipv4. More emails arrive when you disable ipv6 on your mail servers. Kind regards, Job -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ipv6-wg/attachments/20191003/36674e75/attachment.html>
- Previous message (by thread): [ipv6-wg] Disband IPv6 WG
- Next message (by thread): [ipv6-wg] Disband IPv6 WG
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]