Closed Bug 1815559 Opened 2 years ago Closed 1 year ago

Delivered-To header ignored when selecting reply identity (for catch-all)

Categories

(Thunderbird :: Account Manager, enhancement)

Thunderbird 102
enhancement

Tracking

(thunderbird_esr102 wontfix, thunderbird_esr115? fixed)

RESOLVED FIXED
119 Branch
Tracking Status
thunderbird_esr102 --- wontfix
thunderbird_esr115 ? fixed

People

(Reporter: me, Assigned: me)

References

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/109.0

Steps to reproduce:

  • Setup an account with addresses that accept aliases, i.e. with protonmail name1@proton.me (as default server identity) and name2@proton.me (as second identity)
  • Setup a different (unrelated) account with a catch-all address, e.g. *@cimba.li
  • Attempt to reply to an aliased email, i.e. sent to name2+alias@proton.me

Actual results:

Selected reply identity is the default identity, name1@proton.me

Expected results:

Selected identity should be the receiving identity, name2@proton.me, matched in the email headers with “Delivered-To: name2@proton.me

  • If an email is sent to name2@proton.me instead of name2+alias@proton.me, the correct identity is matched.
  • This happens when at least an email address has catch-all enabled, even if it’s completely unrelated (as in a different domain, servers, and all)
  • If there is no catch-all at all, then the delivered-to header is checked

It seems delivered-to header was initially used only on replies to lists, and then as a hint for any received email since circa 2012, only dropped in the changeset that introduced catchall (if catch-all is enabled, and still used if catch-all is disabled). RFC 9228 describes “alias processing” (in this case name2+alias@proton.me -> name2@proton.me) as a valid use of this header.

I think either one of these 2 fixes should be implemented:

  • append the last delivered-to address (as returned by findDeliveredToIdentityEmail()) to the list of hints used for matching (collectedHeaderAddresses)
  • add “delivered-to” to the default list in mail.compose.catchAllHeaders

These options only differ if there are repeated “delivered-to” headers. I’m not 100% sure of the implications of that -- findDeliveredToIdentityEmail() seems to go to some effort to check latest headers first.

Summary: Delivered-To header ignored when selecting reply identity → Delivered-To header ignored when selecting reply identity (for catch-all)
See Also: → 1851512

Adds the “delivered-to” to the list of default headers to use to
identify the identity when catch-all is active. Note that delivered-to
is already used when catch-all is off.

Assignee: nobody → me
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/d9a3a27f769f
Expand use of "delivered-to" to find identity to catch-all. r=mkmelin

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED

Comment on attachment 9352036 [details]
Bug 1815559 - Expand use of "delivered-to" to find identity to catch-all. r=mkmelin

[Approval Request Comment]
User impact if declined: delivered-to not considered for catch-all
Testing completed (on c-c, etc.): c-c, beta
Risk to taking this patch (and alternatives if risky): fairly safe

Attachment #9352036 - Flags: approval-comm-esr115?

Comment on attachment 9352036 [details]
Bug 1815559 - Expand use of "delivered-to" to find identity to catch-all. r=mkmelin

[Triage Comment]
Approved for esr115

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

Attachment

General

Creator:
Created:
Updated:
Size: