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

[Brad Rogers]

Hello,

I have noticed recently some emails to mailing lists going astray.
Examination of 'sent' messages shows that some have no To: address.
Obviously, they're going to fail.  *However*, these mails are being sent
from folders where default To, Reply-To etc. values are set for Compose,
so they /should/ have a valid To address header.

I have found that the issue is having a Default Cc: set.  When that is
set, no valid To: address is placed in the headers.  Untick the Default
Cc: and a To: address is entered correctly.

As far as I can ascertain, this change in behaviour occurred somewhere
between git57 and git65.  I can't narrow it any tighter than that
because of when I compiled versions.  Sorry.

Obviously there's an easy workaround, but thought I'd mention it case
others have similar issues.

If requested, I can create a bug report.

-- 
 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?"
Looking for something I can call my own
Chairman Of The Bored - Crass
-------------- 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/c24720bb/attachment.sig>