[DUG] Email attachment encoding/decoding

[Bevan Edwards]

Hi John,

Probably because when the data is being sent via SMTP, a single dot and 
CRLF on a line indicates the end of the message data - so perhaps it's 
being added by a mail server in order to prevent end of data being 
specified?

Regards,

Bevan


On 13/09/2014 4:18 p.m., John Bird wrote:
> I have a program that sends data via an email attachment, the file 
> data is encoded into ascii text (ie all characters are ASCII and the 
> whole range can be used) and contains CRLF between the lines of data.
> Sending and receiving is done via standard email programs, so the 
> encoding/decoding is not done by me.
> When the file is received and the attachment saved, I have noticed an 
> oddity -- if a line in the sent data occasionally happens to start 
> with a full-stop "." (ie immediately after the CRLF)  then at the 
> other end there appears two full-stops instead of one.   Otherwise the 
> attachment arrives the same as sent.
> Anyone have ideas why this happens and how to get around this? eg I am 
> wondering if I should replace the CRLF characters with something else 
> so the encoding does not treat it as text.
>
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at listserver.123.net.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at listserver.123.net.nz with Subject: unsubscribe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20140913/8b700100/attachment.html