|
|
Uday S Reddy <uDOTsDOTreddy@xxxxxxxxxxxxx> writes:
> blueman wrote:
>
>>
>> Plus using the separator is really as Julian suggested (and you
>> confirmed) a deviant case since when piping single messages, the
>> separator really has no use or meaning. To quote Julian:
>>
>> The initial From line is NOT part of the RFC standard, nor is it
>> part of the message. It's an obsolete Unix mbox hack that should
>> have been killed off decades ago - the mbox format is patently
>> unsuitable, leading to abominations like From-stuffing. I've had
>> immense trouble with very broken mail systems (procmail) that
>> insist on putting the From in where it has no business - it caused
>> standards-compliant mail filters to break, because they saw a From
>> instead of a proper message.
>>
>> Even I (who is the one who requested the From_ header) don't have a use
>> case for it in the case of individual messages. I only need it when
>> piping multiple messages.
>
> Ok, I am removing the original addition to the singular version of the
> command since it doesn't seem to be useful. There will be no 4-prefix
> version of the command for the same reason.
Although I always like more options and wouldn't have minded the
4-prefix version, I think your decision is wise in that it avoids
confusion between multiple ways of adding separators. And since as
Julian pointed out, the separators have more to do with multiple
messages and don't really have meaning on single messages, the best way
to get separators for a single message is to use vm-pipe-messages-to-command.
Perhaps we should add to the def strings that vm-pipe-message-to-command
does not include separators and that vm-pipe-messages does.
> It is my understanding that the plural version of the command in
> launchpad satisfies all your needs. If not, please let me know.
>
That is correct. I will send you a new patch when we figure out why it
isn't working on your setup.
|
|