using telnet to send emails

[Kent Paul Dolan]

Chris,

Notice in your prior example that you had
"succeeded" on your next to the last attempt, but
went on to try again with _another_ a mail send,
while the previous one was waiting for more input,
generating the "recursive" error message. If you'd
gone ahead instead and done the rest of the email
composing as "Smoot" showed, you'd have succeeded at
doing _something_, but probably not what you
intended.

You really do want to read RFC 821 and RFC 822 as
previously suggested.

It helps at the start for you to know what the valid
formats are for a two part address:

"Christopher Lemire" christopher.lemire at gmail.com
(Christopher Lemire) christopher.lemire at gmail.com
Christopher\ Lemire <christopher.lemire at gmail.com> <---- I think.

I'm not sure a space is permitted as shown in that
last one, even if escaped, but I seem to recall it
working okay that way.

Not that I've tried any of these to see if they work
in telnet, though.

xanthian.

Now if everyone would play good citizen and turn off
all the noise they're sending, like PGP siggies,
HTMLized redundant email copies, MIME wrappers,
non-pure 7 bit ASCII that triggers the email
reflecter to base64 encode the whole email body,
multiple quoted copies of the email reflector
siggie, unneeded bulk quoting of prior email, whines
about thread problems that are meaningless to
someone reading the list with a plain text email
client, quoted-printable mangling, Face, vcard, and
similar ego puffery, employer legal mumbo jumbo
trailers, my ubuntu email would be 10% its current
volume, while being much easier to read.

A little due diligence effort to keep mail bulk down
and garbage suppressed at the origin multiplies its
helpfulness when the fanout is so big as this list.