I typed a message in mozilla/linux using the html compose window, with my pref set to always convert to plaintext on send. One recipient sent me this. Is it the format=flowed that's confusing OE? I've edited out the Received-by headers. ---------------------- My mailer (OE Mac version 5) said "Some text in this message is in a language your computer cannot display". Other than that it looked fine. Here are all the headers in case they're useful: > Return-Path: <email@example.com> > Received: from mx1.znet.com (mx.znet.com [18.104.22.168]) > by sj.znet.com (8.10.0/8.10.0/jjb-sj) with ESMTP id e2A09SE08075; > Thu, 9 Mar 2000 16:09:28 -0800 (PST) > Message-ID: <38C83D19.firstname.lastname@example.org> > Date: Thu, 09 Mar 2000 16:08:57 -0800 > From: email@example.com (Akkana Peck) > User-Agent: Mozilla/5.0 (X11; N; Linux 2.2.5-22 i686; en-US; m14) > Netscape6/6.0b1 > X-Accept-Language: en > MIME-Version: 1.0 > To: firstname.lastname@example.org > Subject: Re: [PSC] PSC Night > References: <email@example.com> > Content-Type: text/plain; charset=us-ascii; format=flowed > Content-Transfer-Encoding: 8bit > X-MIME-Autoconverted: from quoted-printable to 8bit by seds.lpl.arizona.edu id > RAA08762 > Sender: firstname.lastname@example.org > Precedence: bulk > Reply-To: email@example.com > X-UIDL: 6a8f918e313807c76dfdbd9b10de7fd2
reassign to rhp
Assignee: ducarroz → rhp
I know that Outlook Express can deal with our format=flowed/quoted printable email messages...I test with OE from time to time on MIME interoperability. I think this is the culprit: X-MIME-Autoconverted: from quoted-printable to 8bit by seds.lpl.arizona.edu id Looks like they have some sort of service to convert quoted printable before it hits the desktop. I'm suspect of this service. - rhp
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
Nope. You're right that I had my mozilla pref set for quoted-printable, whereas my 4.x pref was set to as-is. So I changed the mozilla pref, and tried again to send to the same user. He still sees the error message, and the headers now no longer include the line about autoconversion. Note that I send mail to this user all the time with 4.x, and it works fine. I expect mozilla mail to be able to send to any user I could converse with with Netscape (otherwise I can't use mozilla instead of Netscape).
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Rich: you mention testing with Outlook Express, but is it possible that you're talking about the Windows version? OE/Mac is a completely different program, very popular among Mac users.
Sorry, but I can't debug without the source to the message as your friend is receiving it. The problem is that we are adhearing to the standard. If OE on Mac isn't smart enough to deal with it, there is little I can do. - rhp
Status: REOPENED → ASSIGNED
What level of source do you need to see? My friend thought that the headers would tell us what we need to know (remember, this is a plaintext message, so there's no html source or mime multipart headers to deal with). Let me know what you need, and I'll ask for it ...
So is the bug that we're sending QP when we shouldn't? Or than the QP we generate is wrong? Seems like this should be easy enough to verify, given the body of the message that their QP -> 8bit translator started with. Or some other message which demonstrates the problem, if you (Akkana) prefer.
My uneducated guess is that OE on Mac is barfing on valid (but not common) format=flowed/quoted printable messages. I've asked for the source of the message from the person on the mac to verify. - rhp
It's not just quoted printable; this happened after I switched my pref to "send as is". I'm not sure what's triggering the problem. I'll append message source as soon as I get some.
Re my last comment: it looks like our mail server translated my message to quoted-printable even though I didn't send it that way. ?? In looking at the headers from these various messages, I notice that some say 8bit and some say 7bit, though I never use any characters beyond 7-bit ascii when I'm typing the message. I haven't found any regularity to which messages say 8 vs 7 bits, or between the number of bits and whether the message will cause OE/Mac to complain. Why is it sometimes 7 and sometimes 8, and could this be relevant to this bug?
Ok...how about this... Akkana, can you take look in your sent folder and save the copy of the messages that were sent. Maybe I can tell from the original copies what is going on. There is no reason we should be sending 8-bit unless we really need to. - rhp
Hi Akkana, Let me know if you can dig those messages up from your Sent folder and I will take a look at them. - rhp
Target Milestone: M18
Sorry, forgot to do that yesterday. I've attached the message from my Sent folder. Any idea what's up with all the newlines between the headers of the forwarded message?
Hi Akkana, Any idea if this problem is still showing up. Not sure I'll be able to do much with this one. - rhp
Target Milestone: M19 → Future
I am using OE 5.01 and just used Perl to send myself the attachment, and there was no error message for me.
reassigning to ducarroz
Assignee: rhp → ducarroz
Status: ASSIGNED → NEW
Assignee: ducarroz → nobody
Status: ASSIGNED → NEW
QA Contact: lchiang → composition
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.