Re: Dumplicated 'To' fields

[Simon Josefsson <jas@extundo.com>]

Jesper Harder <harder@myrealbox.com> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> Jesper Harder <harder@myrealbox.com> writes:
>>
>>> Simon Josefsson <jas@extundo.com> writes:
>>
>>>> It is valid, so it should work.
>>>
>>> Nope, multiple To fields are not allowed, cf. the table in RFC 2822,
>>> Section 3.6.
>>
>> See RFC 2822 4.5 for the obs-to field definition, which is identical
>> to the to field definition, but can occur several times.
>
> Ah, yes you're right -- it's obsolete, but clients should still be
> able to interpret it.

Perhaps Gnus could warn if the user types multiple To: lines though?
OTOH, minibuffer queries are pure evil, so the warning must be
non-obtrusive if it is present at all.  Perhaps coloring the second To
red and having a balloon help with information would work; or some
tty-friendlier variation of the same idea.

Perhaps other message.el warnings could be recast like this too.  The
non-legible character set question would be really nice to get rid of
IMHO.  Just highlight the illegible text in the message buffer, and
when the user sends the message, really do send it.