Please help with MIME issue

[Guest]

Hi all,

I am beating a dead horse on this one from my end and could use some
expertise assistance. I am running and Exchange 2003 server ans Outlook 2003
clients. We have a vendor sending us an email that when sent to other
Exchange servers outside of my organization are received fine. It also works
fine when sent to places like yahoo or AOL mail.

I have read some posts but still not sure how to resolve this one. Here is
the Content info if that helps and I am most greatful for any and all
assistance.

This is a multi-part message in MIME format.


--_______eG_Doc_Bndry______
Content-Type: multipart/alternative;
boundary="_______eG_Doc_Bndry1______"

--_______eG_Doc_Bndry1______
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

 

[Azul Funk]

Hi all,

I am beating a dead horse on this one from my end and could use some
expertise assistance. I am running and Exchange 2003 server ans Outlook
2003
clients. We have a vendor sending us an email that when sent to other
Exchange servers outside of my organization are received fine. It also
works
fine when sent to places like yahoo or AOL mail.

I have read some posts but still not sure how to resolve this one. Here is
the Content info if that helps and I am most greatful for any and all
assistance.

This is a multi-part message in MIME format.


--_______eG_Doc_Bndry______
Content-Type: multipart/alternative;
boundary="_______eG_Doc_Bndry1______"

--_______eG_Doc_Bndry1______
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Good Luck with that. I'll be watching this one carefully because I've been
trying to figure it out for a year now, and the smart money is on there not
being an answer.

All the best,

Azul

 

[Guest]

I disagree, I believe I am narrowing in in this one and will be glad to share
my results if they are worthwhille. I think it could be because there is no
"end" on the first boundary.

Steve

 

[Brian Tillman]

I disagree, I believe I am narrowing in in this one and will be glad
to share my results if they are worthwhille. I think it could be
because there is no "end" on the first boundary.

That's how multipart/alternative messages are structured. The boundaries
are

boundary 1
something
boundary 2
something
boundary 2
something
boundary 2 end
boundary 1
something else
boundary 1 end

At least for me, Outlook 2003 and Exchange 2003 receive these messages just
fine.

 

[Guest]

Brain,

thanks for the feedback. Do you see anything in the body of this message to
say why 99% of these types of messages come through fine for us and
regardless of who receives this one, it fails? Here is the complete message
minus any confidential info.


This is a multi-part message in MIME format.


--_______eG_Doc_Bndry______
Content-Type: multipart/alternative;
boundary="_______eG_Doc_Bndry1______"

--_______eG_Doc_Bndry1______
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Note: The content of your first Billing email was incomplete. The content
has been corrected and the email has been resent. Thank you for your
patience during this BETA testing phase. Please contact MZ with comments or
concerns.
<br><br>
Dear W Customer:
<br><br>
Your monthly bill is ready for account 0000000 for services at 0000 W
CLYDE,
Your

EFT


Credit Card


will be charged the amount due of $ 89.38 within three days of
receipt of this email.
<br><br>
To view your bill, please click on this link: <a
href="http://00000.company.net/scripts/em...com&ru=http://scp.servicecenter.mycompany.net">
View Your Bill </a>. If you have trouble accessing your account, please
feel free to contact W Customer Service Department at (888)000-0000.
<br><br>
Thank you,
<br>

--_______eG_Doc_Bndry1______
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Note: The content of your first Billing email was incomplete. The content
has been corrected and the email has been resent. Thank you for your
patience during this BETA testing phase. Please contact MZ with comments or
concerns.
<br><br>
Dear Customer:
<br><br>
Your monthly bill is ready for account WRES000000 for services at 0000 W
CLYDE , CO 802112718. Your

EFT


Credit Card


will be charged the amount due of $ 89.38 within three days of
receipt of this email.
<br><br>
To view your bill, please click on this link: <a
href="http://WCS00207.egain.net/scripts/e...com&ru=http://scp.servicecenter.mycompany.net">
View Your Bill </a>. If you have trouble accessing your account, please
feel free to contact Customer Service Department at (888)0000-0000.
<br><br>
Thank you,
<br>

--_______eG_Doc_Bndry1______--

 

[Brian Tillman]

thanks for the feedback. Do you see anything in the body of this
message to say why 99% of these types of messages come through fine
for us and regardless of who receives this one, it fails?

The only thing I see is that there is no end boundary to
"--_______eG_Doc_Bndry______", which should be
"--_______eG_Doc_Bndry______--"