🚀 go-pugleaf

In article <8F118FF97033084667@192.116.202.48> 
yaronm@nikuv.co.il (Yaron munz) writes:

> I'm developing an application that can send "raw" SMTP message with MIME to 
> exchange server.  (version is : Microsoft Exchange Internet Mail Connector 
> 4.0.993.5)
> 
> 1. i dont have problems sending non-mime (text only) message : the text 
> apears ok in outlook/inbox. (as regular text no attachemnt).
> 
> 2. when tring to attach a file (mime) using base64 encoding, the file comes 
> OK, but i am NOT ABLE to make additional text to appear as non-attachment 
> in the message. also the 1st text boundry ("TEST LINE 1") is ignored !!!
> My result is a message that have 3 files attached : 
>     	a. the text that i write ("TEST LINE 2")
>     	b. the binary (or any) file a attach with base64 encoding.
>     	c. a message.txt with all data inside incl. header !!!
> 
> pls advs whats wrong here, and how can i solve my problem !
> thanks in advance,
> Yaron
> 
> 
> Here is the lines that i send (between the <DATA> and the <.> commands :
> ------------------------------------------------------------------------
> Date: 09 Apr 2000 12:51:40 GMT
> From: YARON MUNZ
> To: yaronm@nikuv.co.il
> Subject: SUBJECT
> MIME-Version: 1.0
> Content-type: multipart/mixed; boundary="----_=_NextPart_001"
> Content-Disposition: inline
> 
> ------_=_NextPart_001
> Content-type: text/plain; charset=us-ascii
> Content-Disposition: inline
> 
> TEST LINE 1

Note that CRLF before delimiter line is part of delimiter
and headers end to empty line (only CRLF on line). So net
result is that you need two empty lines on here:

Content-Disposition: inline


------_=_NextPart_001
Content-type: text/plain; charset=us-ascii


First empty line ends headers.
And second emty line provides CRLF (or EOLN) 
what is needed for delimiter between body parts.


/ Kari Hurtta