Closed Bug 1679280 Opened 5 years ago Closed 5 years ago

Connection refused to local network IMAP server after update to 78.5.0

Categories

(MailNews Core :: Networking: IMAP, defect)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1677806

People

(Reporter: it, Unassigned)

Details

(Keywords: regression, Whiteboard: [regression 78.4.3->78.5.0])

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

installed the update from version 78.4.3 to version 78.5.0 (on Windows 10 Pro), tried connecting to my local network IMAP server (account already existing before the update)

Actual results:

The connection to my IMAP server on the local network was refused ("Could not connect to server server2"). On the IMAP-server no connection-request was logged.
Connecting to the server over its IP-address (192.168.0.1) works, using its name 'server2' gives me the error. So it seems to me that the problem lies within the name resolution.

Reinstalling version 78.4.3 'fixes' the problem: the connection via hostname 'server2' works again. So it seems to me that this bug was introduced with the update to 78.5.0

Expected results:

the connection to the local network IMAP-server should have worked via its hostname

Component: Untriaged → Networking: IMAP
Product: Thunderbird → MailNews Core

The Thunderbird counterpart of bug 1677806?

Thanks, :emk! Yes, sounds like it.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Keywords: regression
Resolution: --- → DUPLICATE
Whiteboard: [regression 78.4.3->78.5.0]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: