[NTLUG:Discuss] MINE transmission example

[Stuart Johnston]

Leroy Tennison wrote:
> Stuart Johnston wrote:
>> Leroy Tennison wrote:
>>> Anyone got an example showing the SMTP commands used to send a 
>>> base64-encoded MIME message along with the server responses?  I've 
>>> searched the Web and either didn't search for the right things or 
>>> this kind of example is not "out there".
>>>
>>> I would have sent an email with an attachment and captured the packet 
>>> stream with WireShark but my email provider (AT&T) has switched to 
>>> exclusively secure email.  If you use a server which doesn't use 
>>> encryption and could supply a packet capture of the transmission of a 
>>> simple email with an attachment I would be glad to analyze it.
>>>
>>> Thanks for any and all input.
>>
>> MIME is completely independent from SMTP.  Actually, that's kinda the 
>> whole point.  The MIME encoding happens entirely within the DATA 
>> portion (body and headers) so it looks just like a regular text 
>> message to the servers.
>>
>> If you want to see what a MIME encoded email looks like, send yourself 
>> an email with attachment and then hit Ctrl-U on the message (I see you 
>> are using Thunderbird).
>>
> Ctrl-U, I guess I need to read product help, thanks for pointing it out. 
>  My question is this: Do you still use the DATA statement when sending 
> MIME?  In other words, is the sequence
> 
> EHLO
> MAIL FROM: ...
> RCPT TO: ...
> <MIME directives such as Content-type>
> DATA
> <MIME markers separating parts>
> .

Everything goes inside the DATA section:

EHLO
MAIL FROM: ...
RCPT TO: ...
DATA
<MIME directives such as Content-type>
<MIME markers separating parts>
.


I am wondering though, what it is you are trying to do?  This is the 
sort of thing that, generally, you let someone else worry about and use 
an existing module/application.  Or perhaps it is purely academic?