Re: IPv6 recap

Mario Roberto Ferreira <[email protected]>
Newsgroups gmane.mail.imap.courier.general
Message-ID <CABSW8ZzvXQ+NYZpP3JROes4eu2mnHCOVTJrEt2xc9Uc_ARf8QQ@mail.gmail.com>
Question from last time...lol

Reverse... until when will it be necessary?

In my opinion, it should be extinct.

Em sex., 5 de abr. de 2024 às 08:53, Alessandro Vesely <[email protected]>
escreveu:

> Hi,
>
> this happened again, but this time caused a bounce:
>
>   <<< 554 resimta-c2p-559421.sys.comcast.net
> resimta-c2p-559421.sys.comcast.net 2a02:29e1:500:6c00::4 Comcast requires
> that all mail servers must have a PTR record with a valid Reverse DNS
> entry. Currently your mail server does not fill that requirement. For more
> information, refer to:
> https://postmaster.comcast.net/smtp-error-codes.php#554
>
> Is it possible to inhibit use of IPv6 a little bit harder?
>
> There's no way I can get a reverse address for 2a02:29e1:500:6c00::/56, as
> my provider itself didn't get a delegation for its 2a02:29e1::/32.  It goes
> to 2a:: in RIPE:
>
> ; <<>> DiG 9.18.24-1-Debian <<>> 1.e.9.2.2.0.a.2.ip6.arpa ns
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19800
> ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 1232
> ; COOKIE: cad8ae482b0e559c01000000660fe49763aa815e05fda159 (good)
> ;; QUESTION SECTION:
> ;1.e.9.2.2.0.a.2.ip6.arpa.      IN      NS
>
> ;; AUTHORITY SECTION:
> 0.a.2.ip6.arpa.         3600    IN      SOA     pri.authdns.ripe.net.
> dns.ripe.net. 1712314758 3600 600 864000 3600
>
>
> Best
> Ale
>
>
> On Mon 01/Apr/2024 12:18:52 +0200 Alessandro Vesely wrote:
> > On Sun 24/Mar/2024 13:00:34 +0100 Alessandro Vesely wrote:
> >>
> >> I ended up setting two new IPv6 addresses.  One for outgoing mail, in
> ip6out
> >> and SPF record.  The other for incoming, set in esmtpd's PORT variable
> and
> >> published as a secondary MX which only has an AAAA address.
> >>
> >> Thus far neither happened to be used.
> >
> >
> > Update: one was used yesterday, for outgoing mail:
> >
> > Mar 31 04:47:04 22 north courieresmtp:
> > id=00000000005DC23B.000000006608CEA7.000063AD,from=<[email protected]
> >,addr=<[email protected]>: 250 2.0.0 OK  1711853224
> g24-20020a1709063b1800b00a47484f15e9si3262997ejf.241 - gsmtp
> > Mar 31 04:47:04 22 north courieresmtp:
> > id=00000000005DC23B.000000006608CEA7.000063AD,from=<[email protected]
> >,addr=<[email protected]>,success: delivered: alt1.aspmx.l.google.com
> [2a00:1450:4025:c03::1b]
> > Mar 31 04:47:04 22 north courieresmtp:
> > id=00000000005DC23B.000000006608CEA7.000063AD,from=<[email protected]
> >,addr=<[email protected]>,status: success
> >
> > Probably due to a delayed response to the A query.
> >
> >
> > Best
> > Ale
>
>
> _______________________________________________
> courier-users mailing list
> [email protected]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
>

_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.