Closed Bug 1847531 Opened 2 years ago Closed 2 years ago

Mailserver configuration detection broken. Error "no configuration found".

Categories

(Thunderbird :: Account Manager, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: amanita+BUGZILLA, Unassigned)

References

Details

(Whiteboard: [support])

Steps to reproduce:

Since 115 creating a new account and autodetecting configs IS BROKEN

I have no idea why, but it doesnt detect the settings anymore and also manual setup doesnt work in my case.

Actual results:

I enter my mail address and password and it tries to get the configs. It stops immediately and says "no configuration found"

Expected results:

The detection should work normally. At least manually it should be possible to create one

Specified App:
Thunderbird org.mozilla.Thunderbird 115.1.0 stable flathub

--- Software ---
OS: Fedora Linux 38.20230806.0 (Kinoite)
KDE Plasma: 5.27.6
KDE Frameworks: 5.108.0
Qt: 5.15.10
Kernel: 6.4.7-200.fc38.x86_64
Compositor: wayland

Unfortunately this is not actionable because you have not supplied information

  • about the account which is failing, eg who is your (mail server) provider
  • the manual settings you attempted to use (assuming you went to manual config after getting "no configuration found")

Another question - does/did this work in a non-flathub environment?

Flags: needinfo?(amanita+BUGZILLA)
Whiteboard: [support]

Is it the outlook account mentioned in bug 1847353 ?

See Also: → 1847353
Summary: Mailserver configuration detection broken → Mailserver configuration detection broken. Error "no configuration found".

this is not about an outlook account, its about all mailservers that normally work without any changes

Flags: needinfo?(amanita+BUGZILLA)

I would not expect 115 autoconfig to be broken for all mailservers.

(In reply to Amanita from comment #3)

this is not about an outlook account, its about all mailservers that normally work without any changes

That's not the case on my end. Perhaps it's a problem specific to your environment as Wayne states.

Only this bug found in bugzilla https://mzl.la/3uhj6cG.
And nothing at all found with google.

If you still see this issue, will need more information about these serveres.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.