If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

line started with ">from " is not displayed as quoted

NEW
Unassigned

Status

SeaMonkey
MailNews: Message Display
13 years ago
9 years ago

People

(Reporter: Reinhold Jordan, Unassigned)

Tracking

(Depends on: 2 bugs)

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040514
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040514

Lines started with ">" should displayed in another font and color. But if there
is no space and the first word is "from" this dosn't work

Reproducible: Always
Steps to Reproduce:
1. compose a new mail with
>by x
>from x
>to x
2. save it
3. display it

Actual Results:  
1st and 3rd line is displayed as quoted. 2nd line not

Expected Results:  
all lines should displayed quoted

Comment 1

13 years ago
related: bug 121946, bug 121947

If i read this right, it's actually contradicted by bug 121947, which says:
">From now on" should be unescaped to "From now on".

I may be more than ordinarily confused, of course.
Adding this a blocker for 121947 (under great doubt!)
Blocks: 121947

Comment 2

13 years ago
This bug describes the how the *user* sees a message now, and how
the user should see a message in future.

The bugs 121947,121946 describe how a mail should be converted
into mbox format, as it comes in from a mail server or the mail editor, and how
it should be decoded  from mbox format for display to the user.
Taken together these two bugs should satisfy the current bug.

Thefore...maybe 121947,121946 should block this bug?

Updated

13 years ago
No longer blocks: 121947
Severity: trivial → normal
Depends on: 121946, 121947
OS: Linux → All
Hardware: PC → All
Summary: line started with ">from " is not displyed as quoted → line started with ">from " is not displayed as quoted
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
(Reporter)

Comment 4

12 years ago
Ok, I download and install Thunderbird version 1.5 Beta 1 (20050908) and retest
this bug. And I can reproduce it, but not the same way. If I write a line
starting with ">", Thunderbird add a space before the ">". So I send a mail to
Thunderbird from command line:

# mail <account>
Subject: test
>by x
>from x
>to x
.
Cc:

And I get the same result

Updated

12 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 5

12 years ago
(In reply to comment #4)
> If I write a line starting with ">", Thunderbird add a space before the ">".

Yes, it does that; that's a format=flowed convention.  In order to bypass it, 
you need to either turn f=f off (generally not recommended, but see bug 168420) 
or use   Edit | Paste as Quotation

i.e. In the compose window, type:
===
by x
from x
to x
===
Select the text; Cut; Paste as Quotation

The fact is, the "quoted" display is *supposed* to be limited to the actual 
message you're quoting.  It appears you want to have headers as part of the 
quoted text; that's bug 209632.

Comment 6

12 years ago
(In reply to comment #5)
> It appears you want to have headers as part of the 
> quoted text; that's bug 209632.

Wrong bug -- it's bug 218258.

Comment 7

12 years ago
But, with "send f=f" turned off, the results I see are more-or-less consistent 
with the original report: the line beginning with    >From    is shown as

>From    [with the '>' symbol]

but not quoted, whereas the other lines are shown as quoted (in blue).
(With  mail.quoted_graphical  set 'true', the quoted lines appear with a 
vertical bar but no '>' character; with the pref set 'false', the quoted lines 
appear with a vertical bar *and* a '>' character (TB 1.6a1).  This second case 
seems wrong.)

Here's a workaround, if you'd rather go without f=f:
  >from:    <--- use a colon
With the colon in place, the line is handled normally; the mbox divider string 
is "From ".
You need to log in before you can comment on or make changes to this bug.