Bug 3432 - False Positive with FORGED_JUNO_RCVD rule
Summary: False Positive with FORGED_JUNO_RCVD rule
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (Eval Tests) (show other bugs)
Version: 2.63
Hardware: Other other
: P5 normal
Target Milestone: 3.1.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-27 07:32 UTC by Jeff Seifert
Modified: 2005-01-26 13:32 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Seifert 2004-05-27 07:32:21 UTC 
A user has been complaining of getting a false positive on e-mail coming from
Juno.  The headers from a legitimate piece of mail:

From: wendy wong <wendl@juno.com>
To: ac996@yahoo.com,ckw224@yahoo.com,dtu@ams.com,josephtu@nyc.rr.com,
jjlin@everybody.org,laiernie@hotmail.com,lichin@juno.com,
mchoi1@hotmail.com,sanl888@aol.com
Date: Wed, 26 May 2004 10:42:42 -0400
Subject: june and beyond
Message-ID: <20040526.104312.468.3.wendl@juno.com>
Received: from mx12.lax.untd.com (mx12.lax.untd.com [10.130.24.72])
        by maildeliver23.lax.untd.com with SMTP id AABAMKMK3AL6WS3J
        for <lichin@juno.com> (sender <wendl@juno.com>);
        Wed, 26 May 2004 07:44:09 -0700 (PDT)
Received: from m07.lax.untd.com (m07.lax.untd.com [64.136.30.70])
        by mx12.lax.untd.com with SMTP id AABAMKMK3AG5G5U2
        for <lichin@juno.com> (sender <wendl@juno.com>);
        Wed, 26 May 2004 07:44:09 -0700 (PDT)
Received: (from wendl@juno.com)
by m07.lax.untd.com (jqueuemail) id JWKKBAD4; Wed, 26 May 2004 07:43:23 PDT
X-Mailer: Juno 5.0.33
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=--__JNP_000_2e8b.3398.332c
Return-Path: <wendl@juno.com>
X-UNTD-OriginStamp: jrZ+XuBecrUeR4lWV72HFY++1RTlAnvmQQ1IWRVjbAUVVWzwK/6ESg==
Message-ID: <20040526.104312.468.3.wendl@juno.com>

Unfortunately, my understanding of the SpamAssassin code isn't that great, so
I'm not able to see why the check_for_forged_juno_received_headers function is
failing here.
Comment 1 Daniel Quinlan 2004-08-27 16:59:22 UTC 
moving accuracy and some bugs to 3.1.0 milestone
Comment 2 Daniel Quinlan 2004-08-27 17:17:41 UTC 
more accuracy and performance bugs going to 3.1.0 milestone
Comment 3 Daniel Quinlan 2005-01-26 22:32:52 UTC 
I'm unable to reproduce this issue with SVN HEAD or 2.6x.  Closing as
WORKSFORME.