On 1999-10-18 Anthony J. Albert said:
>Dear Samuel Heywood,
>Yes, the standard for SMTP email does use a '.', alone on a line,
>as the end-of-message marker. However, the mailers are supposed
>to handle it if this occurs in the message text itself. [Without
>checking the RFC, I believe this is handled by the mailer sending a
>'..' sequence, which is converted back to '.'.]
>UUencoded attachments should _never_ have a '.' as the first
>character on the line. The only legal characters that can appear as
>the first character on the line in a UUencoded attachement are:
>'b' (for 'begin')
>'M' (for each line of the attachement)
>'e' (for 'end')
>If you ISP's server is not handling attachments properly, then about
>the only thing that you can do is bring their attention to it. You
>also might switch to MIME-encoded attachements, though that is less
>standardized and some people will have trouble receiving them.
>Anthony J. Albert
Dear Mr. Albert:
In the case of a small executable file that I encoded using UUENCODE
(v56), the latest version by author Richard Marks, the output file
contained a line beginning with a period. The name of the file that
I encoded is DR.COM, 8564 bytes, 12-03-90, a freeware file management
utility from PC Magazine. (I will gladly email this file privately to
anyone on the list who should request it.) To get around the problem
I encoded it again with UUENCODE by use of the "-x" option. The output
file contained no lines beginning with a period. I could successfully
send it by email. The same file, as encoded without the "-x" option
could not be sent by email because the output file had a line beginning
with a period.
Sam Heywood
Net-Tamer V 1.11.2 - Registered
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
