Does anyone use aerc on an IPv6 only network? If I disable IPv4,
aerc seems to fail immediately with "Migadu: client not ready"
and a few seconds later, "[Migadu] Disconnected".

Here's what I have in accounts.conf:

    [Migadu]
    source   = imaps://******@imap.migadu.com:993
    outgoing = smtps+plain://******@smtp.migadu.com:465

But both of these domains have full IPv6 support:
https://ip6.nl/#!imap.migadu.com
https://ip6.nl/#!smtp.migadu.com

And I have IPv6 -- I'm able to reach Migadu's web interface.
Changing the config to something like this:

    source   = imaps://******@[2001:41d0:203:b4db::]:993

Unfortunately doesn't seem to work.

On Wed Jun 1, 2022 at 11:12 PM CEST, Mark Dain wrote:
> Does anyone use aerc on an IPv6 only network? If I disable IPv4,
> aerc seems to fail immediately with "Migadu: client not ready"
> and a few seconds later, "[Migadu] Disconnected".

Are you on an IPv6 connection? Some providers still don't support it. I
know that aerc *can* use IPv6, since it uses IPv6 to connect to my
mailserver.

--
Moritz Poldrack
https://moritz.sh

June 1, 2022 10:31 PM, "Moritz Poldrack" <moritz@poldrack.dev> wrote:

> On Wed Jun 1, 2022 at 11:12 PM CEST, Mark Dain wrote:
> 
>> Does anyone use aerc on an IPv6 only network? If I disable IPv4,
>> aerc seems to fail immediately with "Migadu: client not ready"
>> and a few seconds later, "[Migadu] Disconnected".
> 
> Are you on an IPv6 connection?

Yeah, IPv6 work perfectly fine. I get 10/10 on test-ipv6.com and can reach
IPv6 only sites like loopsofzen.uk.

> I know that aerc *can* use IPv6, since it uses IPv6 to connect to my
> mailserver.

I'm sure I've seen aerc use IPv6 too... this is what I'm confused by. It
might be some kind of bootstrapping; I sometimes run into this when I have
IPv4 turned off -- it exposes that a lot of "IPv6 capable" stuff often
requires an IPv4 connection for DNS or OCSP.

Hello,

RE an old thread on IPv6;

I'm sitting in FOSDEM and aerc (0.16.0-1) is failing to connect to my
mail server. Some facts:

  * I'm on the FOSDEM wifi
  * It's issued me an IPv6 address and route only
  * my mailserver host has A and AAAA records
  * mutt works (mailserver ok; routing to it via IPv6 OK)

If I substitute my hostname for one that only has an AAAA record, aerc
connects (and complains that the SSL cert is invalid for this hostname,
which is correct)

If I add an ipv6-only /etc/hosts entry, aerc correctly connects.

My theory is, if aerc resolve an A record but fails to connect (due to
no ipv4 route if not other reasons), it doesn't attempt the AAAA.

Please go looking for an unattended 26 year old French boy. He will 
personally check it out :D

-- 
Moritz Poldrack
https://moritz.sh

Quoting from IRC:

18:22           mpldr  rjarry, can you use aerc at fosdem?
               rjarry  yes
               rjarry  jmap only
               rjarry  imap is broken
18:23          rjarry  I guess go-imap does not try connecting again when ipv4 fails
          ferdinandyb  What a field test this is then!
18:24           mpldr  can you look more into why that is? I dont really have an environment to test that in

So let's hope he isn't too hammered and can investigate. Otherwise,
we'll try to reproduce it somehow.

-- 
Moritz Poldrack
https://moritz.sh

> Positively no smoking.

Jonathan Dowland, Feb 03, 2024 at 18:14:
> Hello,
>
> RE an old thread on IPv6;
>
> I'm sitting in FOSDEM and aerc (0.16.0-1) is failing to connect to my
> mail server. Some facts:
>
>   * I'm on the FOSDEM wifi
>   * It's issued me an IPv6 address and route only
>   * my mailserver host has A and AAAA records
>   * mutt works (mailserver ok; routing to it via IPv6 OK)
>
> If I substitute my hostname for one that only has an AAAA record, aerc
> connects (and complains that the SSL cert is invalid for this hostname,
> which is correct)

I can confirm that there is an issue with IMAP when connected on the 
FOSDEM wifi. However, JMAP works fine.

> If I add an ipv6-only /etc/hosts entry, aerc correctly connects.
>
> My theory is, if aerc resolve an A record but fails to connect (due to
> no ipv4 route if not other reasons), it doesn't attempt the AAAA.

Aerc actually does not resolve anything. It is done by your local 
resolver. Have you had a look in /etc/nsswitch.conf?

My theory is that the issue of not having an IPv4 address when 
getnameinfo() returns multiple results with mixed v4 and v6 is not 
handled properly by go-imap which aerc builds upon.

We would need to check it with go-imap about what they think.

Short test that demonstrates that a go program uses the v4 address 
returned by the DNS request:

$ echo HELO | nc -v imap.gmail.com 993
Ncat: Version 7.93 ( https://nmap.org/ncat )
Ncat: Connected to 2a00:1450:400c:c02::6c:993.
FNcat: 5 bytes sent, 7 bytes received in 0.15 seconds.

$ cat dial.go 
package main

import (
	"log"
	"net"
	"os"
)

func main() {
	addr, err := net.ResolveTCPAddr("tcp", os.Args[1])
	if err != nil {
		log.Fatalf("net.ResolveTCPAddr: %v\n", err)
	}

	log.Printf("%v: %#v\n", addr, addr)

	conn, err := net.DialTCP("tcp", nil, addr)
	if err != nil {
		log.Fatalf("net.DialTCP: %v\n", err)
	}

	conn.Close()
}
$ go run dial.go imap.gmail.com:993
2024/02/03 18:51:13 64.233.184.108:993: &net.TCPAddr{IP:net.IP{0x40, 0xe9, 0xb8, 0x6c}, Port:993, Zone:""}
2024/02/03 18:51:13 net.DialTCP: dial tcp 64.233.184.108:993: connect: network is unreachable
exit status 1

Hey Jonathan,

following up on this, could you please try the following:
- go mod vendor
- curl http://0x0.st/HDDg.patch | git apply
- make aerc && ./aerc

Let me know if this fixes things :)

-- 
Moritz Poldrack
https://moritz.sh

> Limitations on coverage and remedies apply.

On Sat Feb 3, 2024 at 6:14 PM CET, Jonathan Dowland wrote:
> I'm sitting in FOSDEM and aerc (0.16.0-1) is failing to connect to my
> mail server. Some facts:

Most likely the network blocked access to non-HTTP ports. I had
the same problems.

Matěj

-- 
http://matej.ceplovi.cz/blog/, @mcepl@floss.social
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
Thou shalt not nede to be afrayed for any bugges by night.
  -- Coverdale’s 1535 translation of Psalm 91
     (or Christopher Higley’s 1972 thesis explaining why
      programmers’ are nocturnal beasts)

On Sat Feb 3, 2024 at 2:05 PM CST, Matěj Cepl wrote:
> On Sat Feb 3, 2024 at 6:14 PM CET, Jonathan Dowland wrote:
> > I'm sitting in FOSDEM and aerc (0.16.0-1) is failing to connect to my
> > mail server. Some facts:
>
> Most likely the network blocked access to non-HTTP ports. I had
> the same problems.

Robin could test this tomorrow through the fastmail imap proxy:

  imaps-proxy.fastmail.com:443

-- 
Tim

On Sat Feb 3, 2024 at 8:20 PM GMT, Matěj Cepl wrote:
> On Sat Feb 3, 2024 at 6:14 PM CET, Jonathan Dowland wrote:
> > I'm sitting in FOSDEM and aerc (0.16.0-1) is failing to connect to my
> > mail server. Some facts:
>
> Most likely the network blocked access to non-HTTP ports. I had
> the same problems.

I'm not so sure; as I say, neomutt worked.

I'm here Tomorrow too (and intending to catch Robin's lightning talk.
Are you going to be there Matěj? I would like to say hello :-))

I'll try to TAL the patch posted to this thread before then.

On Sat Feb 3, 2024 at 5:44 PM GMT, Moritz Poldrack wrote:
> following up on this, could you please try the following:
> - go mod vendor
> - curl http://0x0.st/HDDg.patch | git apply
> - make aerc && ./aerc
>
> Let me know if this fixes things :)

Thank you: this mail confirms it's built and functional (from my
ipv4 hotel room); Tomorrow I will road test it at FOSDEM.

On 2024-02-03 23:57, Jonathan Dowland wrote:
> I'm here Tomorrow too (and intending to catch Robin's lightning talk.
> Are you going to be there Matěj? I would like to say hello :-))

I will try my best.

Matěj
-- 
http://matej.ceplovi.cz/blog/, @mcepl@floss.social
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8

[…] sleep is no substitute for caffeine.
       -- Robert Storey in review of Debian
          (when describing re-compilation of kernel :-))

On Sun Feb 4, 2024 at 10:06 AM GMT,  wrote:
> On 2024-02-03 23:57, Jonathan Dowland wrote:
> > I'm here Tomorrow too (and intending to catch Robin's lightning talk.
> > Are you going to be there Matěj? I would like to say hello :-))
>
> I will try my best.

I'm going to fail to catch Robin's talk due to a clash :(

Stop me if you see me. I'm wearing a redhat fedora and a Debian Debconf
'07 t-shirt (grey/blue). I'll be spending time near food trucks, in Chez
Theo, and around booths, but I'll be over in K at 2pm.
Photo of me at jmtd.net/about

Good luck Robin! Be sure to mention the FOSDEM-triggered fix!