MIME format in pop3 email
 

I received 2 emails which were not in the usual plain/rich text BUT in MIME
format like that below;

I have scoured the net for a decoder/translator but was unsuccessful.

CAN SOME PLEASE HELP.


""This is a multi-part message in MIME format.
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="_----------=_1176486050129256";
charset=UTF-8

--_----------=_1176486050129256
Content-Type: application/octet-stream; name=email_text.txt
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="email_text.txt"

DQpEZWFyIEN1c3RvbWVyLA0KDQpUaGFuayB5b3UgZm9yIHlvdX IgcmVjZW50
IGVucXVpcnkgcmVnYXJkaW5nIHlvdXIgQ2Fub24gcHJvZHVjdC 4gDQoNCllv
dXIgcXVlcnkgaGFzIGJlZW4gc2VudCB0byB0aGUgYXBwcm9wcm lhdGUgZ3Jv
dXAgYW5kIGlzIGN1cnJlbnRseSB1bmRlciBpbnZlc3RpZ2F0aW 9uLg0KDQoN
CllvdXJzIHNpbmNlcmVseSwNCkNhbm9uIFN1cHBvcnQgQ2VudH JlDQpTaG91
bGQgb3VyIGFuc3dlciBub3QgZnVsbHkgcmVzb2x2ZSB5b3VyIH Byb2JsZW0s
IHBsZWFzZSBmZWVsIGZyZWUgdG8gZWl0aGVyIHJlLXN1Ym1pdC BhIG5ldyBx
dWVyeSBieSBjbGlja2luZyBoZXJlLCBvciBhbHRlcm5hdGl2ZW x5IGNhbGwg
b3VyIHN1cHBvcnQgaGVscGRlc2sgYXQgMDg3MDUgMTQzIDcyMy BNb25kYXkg
dG8gRnJpZGF5IGZyb20gOTowMEFNIHRvIDU6MzBQTSBzdGF0aW 5nIHRoZSA3
IGRpZ2l0IHJlZmVyZW5jZSBudW1iZXIgaW4gdGhlIHN1YmplY3 Qgb2YgdGhp
cyBlbWFpbC4NCg0KV2UgYWltIHRvIGFuc3dlciBxdWVyaWVzIG FzIHNvb24g
YXMgcG9zc2libGUuIFJlc3BvbnNlcyBvbiBhdmVyYWdlIHRha2 UgMiB0byAz
IGJ1c2luZXNzIGRheXMgKG9yIHRoZSBuZXh0IHdvcmtpbmcgZG F5IGlmIHN1
Ym1pdHRpbmcgb24gYSB3ZWVrZW5kIG9yIHB1YmxpYyBob2xpZG F5KS4NCg0K
DQoNCqkgQ29weXJpZ2h0IDIwMDUgIHwgIFRlcm1zIGFuZCBDb2 5kaXRpb25z

--_----------=_1176486050129256
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.01 (F2.74; A1.74; B3.07; Q3.07)
Date: Fri, 13 Apr 2007 17:40:50 UT
Content-Type: multipart/related; boundary="_----------=_1176486050129257";
charset=UTF-8

--_----------=_1176486050129257
Content-Length: 3260
Content-Type: text/html
Content-Transfer-Encoding: binary
Content-Disposition: inline

html
meta http-equiv="Content-Type" content="text/html; charset=UTF-8"
style type="text/css"
body {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
margin-left : 0px;
margin-right: 0px;
margin-top : 0px;
margin-bottom: 0px;
}

td {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
margin-left : 0px;
margin-right: 0px;
margin-top : 0px;
margin-bottom: 0px;
}

a {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration : none;
}

a:hover {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:none;
}

a:active {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:none;
}

a.formatlink {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration: none
}

a.formatlink:hover {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:underline;
}

a.formatlink:active {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:underline;
}

..footer{
font-family: Verdana, Geneva, Arial, Helvetica, sans-serif;
font-size : 10px;
color : #999999;
background-color : #e6e6e6;
}

/style
body
table border=0 width=620
tr
td width=50% align="left"img
src="https://self-service.canon-europe.com/ce/pages/docs/gcc_outbound_email_you_can_canon.gif"/td
td width=50% align="right"img
src="https://self-service.canon-europe.com/ce/pages/docs/gcc_outbound_email_i_canon_support_centre.jpg"/td/tr
tr
td colspan="2"
brbrbr
Dear Customer,
brbrbr""

MIME format in pop3 email
 

Are you seeing that in the normal message reading window or when looking
at the message source?

If you are seeing that in the message reading window, it means that the
MIME headers in the message are corrupted. One cause of that is an
anti-virus program scanning e-mail, or an anti-spam program.

It could also be a problem on the sender's end in not properly
formatting the message.

It's also possible to repair the messages to make them readable. To do
that, you need to File, Save As the message to an EML file. Then open
the EML file in Notepad to fix it. Then you can double click the
repaired file to open in an OE message reading window or drag it back to
an OE folder.

The exact fix depends on the what exactly is wrong. There are two
common problems. One is an extraneous blank line inserted in the
header. The first blank line indicates end of the header and the start
of the message body. The other common problem is corruption of the
boundary strings that identity the various sections of the message.
This is more complicated to straighten out.

If you want to read up on this, see:
ftp://ftp.isi.edu/in-notes/rfc2822.txt
ftp://ftp.isi.edu/in-notes/rfc2045.txt

IF this is a one time problem, and the messages are important to you,
you can e-mail them to me and I'll fix them for you. It's best if you
zip the message so that I get an exact copy of it. To do that, do a
File, Save As to an EML file of a problem message. Then Right click the
saved EML file and select Send To, Compressed (zipped) folder. Then
e-mail me the resulting ZIP file. Alternately, you can do a Message,
Forward As Attachment of a problem message. This is not as good as the
zip file since the headers can be modified in transit which may obscure
the problem. A simple Forward is worthless since it does not include
the headers.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"Donnie Darko" wrote in message
...
I received 2 emails which were not in the usual plain/rich text BUT in
MIME format like that below;

I have scoured the net for a decoder/translator but was unsuccessful.

CAN SOME PLEASE HELP.


""This is a multi-part message in MIME format.
Mime-Version: 1.0
Content-Type: multipart/mixed;
boundary="_----------=_1176486050129256"; charset=UTF-8

--_----------=_1176486050129256
Content-Type: application/octet-stream; name=email_text.txt
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="email_text.txt"

DQpEZWFyIEN1c3RvbWVyLA0KDQpUaGFuayB5b3UgZm9yIHlvdX IgcmVjZW50
IGVucXVpcnkgcmVnYXJkaW5nIHlvdXIgQ2Fub24gcHJvZHVjdC 4gDQoNCllv
dXIgcXVlcnkgaGFzIGJlZW4gc2VudCB0byB0aGUgYXBwcm9wcm lhdGUgZ3Jv
dXAgYW5kIGlzIGN1cnJlbnRseSB1bmRlciBpbnZlc3RpZ2F0aW 9uLg0KDQoN
CllvdXJzIHNpbmNlcmVseSwNCkNhbm9uIFN1cHBvcnQgQ2VudH JlDQpTaG91
bGQgb3VyIGFuc3dlciBub3QgZnVsbHkgcmVzb2x2ZSB5b3VyIH Byb2JsZW0s
IHBsZWFzZSBmZWVsIGZyZWUgdG8gZWl0aGVyIHJlLXN1Ym1pdC BhIG5ldyBx
dWVyeSBieSBjbGlja2luZyBoZXJlLCBvciBhbHRlcm5hdGl2ZW x5IGNhbGwg
b3VyIHN1cHBvcnQgaGVscGRlc2sgYXQgMDg3MDUgMTQzIDcyMy BNb25kYXkg
dG8gRnJpZGF5IGZyb20gOTowMEFNIHRvIDU6MzBQTSBzdGF0aW 5nIHRoZSA3
IGRpZ2l0IHJlZmVyZW5jZSBudW1iZXIgaW4gdGhlIHN1YmplY3 Qgb2YgdGhp
cyBlbWFpbC4NCg0KV2UgYWltIHRvIGFuc3dlciBxdWVyaWVzIG FzIHNvb24g
YXMgcG9zc2libGUuIFJlc3BvbnNlcyBvbiBhdmVyYWdlIHRha2 UgMiB0byAz
IGJ1c2luZXNzIGRheXMgKG9yIHRoZSBuZXh0IHdvcmtpbmcgZG F5IGlmIHN1
Ym1pdHRpbmcgb24gYSB3ZWVrZW5kIG9yIHB1YmxpYyBob2xpZG F5KS4NCg0K
DQoNCqkgQ29weXJpZ2h0IDIwMDUgIHwgIFRlcm1zIGFuZCBDb2 5kaXRpb25z

--_----------=_1176486050129256
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.01 (F2.74; A1.74; B3.07; Q3.07)
Date: Fri, 13 Apr 2007 17:40:50 UT
Content-Type: multipart/related;
boundary="_----------=_1176486050129257"; charset=UTF-8

--_----------=_1176486050129257
Content-Length: 3260
Content-Type: text/html
Content-Transfer-Encoding: binary
Content-Disposition: inline

html
meta http-equiv="Content-Type" content="text/html; charset=UTF-8"
style type="text/css"
body {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
margin-left : 0px;
margin-right: 0px;
margin-top : 0px;
margin-bottom: 0px;
}

td {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
margin-left : 0px;
margin-right: 0px;
margin-top : 0px;
margin-bottom: 0px;
}

a {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration : none;
}

a:hover {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:none;
}

a:active {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:none;
}

a.formatlink {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration: none
}

a.formatlink:hover {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:underline;
}

a.formatlink:active {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:underline;
}

.footer{
font-family: Verdana, Geneva, Arial, Helvetica, sans-serif;
font-size : 10px;
color : #999999;
background-color : #e6e6e6;
}

/style
body
table border=0 width=620
tr
td width=50% align="left"img
src="https://self-service.canon-europe.com/ce/pages/docs/gcc_outbound_email_you_can_canon.gif"/td
td width=50% align="right"img
src="https://self-service.canon-europe.com/ce/pages/docs/gcc_outbound_email_i_canon_support_centre.jpg"/td/tr
tr
td colspan="2"
brbrbr
Dear Customer,
brbrbr""

MIME format in pop3 email
 

Hi
I am seeing the message in the normal message reading window. Also how do
you repair the mail if you open in notepad?? Don't understand.

I am using GRISOFT AVG as the antivirus. However, all messages apart from
these 2 have been in normal format - i.e. no problem.

Hear from you soon.
Rgds
Roman

"Michael Santovec" wrote in message
...
Are you seeing that in the normal message reading window or when looking
at the message source?

If you are seeing that in the message reading window, it means that the
MIME headers in the message are corrupted. One cause of that is an
anti-virus program scanning e-mail, or an anti-spam program.

It could also be a problem on the sender's end in not properly formatting
the message.

It's also possible to repair the messages to make them readable. To do
that, you need to File, Save As the message to an EML file. Then open the
EML file in Notepad to fix it. Then you can double click the repaired
file to open in an OE message reading window or drag it back to an OE
folder.

The exact fix depends on the what exactly is wrong. There are two common
problems. One is an extraneous blank line inserted in the header. The
first blank line indicates end of the header and the start of the message
body. The other common problem is corruption of the boundary strings that
identity the various sections of the message. This is more complicated to
straighten out.

If you want to read up on this, see:
ftp://ftp.isi.edu/in-notes/rfc2822.txt
ftp://ftp.isi.edu/in-notes/rfc2045.txt

IF this is a one time problem, and the messages are important to you, you
can e-mail them to me and I'll fix them for you. It's best if you zip
the message so that I get an exact copy of it. To do that, do a File,
Save As to an EML file of a problem message. Then Right click the saved
EML file and select Send To, Compressed (zipped) folder. Then e-mail me
the resulting ZIP file. Alternately, you can do a Message, Forward As
Attachment of a problem message. This is not as good as the zip file
since the headers can be modified in transit which may obscure the
problem. A simple Forward is worthless since it does not include the
headers.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"Donnie Darko" wrote in message
...
I received 2 emails which were not in the usual plain/rich text BUT in
MIME format like that below;

I have scoured the net for a decoder/translator but was unsuccessful.

CAN SOME PLEASE HELP.


""This is a multi-part message in MIME format.
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="_----------=_1176486050129256";
charset=UTF-8

--_----------=_1176486050129256
Content-Type: application/octet-stream; name=email_text.txt
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="email_text.txt"

DQpEZWFyIEN1c3RvbWVyLA0KDQpUaGFuayB5b3UgZm9yIHlvdX IgcmVjZW50
IGVucXVpcnkgcmVnYXJkaW5nIHlvdXIgQ2Fub24gcHJvZHVjdC 4gDQoNCllv
dXIgcXVlcnkgaGFzIGJlZW4gc2VudCB0byB0aGUgYXBwcm9wcm lhdGUgZ3Jv
dXAgYW5kIGlzIGN1cnJlbnRseSB1bmRlciBpbnZlc3RpZ2F0aW 9uLg0KDQoN
CllvdXJzIHNpbmNlcmVseSwNCkNhbm9uIFN1cHBvcnQgQ2VudH JlDQpTaG91
bGQgb3VyIGFuc3dlciBub3QgZnVsbHkgcmVzb2x2ZSB5b3VyIH Byb2JsZW0s
IHBsZWFzZSBmZWVsIGZyZWUgdG8gZWl0aGVyIHJlLXN1Ym1pdC BhIG5ldyBx
dWVyeSBieSBjbGlja2luZyBoZXJlLCBvciBhbHRlcm5hdGl2ZW x5IGNhbGwg
b3VyIHN1cHBvcnQgaGVscGRlc2sgYXQgMDg3MDUgMTQzIDcyMy BNb25kYXkg
dG8gRnJpZGF5IGZyb20gOTowMEFNIHRvIDU6MzBQTSBzdGF0aW 5nIHRoZSA3
IGRpZ2l0IHJlZmVyZW5jZSBudW1iZXIgaW4gdGhlIHN1YmplY3 Qgb2YgdGhp
cyBlbWFpbC4NCg0KV2UgYWltIHRvIGFuc3dlciBxdWVyaWVzIG FzIHNvb24g
YXMgcG9zc2libGUuIFJlc3BvbnNlcyBvbiBhdmVyYWdlIHRha2 UgMiB0byAz
IGJ1c2luZXNzIGRheXMgKG9yIHRoZSBuZXh0IHdvcmtpbmcgZG F5IGlmIHN1
Ym1pdHRpbmcgb24gYSB3ZWVrZW5kIG9yIHB1YmxpYyBob2xpZG F5KS4NCg0K
DQoNCqkgQ29weXJpZ2h0IDIwMDUgIHwgIFRlcm1zIGFuZCBDb2 5kaXRpb25z

--_----------=_1176486050129256
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.01 (F2.74; A1.74; B3.07; Q3.07)
Date: Fri, 13 Apr 2007 17:40:50 UT
Content-Type: multipart/related;
boundary="_----------=_1176486050129257"; charset=UTF-8

--_----------=_1176486050129257
Content-Length: 3260
Content-Type: text/html
Content-Transfer-Encoding: binary
Content-Disposition: inline

html
meta http-equiv="Content-Type" content="text/html; charset=UTF-8"
style type="text/css"
body {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
margin-left : 0px;
margin-right: 0px;
margin-top : 0px;
margin-bottom: 0px;
}

td {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
margin-left : 0px;
margin-right: 0px;
margin-top : 0px;
margin-bottom: 0px;
}

a {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration : none;
}

a:hover {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:none;
}

a:active {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:none;
}

a.formatlink {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration: none
}

a.formatlink:hover {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:underline;
}

a.formatlink:active {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:underline;
}

.footer{
font-family: Verdana, Geneva, Arial, Helvetica, sans-serif;
font-size : 10px;
color : #999999;
background-color : #e6e6e6;
}

/style
body
table border=0 width=620
tr
td width=50% align="left"img
src="https://self-service.canon-europe.com/ce/pages/docs/gcc_outbound_email_you_can_canon.gif"/td
td width=50% align="right"img
src="https://self-service.canon-europe.com/ce/pages/docs/gcc_outbound_email_i_canon_support_centre.jpg"/td/tr
tr
td colspan="2"
brbrbr
Dear Customer,
brbrbr""

MIME format in pop3 email
 

I got your 2 problem messages, fixed both messages and sent them back to
you.

For the benefit of others, I listed below what I found wrong with them.

The problem in both messages was the following text in the message:

X-Antivirus: AVG for E-mail 7.5.446 [269.3.0/758]
X-Text-Classification: personal
X-POPFile-Link: http://127.0.0.1:8080/jump_to_message?view=344

This is a multi-part message in MIME format.
Mime-Version: 1.0

There should not have been the blank after the 3rd line. It should have
been:

X-Antivirus: AVG for E-mail 7.5.446 [269.3.0/758]
X-Text-Classification: personal
X-POPFile-Link: http://127.0.0.1:8080/jump_to_message?view=344
This is a multi-part message in MIME format.
Mime-Version: 1.0

The fix involved opening the EML file in Notepad, removing the blank
line, then saving it again.

The culprit is probably POPFile, although it could be the interaction
between that and AVG anti-virus.

There is something else unusual about the message. The line
This is a multi-part message in MIME format.
should not be in the header. The normal place for it is in the message
body. It should be more like:

Message-Id:
X-Antivirus: AVG for E-mail 7.5.446 [269.3.0/758]
X-Text-Classification: personal
X-POPFile-Link: http://127.0.0.1:8080/jump_to_message?view=347
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="_----------=_1176488840131822";
charset=UTF-8

This is a multi-part message in MIME format.

--_----------=_1176488840131822
Content-Type: application/octet-stream; name=email_text.txt
Content-Transfer-Encoding: base64

As a start, I would disable the AVG E-mail scanning. As long as your
anti-virus software is set to scan files as they are opened, scanning
e-mail as it downloads or sends is unnecessary and prone to problems.
In the case of AVG, you need to uninstall it, then reinstall using a
Custom install and uncheck the e-mail component. Just disabling the
e-mail scanning from the AVG control panel doesn't really remove the
scanning.


--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"Donnie Darko" wrote in message
...
Hi
I am seeing the message in the normal message reading window. Also
how do
you repair the mail if you open in notepad?? Don't understand.

I am using GRISOFT AVG as the antivirus. However, all messages apart
from
these 2 have been in normal format - i.e. no problem.

Hear from you soon.
Rgds
Roman

"Michael Santovec" wrote in message
...
Are you seeing that in the normal message reading window or when
looking at the message source?

If you are seeing that in the message reading window, it means that
the MIME headers in the message are corrupted. One cause of that is
an anti-virus program scanning e-mail, or an anti-spam program.

It could also be a problem on the sender's end in not properly
formatting the message.

It's also possible to repair the messages to make them readable. To
do that, you need to File, Save As the message to an EML file. Then
open the EML file in Notepad to fix it. Then you can double click
the repaired file to open in an OE message reading window or drag it
back to an OE folder.

The exact fix depends on the what exactly is wrong. There are two
common problems. One is an extraneous blank line inserted in the
header. The first blank line indicates end of the header and the
start of the message body. The other common problem is corruption of
the boundary strings that identity the various sections of the
message. This is more complicated to straighten out.

If you want to read up on this, see:
ftp://ftp.isi.edu/in-notes/rfc2822.txt
ftp://ftp.isi.edu/in-notes/rfc2045.txt

IF this is a one time problem, and the messages are important to you,
you can e-mail them to me and I'll fix them for you. It's best if
you zip the message so that I get an exact copy of it. To do that,
do a File, Save As to an EML file of a problem message. Then Right
click the saved EML file and select Send To, Compressed (zipped)
folder. Then e-mail me the resulting ZIP file. Alternately, you can
do a Message, Forward As Attachment of a problem message. This is
not as good as the zip file since the headers can be modified in
transit which may obscure the problem. A simple Forward is worthless
since it does not include the headers.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"Donnie Darko" wrote in message
...
I received 2 emails which were not in the usual plain/rich text BUT
in MIME format like that below;

I have scoured the net for a decoder/translator but was
unsuccessful.

CAN SOME PLEASE HELP.


""This is a multi-part message in MIME format.
Mime-Version: 1.0
Content-Type: multipart/mixed;
boundary="_----------=_1176486050129256"; charset=UTF-8

--_----------=_1176486050129256
Content-Type: application/octet-stream; name=email_text.txt
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="email_text.txt"

DQpEZWFyIEN1c3RvbWVyLA0KDQpUaGFuayB5b3UgZm9yIHlvdX IgcmVjZW50
IGVucXVpcnkgcmVnYXJkaW5nIHlvdXIgQ2Fub24gcHJvZHVjdC 4gDQoNCllv
dXIgcXVlcnkgaGFzIGJlZW4gc2VudCB0byB0aGUgYXBwcm9wcm lhdGUgZ3Jv
dXAgYW5kIGlzIGN1cnJlbnRseSB1bmRlciBpbnZlc3RpZ2F0aW 9uLg0KDQoN
CllvdXJzIHNpbmNlcmVseSwNCkNhbm9uIFN1cHBvcnQgQ2VudH JlDQpTaG91
bGQgb3VyIGFuc3dlciBub3QgZnVsbHkgcmVzb2x2ZSB5b3VyIH Byb2JsZW0s
IHBsZWFzZSBmZWVsIGZyZWUgdG8gZWl0aGVyIHJlLXN1Ym1pdC BhIG5ldyBx
dWVyeSBieSBjbGlja2luZyBoZXJlLCBvciBhbHRlcm5hdGl2ZW x5IGNhbGwg
b3VyIHN1cHBvcnQgaGVscGRlc2sgYXQgMDg3MDUgMTQzIDcyMy BNb25kYXkg
dG8gRnJpZGF5IGZyb20gOTowMEFNIHRvIDU6MzBQTSBzdGF0aW 5nIHRoZSA3
IGRpZ2l0IHJlZmVyZW5jZSBudW1iZXIgaW4gdGhlIHN1YmplY3 Qgb2YgdGhp
cyBlbWFpbC4NCg0KV2UgYWltIHRvIGFuc3dlciBxdWVyaWVzIG FzIHNvb24g
YXMgcG9zc2libGUuIFJlc3BvbnNlcyBvbiBhdmVyYWdlIHRha2 UgMiB0byAz
IGJ1c2luZXNzIGRheXMgKG9yIHRoZSBuZXh0IHdvcmtpbmcgZG F5IGlmIHN1
Ym1pdHRpbmcgb24gYSB3ZWVrZW5kIG9yIHB1YmxpYyBob2xpZG F5KS4NCg0K
DQoNCqkgQ29weXJpZ2h0IDIwMDUgIHwgIFRlcm1zIGFuZCBDb2 5kaXRpb25z

--_----------=_1176486050129256
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.01 (F2.74; A1.74; B3.07; Q3.07)
Date: Fri, 13 Apr 2007 17:40:50 UT
Content-Type: multipart/related;
boundary="_----------=_1176486050129257"; charset=UTF-8

--_----------=_1176486050129257
Content-Length: 3260
Content-Type: text/html
Content-Transfer-Encoding: binary
Content-Disposition: inline

html
meta http-equiv="Content-Type" content="text/html; charset=UTF-8"
style type="text/css"
body {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
margin-left : 0px;
margin-right: 0px;
margin-top : 0px;
margin-bottom: 0px;
}

td {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
margin-left : 0px;
margin-right: 0px;
margin-top : 0px;
margin-bottom: 0px;
}

a {
color : #666666;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration : none;
}

a:hover {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:none;
}

a:active {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:none;
}

a.formatlink {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration: none
}

a.formatlink:hover {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:underline;
}

a.formatlink:active {
color : #ED252A;
font-family : Verdana, Arial, Helvetica, sans-serif;
font-size : 11px;
text-decoration:underline;
}

.footer{
font-family: Verdana, Geneva, Arial, Helvetica, sans-serif;
font-size : 10px;
color : #999999;
background-color : #e6e6e6;
}

/style
body
table border=0 width=620
tr
td width=50% align="left"img
src="https://self-service.canon-europe.com/ce/pages/docs/gcc_outbound_email_you_can_canon.gif"/td
td width=50% align="right"img
src="https://self-service.canon-europe.com/ce/pages/docs/gcc_outbound_email_i_canon_support_centre.jpg"/td/tr
tr
td colspan="2"
brbrbr
Dear Customer,
brbrbr""