Hi,

the manual page of formail says: If you want to save the original ‘From ’
line, rename it with the -R option to a legal header field such as
‘X-From_:’. But this removes the space after the colon.

% echo From test@localhost | formail -R From X-From_:
X-From_:test@localhost

% echo From test@localhost | formail -R From X-From_
X-From_ test@localhost

% echo From: test@localhost | formail -R From X-From_:
X-From_: test@localhost

% echo From: test@localhost | formail -R From X-From_
X-From_: test@localhost

Bye, Jörg.

Hello.

I received this from the Debian bug system.
Please keep the Cc: lines when replying.

BTW: Is this address still the correct one to report bugs?
I have been forwarding procmail bugs to this address for several years,
but lately nobody reply to them. Please tell me that you are alive.

Package: procmail
Version: 3.22-16
Severity: normal

Hi,

the manual page of formail says: If you want to save the original `From '
line, rename it with the -R option to a legal header field such as
`X-From_:'. But this removes the space after the colon.

% echo From test@localhost | formail -R From X-From_:
X-From_:test@localhost

% echo From test@localhost | formail -R From X-From_
X-From_ test@localhost

% echo From: test@localhost | formail -R From X-From_:
X-From_: test@localhost

% echo From: test@localhost | formail -R From X-From_
X-From_: test@localhost

Bye, Jörg.

[...]

The way I viewed it, was that the actual content of the 'From ' line
starts *after* the space.  RFC prescribes that mail field content starts
directly after the colon, so by introducing an extra space there in case
of renaming a "From " line, would contaminate the content.

It could be argued that an exception for this case (that adds the space
there) would be ok, but I'm not sure if this still is a good idea,
considering backward compatibility.  It would probably be better to
document the anomaly in the man page instead.