🚀 go-pugleaf

Quoted spaces in headers broke my mail program too, but I *think* I have it
patched up now.  I agree that to fix the problem (you listening Brian?) is far
better than to kluge around it...

I am just patching in code to add a "Message-Id:" line to outgoing messages
from my system (this is homebrew from the bottom up, Univac 1100 assembly).
I have two questions on whether this is going to break anybody's mailers.
Here is an example message I just sent up:

--------------------------------------------

From ZBEN@UMD2.ARPA Thu May 23 09:14:19 1985
Received: from UMD2.ARPA by UMD5.ARPA (4.9/a/4.7)
        id AA09744; Thu, 23 May 85 09:14:13 EDT
Date: Thu, 23 May 85 09:14:24 EDT
From: Ben Cranston <ZBEN@UMD2.ARPA>
To: LOUIE@UMD5
Cc: ZBEN@UMD5
Subject: Message-ID line
Message-Id: <M1985$001009.016118BEN.ZBEN@UMD2.ARPA>
Status: RO

Does it look reasonable?
-zben

--------------------------------------------

Question one: Is the length of the data in the "Message-Id:" going to give
anybody problems?  The M198x$xxxxxx is a unique sequence number.  The
016118BEN is a unique per-user identifier I can use to "Witch-Hunt" anyone
sending obscene or objectionable mail.  The "ZBEN" is just the name of the
mailbox, and is limited to 12 characters.

Question two: I have seen problems with dollar signs ($) in mail names
before.  Advisories from our VM/CMS system come from a virtual machine
named "$MAILER@UMDA" and I have seen at least one system pass that on to
the user as "AILER@UMDA" - presumably because "$M" looked like a beast
called a "MACRO NAME" to SENDMAIL.  I shudder to think what might have
happened if there actually HAD been a $M macro defined.  So, the question
is, will the dollar sign in M198x$xxxxxx give anybody any problems?
Theoretically it may be followed by any digit, practically unless there is
a huge increase in usage of mail the digit will always be a zero.
-- 
Ben Cranston  ...{seismo!umcp-cs,ihnp4!rlgvax}!cvl!umd5!zben  zben@umd2.ARPA