New Incoming mails in Trash folder

RESOLVED EXPIRED

Status

MailNews Core
Filters
--
critical
RESOLVED EXPIRED
13 years ago
9 years ago

People

(Reporter: Timothy Huang, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

Trunk
PowerPC
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041003
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041003

Since 10/2/2004 build, my incoming new mails end up in the Trash folder.

Reproducible: Always
Steps to Reproduce:
1. Get new mail
2. All new mails in Trash folder
3.

Actual Results:  
as describe above

Expected Results:  
Fix it. This is a very serious problem.

Comment 1

13 years ago
do you have any message filters? If so, can you attach them, and also your
prefs.js? thx.
(Reporter)

Comment 2

13 years ago
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
rv:1.8a5) Gecko/20041003
> Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
rv:1.8a5) Gecko/20041003
> 
> Since 10/2/2004 build, my incoming new mails end up in the Trash folder.
> 
> Reproducible: Always
> Steps to Reproduce:
> 1. Get new mail
> 2. All new mails in Trash folder
> 3.
> 
> Actual Results:  
> as describe above
> 
> Expected Results:  
> Fix it. This is a very serious problem.

(In reply to comment #1)
> do you have any message filters? If so, can you attach them, and also your
> prefs.js? thx.

How to get these files? i.e., in what folder?

Comment 3

13 years ago
in your user profile directory - I'm not sure where that is on OS/X, but if you
search for msgFilterRules.dat, that will be your msg filers file. And your
prefs.js will be in a parent directory of that.
Product: MailNews → Core
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
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.