Blank Email in Preview Pane

bjared · Post by **bjared** » Fri Dec 15, 2006 3:33 pm

I knew you guys would have an answer. Thanks for the quick response.
--Brian

bjared · Post by **bjared** » Fri Dec 15, 2006 3:51 pm

Well, there was no "content-disposition:" line, only these:

Content-Type: APPLICATION/PDF;

Name="Payment Advice_ 2000466524 from Scientific Atlanta.PDF"

Content-Transfer-Encoding: base64

dkarp · Post by **dkarp** » Fri Dec 15, 2006 4:05 pm

[quote user="bjared"]Well, there was no "content-disposition:" line, only these:

Content-Type: APPLICATION/PDF;

Name="Payment Advice_ 2000466524 from Scientific Atlanta.PDF"

Content-Transfer-Encoding: base64[/QUOTE]

Yeah, we've never seen a mailer that generates messages like that. File a bug in bugzilla and attach a sample message to it (you can mark the attachment as "private" if you'd like) and we'll try to make your oddball messages render better in the web client.

bjared · Post by **bjared** » Fri Dec 15, 2006 4:23 pm

[quote user="dkarp"]Yeah, we've never seen a mailer that generates messages like that. File a bug in bugzilla and attach a sample message to it (you can mark the attachment as "private" if you'd like) and we'll try to make your oddball messages render better in the web client.[/QUOTE]
Actually, I found a bug that is nearly identical to what I'm experiencing, and attached my two example e-mails to it. The bug number is 11513. Thanks for your assistance.
Ahh...It looks like both examples (from two completely different domain/companies) are both using SAP!
X-Mailer: SAP R/3 Internet Mail Gateway 4.6D5

X-Mailer: SAP Web Application Server 6.40
I imagine the person who gets these will be getting a lot more of them...
--Brian

dkarp · Post by **dkarp** » Fri Dec 15, 2006 4:42 pm

[quote user="bjared"]Actually, I found a bug that is nearly identical to what I'm experiencing, and attached my two example e-mails to it. The bug number is 11513. Thanks for your assistance.[/QUOTE]

I've actually moved your attachments to a new bug, bug 13055. Bug 11513 was a hot mess that referred to 3 different issues, and I figured it was best to kill it and have 3 separate bugs tracking the 3 issues.