Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Very long connecting time on first launch

  • 2 àwọn èsì
  • 0 ní àwọn ìṣòro yìí
  • 4 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ Wayne Mery

more options

I'm on Thunderbird (128.6.0esr (64-bit)) on Fedora/GNOME. I've noticed, that whenever I launch Thunderbird, it takes several minutes (!) where it says "Connecting to mail.myserver.com" in status. I'm using my own postfix/dovecot server with imap and I don't have this problem on Thunderbird Windows for instance, where it connects right away on startup. After the initial slow connection, it works just fine, when I manually trigger to scan for new messages (instantly). I tried literally any option within Thunderbird to fix that, without any success. It seems to be some trouble with resolving / dns or probably ip6/ip4, but then again, why would it work normally after the long connection time in the beginning? Any clue what might be the problem here?

I'm on Thunderbird (128.6.0esr (64-bit)) on Fedora/GNOME. I've noticed, that whenever I launch Thunderbird, it takes several minutes (!) where it says "Connecting to mail.myserver.com" in status. I'm using my own postfix/dovecot server with imap and I don't have this problem on Thunderbird Windows for instance, where it connects right away on startup. After the initial slow connection, it works just fine, when I manually trigger to scan for new messages (instantly). I tried literally any option within Thunderbird to fix that, without any success. It seems to be some trouble with resolving / dns or probably ip6/ip4, but then again, why would it work normally after the long connection time in the beginning? Any clue what might be the problem here?

Ọ̀nà àbáyọ tí a yàn

The Problem was caused by Fedoras network configuration. I had to disable IPv6 (rathermore the automatic DNS lookup). You can do that in Fedoras GUI config in the Network section or edit

sudo nano /etc/sysctl.conf

net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1

and apply the changes:

sudo sysctl -p

Ka ìdáhùn ni ìṣètò kíkà 👍 0

All Replies (2)

more options

Ọ̀nà àbáyọ Tí a Yàn

The Problem was caused by Fedoras network configuration. I had to disable IPv6 (rathermore the automatic DNS lookup). You can do that in Fedoras GUI config in the Network section or edit

sudo nano /etc/sysctl.conf

net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1

and apply the changes:

sudo sysctl -p

Helpful?

more options

Thanks for posting your solution.

Helpful?

Béèrè ìbéèrè

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.