After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 252422 - All new messages marked as "junk"
All new messages marked as "junk"
Status: VERIFIED DUPLICATE of bug 252378
Product: evolution
Classification: Applications
Component: Mailer
1.5.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-12-21 16:13 UTC by Frank Solensky
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Frank Solensky 2003-12-21 16:13:37 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
New Inbox messages are not visible.

Steps to reproduce the problem:
1. Select 'Send/Receive' icon
2. (New messages are downloaded, filtered)
3. 

Actual Results:
No difference in Inbox view

Expected Results:
New messages should be visible

How often does this happen? 
Always

Additional Information:
Some messages that were in the folder prior to migration are also not visible.
The messages are in the Inbox file.  After running a script that changes
1.4 ~/evolution mail files to links to ~/.evolution ones (after backing the
original ones up, of course), the messages are visible when running 1.4.5.
The common attribute between the invisible messages appears to be that the
"X-Evolution:" header field has bit 9 set in the second field (-0080).

1.5 build from HEAD source from yesterday evening.
Comment 1 Frank Solensky 2003-12-21 16:52:51 UTC
Looked at source: found "-0800" is currently 'junk' flag.
Changing to request that _some_ initial rule set be provided: starting
with nearly 100% false positives is not better than some ruleset that
risks a non-0% false positive.
I'm also curious as to why migrated messages were marked: were these
marked as junk when received in 1.4.x?

Comment 2 Frank Solensky 2003-12-21 17:04:37 UTC
Rechecked: it's only newly downloaded messages that are marked. 
Migrated ones are not.

I've been running spambayes (http://spambayes.sourceforge.net) on this
system for a while.  It inserts a set of "X-Spambayes-*:" lines into
the message header.  Is it possible that letters s-p-a-m in these
header field names are triggering a false positive?
Comment 3 Frank Solensky 2003-12-23 04:32:51 UTC
pipe_to_sa() called to invoke 'spam -c -p 7830'; calls execvp() which,
in turn, fails and returns an EFAULT error code.  Child terminates,
parent receives status code of 0xFF00.

Suggestion as to cause of execvp() failure?
Comment 4 Frank Solensky 2003-12-23 13:46:50 UTC

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