message headers in email client no matter what

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
RESOLVED EXPIRED
15 years ago
12 years ago

People

(Reporter: Edward Hammerbeck, Unassigned)

Tracking

Trunk
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a; MultiZilla v1.1.32 final) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a; MultiZilla v1.1.32 final) Gecko/20030210

I supposedly have the email interface set so that email message headers are
minimal.  Yet no matter what I do they are super-verbose.  Here's an example of
what I'm seeing in the message preview pane.

Subject:
Fwd:heh heh
From:
Pookygrl58@aol.com
Date:
Thu, 27 Feb 2003 17:46:18 EST
To:
crystalkaymarie@yahoo.com, IanM80@aol.com, madkingkraz@yahoo.com,
novasoy@bellsouth.net, Goose633@aol.com, m_n_brown@msn.com, riddleeagle@yahoo.com
X-UIDL:
<103.2834930f.2b8fef3a@aol.com>
X-Mozilla-Status:
0001
X-Mozilla-Status2:
00000000
Return-Path:
<Pookygrl58@aol.com>
Received:
from imo-m02.mx.aol.com ([64.12.136.5]) by imf38bis.bellsouth.net (InterMail
vM.5.01.04.25 201-253-122-122-125-20020815) with ESMTP id
<20030227224833.JBGP16508.imf38bis.bellsouth.net@imo-m02.mx.aol.com> for
<novasoy@bellsouth.net>; Thu, 27 Feb 2003 17:48:33 -0500
Received:
from Pookygrl58@aol.com by imo-m02.mx.aol.com (mail_out_v34.21.) id
r.103.2834930f (26116); Thu, 27 Feb 2003 17:46:18 -0500 (EST)
Message-ID:
<103.2834930f.2b8fef3a@aol.com>
MIME-Version:
1.0
Content-Type:
multipart/mixed; boundary="part1_103.2834930f.2b8fef3a_boundary"
X-Mailer:
8.0 for Windows sub 234

Reproducible: Always

Steps to Reproduce:
1. Open Mozilla
2. Open mozilla email client
3. View an email message in the 3-pane view

Actual Results:  
in the header... 

Subject:
Fwd:heh heh
From:
Pookygrl58@aol.com
Date:
Thu, 27 Feb 2003 17:46:18 EST
To:
crystalkaymarie@yahoo.com, IanM80@aol.com, madkingkraz@yahoo.com,
novasoy@bellsouth.net, Goose633@aol.com, m_n_brown@msn.com, riddleeagle@yahoo.com
X-UIDL:
<103.2834930f.2b8fef3a@aol.com>
X-Mozilla-Status:
0001
X-Mozilla-Status2:
00000000
Return-Path:
<Pookygrl58@aol.com>
Received:
from imo-m02.mx.aol.com ([64.12.136.5]) by imf38bis.bellsouth.net (InterMail
vM.5.01.04.25 201-253-122-122-125-20020815) with ESMTP id
<20030227224833.JBGP16508.imf38bis.bellsouth.net@imo-m02.mx.aol.com> for
<novasoy@bellsouth.net>; Thu, 27 Feb 2003 17:48:33 -0500
Received:
from Pookygrl58@aol.com by imo-m02.mx.aol.com (mail_out_v34.21.) id
r.103.2834930f (26116); Thu, 27 Feb 2003 17:46:18 -0500 (EST)
Message-ID:
<103.2834930f.2b8fef3a@aol.com>
MIME-Version:
1.0
Content-Type:
multipart/mixed; boundary="part1_103.2834930f.2b8fef3a_boundary"
X-Mailer:
8.0 for Windows sub 234

Expected Results:  
a very brief header listing just the sender's email and perhaps the subject

Pinball theme.  I am using enigmail.

Comment 1

15 years ago
This happens when you have selected View->Headers->Normal?
Please check if the bug also appears when using default themes.
(Reporter)

Comment 2

15 years ago
Yes, that is true.  Header settings set to normal and in all themes, including
classic, this is the case.

Comment 3

15 years ago
Which version of enigmail are you using?
Does the bug appear also in a new profile?
(Reporter)

Comment 4

15 years ago
Enigmail 0.73.0

It seems to exist for all profiles.

Comment 5

15 years ago
I am also having this problem with both 1.2.1 and 1.3b. 

Comment 6

15 years ago
ben schmitz:
Are you too using Enigmail?
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/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.