FM> Would you care to comment on Eef's comments below?

Ok.

EH>  FM> No I didn't know that. I'm surprised that you saw a tab (which is
EH>  FM> actually #9, #12 is FF) in my message. I don't normally type

EH> Indeed: tab is ctrl-I is #9, FF is ctrl-L = #12.

EH> According to FTS-0001 BOTH are illegal in packets, though.

Please quote FTS-1, that should be good for a laugh.

EH> A packet consists of:
EH> printable chars in the range 32-126 (for text and the text fields in
EH> header)

Yeah?  Quote please.  Wrong again.

EH> And that is it. No other control chars, no "chars >
126", except for this
EH> #141 (and of course the binary bytes and words in the binary fields of the
EH> header).

Quote please.

EH>  FM> I think that's it. I understand that the PKT standard is to use
EH>  FM> #141 as a 'soft' carriage return (CR + 128) but what I don't yet know
EH> is
EH>  FM> whether those should get into the outgoing PKT or be stripped.

Don't generate #141 at all.  Only dickheads generate that.  Have
a look at what percentage of your incoming messages have them.
Very, very few.  Note that you are not allowed to generate #141
as a soft-CR if you use SOT/EOT.  You are allowed to use it as a
national character (it's part of the Russian alphabet, e.g.).

EH> Both is possible. They ARE allowed in .PKT's but when
"tossing" those you
EH> MAY strip them if you do not want them.

So long as you don't alter in-transit mail, you may replace all
occurrences of "shit" with "sh*t" if that's what turns you on.
BFN.  Paul.
@EOT:

---