Thanks to all who responded.

Beechglen mentioned that nmmail can have a problem with attachments with
periods in columns 1 & 67.

Quick testing on my end seems to confirm this.  With quoted-printable encoding
on a short variable-length file with no trailing spaces,  a line with just 66
'x's followed by a '.' ends the message at that point, but it works if I add
or drop an 'x', or put a character after the '.'.  A line with just a period
in column 1 ends the message, but it works if I add something after the
period.

So it should be safe to switch my rtf reports from base-64 encoding to
quoted-printable, because that output is from  cobol reports which won't have
a period at the end of a line  :)

And I can leave my text file app in base64 encoding, which does not have the
'.' problem.  Nobody is complaining about problems reading them, and I think I
know why.  The most common problem with rtf attachments & base64 is webmails
treating the attachment as part of the message body and showing it 'as is',
with all the funky codes.  When you think about it, thats not much of a
problem with plain text files.  The two webmails I can test both do that and
the only problem is that one of them uses a variable font, so columns don't
line up like they would in Notepad.

:)
YMMV

Dave Powell,   MMfab

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *