🚀 go-pugleaf

In article <1992Dec29.183421.22777@news.arc.nasa.gov>, madison@tgv.com (Matt Madison) writes:
> Yes, MX trims trailing blanks.  It does this for two reasons.
> 
>     1.  You have to trim blanks on messages coming in from BITNET.
>         The typical message format there is fixed-length 80-byte records.
> 
>     2.  It saves space on disk.
> 
> The BITNET problem should probably be handled by doing the blank-trimming in
> the MX-Jnet interface ONLY.

And only if the message came in in PUNCH format. Within a few months most of
BITNET (in terms of amount of generated messages, rather than amount of
machines) should be running NETDATA-capable mailers, and there you don't want
to strip spaces. I realize that the JNET interface probably isn't told what
format the file came in, but if the blank line separating the header from the
body is exactly 80 bytes long you can be fairly sure the message was sent in
PUNCH format.

  Eric