Ultimate TCP 2.0

[realJSOP]

Alrightie. I sent my email account a couple of messages - one with an attachment and one without. I can make a connection and save the email messages to temporary files, but I have some questions: 1) ALL of the email messages contain this text: "This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible." Why does it say that, and how does the mail server know that my mail reader doesn't understand MIME? 2) Do I have to parse out different parts of the email message myself? For instance, I want to be able to get the FROM, TO, DATE, SUBJECT, and text message parts. I realize this library is WAY out of date, but I could really use some help.

[Dundas TCP IP Support]

Hello John, The server does not have to worry about if the client has MIME ability or not. It is the responsibility of the email client (e.g. Outlook and outlook Express, etc) to decode the mail message. All what the server cares about is that it has a stream of ASCII characters that it needs to be delivered to the client. Hence the need for MIME encoding (to be able to deliver binary information such as executable and zip files) When an RFC-822 message contains an attachment that is encoded in MIME format, it has to have as part of the header the following string

"MIME-Version: 1.0"

This header is the key for the client to recognize if it needs to use the mime decoding routines or not. (A message headers section is everything from the start of the message until the first blank line) The other mime headers (such as Content-Type will tell the client what decoding routines should be employed. When a message contains more than one part such as text message and an image this header will be tagged as in the following

Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0024_01C09123.EE12B460"

The boundary string the marker is used to know where each attachment starts and ends within the body. Within the body of the RFC-822 message, attachment headers are added for each attachment entity to let the client know what type of encoding is used for this part of the message. For example:

----=_NextPart_000_0024_01C09123.EE12B460
Content-Type: text/plain;
charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

This is a test

----=_NextPart_000_0024_01C09123.EE12B460
Content-Type: image/gif;
name="colors.gif"
Content-Transfer-Encoding: base64

R0lGODlh6wEXA/cAAP//////zP//mf//Zv//M///AP/M///MzP/Mmf/MZv/MM//MAP+Z//+ZzP+Z
some more base 64 code
d4yNfYB6dHyDgIKGe3Nsam1ocYWMj4BpaoWQj4J0dnBzhIl7fZGbiYCNioE=

------=_NextPart_000_0024_01C09123.EE12B460--

In version 2.0, to retrieve the Message headers you need to parse these headers. However, Dundas TCP/IP 3.0 and 4.0 had been enhanced with new classes that handled this functionality through CUT_Msg class And Message ActiveX control that allow you to retrive all headers based on type or name. Kindest Regards Dundas tech Support

[realJSOP]

Is it possible to get the latest version of 2.0? I'll understand if it's not, so don't feel pressured. :-)

[David Cunningham]

Hey John, Email tech@dundas.com and the guys will look after you. D