Closed Bug 1983413 Opened 3 months ago Closed 1 month ago

Sync Error after Thunderbird 142 Beta3 restart - Request FAILED with status 200: failed to deserialize structure from XML

Categories

(MailNews Core :: Networking: Exchange, defect)

Thunderbird 142
defect

Tracking

(thunderbird145 fixed)

RESOLVED FIXED
146 Branch
Tracking Status
thunderbird145 --- fixed

People

(Reporter: jakob, Assigned: edicharry)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36

Steps to reproduce:

Starting the Thunderbird Client and setting up an account with Office365. It syncs emails amd works.
Close and restart Thunderbird - i will not sync again

Actual results:

Error log:
_xpcom::client] Request FAILED with status 200: failed to deserialize structure from XML
[ERROR ews_xpcom::client] an unexpected error occurred: Ews(Deserialize(Error { path: Path { segments: [Map { key: "Body" }, Map { key: "GetItemResponse" }, Map { key: "ResponseMessages" }, Map { key: "GetItemResponseMessage" }, Seq { index: 8 }, Map { key: "Items" }, Map { key: "$value" }, Seq { index: 0 }, Enum { variant: "Message" }, Map { key: "Sender" }, Map { key: "Mailbox" }, Map { key: "RoutingType" }] }, original: Custom("unknown variant SYSTEM, expected SMTP or EX") }))

Expected results:

Get new Email from server

Component: Untriaged → Networking: Exchange
Product: Thunderbird → MailNews Core
Summary: Sync Error after Thunderbird 142 Beta3 restart → Sync Error after Thunderbird 142 Beta3 restart - Request FAILED with status 200: failed to deserialize structure from XML

Thanks for the detailed error message! From the error you're seeing, it looks like we're encountering a routing type that we weren't expecting. The documentation for the RoutingType element lists SMTP and EX as potential values, but it looks like that's not an exhaustive list considering the error message here is about a routing type called "SYSTEM". Rather than using an enum for routing type, I think we want to make that a free-form string field.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: nobody → edicharry
Status: NEW → ASSIGNED

Pushed by brendan@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/f9bae88e0e5f
Use a free-form string for EWS routing type. r=jtracey

Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 146 Branch

Comment on attachment 9521997 [details]
Bug 1983413 - Use a free-form string for EWS routing type. r=#thunderbird-back-end-reviewers

Uplift Approval Request

  • Please state case for uplift consideration and ensure bug severity is set: This is an issue that could block an account from receiving new emails.
  • User impact if declined: If a user receives a SYSTEM email in their exchange account (or any routing type that isn't SMTP or EX), any subsequent emails they receive will not be listed in Thunderbird.
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Daily?: No
  • Has the fix been verified in Beta?: No
  • Needs manual test from QA?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): This just converts a fixed list field that was never really used into a free-form string field.
  • Does the fix cause any migrations to be skipped?: No
  • String changes made/needed:
Attachment #9521997 - Flags: approval-comm-beta?

Comment on attachment 9521997 [details]
Bug 1983413 - Use a free-form string for EWS routing type. r=#thunderbird-back-end-reviewers

[Triage Comment]
Approved for beta

Attachment #9521997 - Flags: approval-comm-beta? → approval-comm-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: