On 05/15/2018 08:01:20 PM Tue, Peter Bloomfield wrote: …
So, here's the problem: if you hit 'Reply to group', Balsa tries to follow RFC 2369[0], which describes how to handle 'mailing list command specification header fields', and, in particular, Balsa looks for a 'List-Post:' header. If the message you're replying to is the one from a conforming list, it finds that header and sets up the 'To:' field correctly. If you received a copy addressed to you directly, it doesn't have that header, and Balsa just gives up. A better reaction might be to pop up a dialog pointing out that the message doesn't appear to have been sent from a group, and suggesting 'Reply all' as an alternative.
Actually, the *real* problem is that "Reply to Group…" should be disabled when the message was not sent by a mailing list. Balsa goes to some trouble to make each entry on the "Message" menu active only when it could actually do something, but "Reply to Group…" was not handled separately from the other reply options. Fixed in master and the wip branches. One remaining issue: if *multiple* messages are selected, "Reply to Group…" is enabled if *any* of them is from a mailing list. Like other reply options, "Reply to Group…" opens a compose window for each of them, and if any is *not* from a mailing list, it gets the empty "To:" list. Perhaps that's acceptable in this unlikely use case? Peter
pgpKeBYKDKBr_.pgp
Description: PGP signature
_______________________________________________ balsa-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/balsa-list
