After upgrade to 102.14.0, I could not connect to my mail server (via local proxy). I think upgrade modified profile incorrectly.
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: ishikawa, Unassigned)
Details
Not really sure what has happened, but here is what I observed.
- After an upgrade to 102.14.0 a few days ago, I realized fetching my mail did not occur
successfully. I thought it was a transient network issue, it was not. - I googled and nobody seems to have similar problem, and my local ISP did not post anything about server problems.
- I checked my profile's server setup.
Whoa, I think somebody messed up the server setup. The only thing I can think of is the update to 102.14.0.
I go through a local proxy filter (for spam check), I have to have the following setup.
I am using a Japanese locale version and so am trying to guess what the English entry names are, but you will get the idea.
server type: POP
server name: 127.0.0.1 Port 7110 (default 110)
username: MyISPHostName:myISPUserID:995:ssl
Notice "995:ssl"
This is how I have to tell the local proxy to connect to the myISPHostName using port 995 and the connection ought to be ssl-based (for protection.)
This works. I just confirmed it again.
Problem was that after update to 102.14.0, TB (well, I think it was the updater) modified the line for username to read
MyISPHostName:myISPUserID:ssl (not the missing port number, 995, at the local ISP's host)
or probably picked up an outdated copy somewhere in the profile directory?
There have been reports of profile being updated incorrectly before.
I got hit with incorrect directory name when I use junction/symlink under Windwos 10.
I am afraid this may be similar incorrect rewriting.
To be honest, it is hard to believe that the profile being updated incorrectly due to hardware issue (disk failure?). I am using ECC for memory to avoid memory issues, just in case.
Eliminating ":995" in the pref can only be done in an intelligent software albeit the result is not what I want.
|
||
Comment 1•2 years ago
|
||
No thunderbird patches of significance in 102.14.0 https://hg.mozilla.org/releases/comm-esr102/pushloghtml
And doesn't seem like any https://hg.mozilla.org/releases/mozilla-esr102/pushloghtml would have caused such a problem
|
Reporter | |
Comment 2•2 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #1)
No thunderbird patches of significance in 102.14.0 https://hg.mozilla.org/releases/comm-esr102/pushloghtml
And doesn't seem like any https://hg.mozilla.org/releases/mozilla-esr102/pushloghtml would have caused such a problem
Indeed this is a mystery.
I am trying to see if there is a suspicious routine that handles ':'.
https://searchfox.org/comm-central/search?q=%27%3A%27&path=&case=false®exp=false
But so far nothing stands out.
Description
•