Jürgen Kreileder Reporter
	Description • 20 years ago

User-Agent:       Mozilla/5.0 (X11; U; Linux ppc64; en-US; rv:1.7.7) Gecko/20050418 Galeon/1.3.20 (Debian package 1.3.20-1)
Build Identifier: Thunderbird 1.0.2

Currently moving mails to a junk folder after marking them as junk does not work
automatically if adaptive filtering is disabled.  I think this should work
without enabling adaptive filtering.

Rationale: My mail already gets checked by SpamAssassin on the receiving SMTP
host. My IMAP server then sorts accepted SPAM mails into a designated folder
(Spam/Detected). If there was a junk mail not identified as such, I can move it
to a junk folder on the IMAP server (Spam/Learn as Spam); SpamAssassin learns
from that folder once per hour.

Currently I have to move unidentified Spam mails to the 'Spam/Learn as Spam'
folder manually. It would nice if just marking a mail as junk in Thunderbird did
that automatically.

Reproducible: Always

Steps to Reproduce:
1. Disable adaptive filtering
2. Mark a mail as junk


Actual Results:  
Mail stays in current folder

Expected Results:  
Mail gets moved the junk folder

	zug_treno
	Comment 1 • 20 years ago

Related to/duplicate of bug 279018?

	Jürgen Kreileder Reporter
	Comment 2 • 20 years ago

Yeah, looks related.

When adaptive filtering is enabled (I neither need nor want this feature) it
works like expected (ie. messages manually marked as junk get moved to the junk
folder).

Without adaptive filterting, messages manually marked as junk don't get moved.

	Gervase Markham [:gerv]
	Comment 3 • 19 years ago

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/

	Jürgen Kreileder Reporter
	Comment 4 • 19 years ago

Problem still exists with 1.5 beta 1.

	Thomas Bertels
	Comment 5 • 19 years ago

Please mark this bug as duplicate of bug 279018.

	David :Bienvenu
	Comment 6 • 19 years ago

*** This bug has been marked as a duplicate of 279018 ***