Open Bug 1973776 Opened 5 days ago Updated 4 days ago

"reply from this identity when delivery headers match" does not respect "To"/wrong priorities

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 128
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: u774610, Unassigned)

Details

Steps to reproduce:

Have a catch-all mailbox mail@example.org which does receive all mails sent to abc@example.org, ..., xyz@example.org.

  1. Create wildcard/catch-all identity: "@example.org" and enable "reply from this identity when delivery headers match" set to "@example.org"
  2. Send an email to test@example.org.
  3. Mail will get delivered to mail@example.org inbox with "Delivered-To" header set to "mail@example.org".
  4. Forward or reply this message.

Actual results:

Identity in forward/reply composing window is set to "mail@example.org".

Expected results:

Identity should be set to "test@example.org".

"To" header should have priority over "Delivered-To". "X-Original-To" header should have priority over "Delivered-To" as well.

(have no access to the mailserver so I can't prevent the mailserver to set the "Delivered-To" header. Anyway, "To" should have priority over "Delivered-To".

All emails get recieved into the 'mail@example.org' catch all account
I presume identity called 'test@example.org' is set up as an additional identity of 'mail@example.org' mail account.
In 'Manage Identities' for the 'test@example.org' identity - Did you set up "reply from this identity when delivery headers match" eg: test@example.org?

Test
I have a mail acount 'mail@domain' which is a catch all acount for emails sent to 'mail@domain' and 'info@domain'.
I added an identity to 'mail@domain' mail account called 'info@domain'
In 'info@domain' identity - I set up 'reply from this identity when delivery headers match' 'info@domain'

When I send email from another account to 'info@domain', it is received into the 'mail@domain' Inbox.
When I click on Reply from uses the 'info@domain' in 'From' and 'TO' uses the account which sent original email.
So all is working as expected.

You need to log in before you can comment on or make changes to this bug.