[Users] Odd behaviour when Default Cc: is sent in a folder's Compose Properties

[Brad Rogers]

On Wed, 12 Feb 2025 17:02:52 -0000
Paul <paul at claws-mail.org> wrote:

Hello Paul,

>So what you are saying is, when the address in the To: header is the
>same as the address in the Cc:, the former is stripped rather than the
>latter?

Yes.  Exactly that.

I realise it's probably an odd thing to set To: and Cc: to the same
address, but I have my reasons.  Those reasons may not be entirely
rational, and based on what you say and further study, redundant.

Whether ort not this is worth pursuing further, I'll leave up to you.


Looking at messages that I get sent back from lists (and at list
archives) that are affected, there is a To: header in them.  So it
appears that the To: header is not being shown in the Compose message
window of CM (I did check the headers pane by scrolling up and down to
double check I wasn't missing a header scrolled out of view) but is
actually transmitted correctly.

I suppose one could argue that this is only a cosmetic problem.

I've also delved back through sent emails and have discovered that this
has been occurring a lot longer than I thought:

Cc: was stripped in 4.1.1git78
To: was stripped in 4.1.1git90

Which is around September/October of 2023.

My previous mention of more recent versions (4.3.0git57 and git65) is
clearly wrong.  My apologies for that.

-- 
 Regards  _       "Valid sig separator is {dash}{dash}{space}"
         / )      "The blindingly obvious is never immediately apparent"
        / _)rad   "Is it only me that has a working delete key?"
My limbs are like palm trees swaying in the breeze
Mirage - Siouxsie & The Banshees
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20250212/476915e8/attachment.sig>