http://www.hughes-family.org/bugzilla/show_bug.cgi?id=122

           Summary: LINE_OF_YELLING matches line of just periods
           Product: Spamassassin
           Version: 2.11
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Rules
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


I received a mail off of the Linux XFS mailing list which had a long line of just 
periods.  This set off 
the LINE_OF_YELLING rule, which with the other rules that hit this particular message, 
flagged 
it as a false positive.  I haven't had time to think about the appropriate change to 
the regexp yet, 
but LINE_OF_YELLING should require some alpha-numerics in the string.

The message in 
question:

>From [EMAIL PROTECTED]  Sun Mar 24 03:03:31 2002
From: Paul 
Blazejowski <[EMAIL PROTECTED]>
To: Eric Sandeen <[EMAIL PROTECTED]>
Subject: 
Re: XFS latest changes, sb corruption?
Date: Sun, 24 Mar 2002 02:56:36 -0500
Cc: <linux-
[EMAIL PROTECTED]>

SPAM: -------------------- Start SpamAssassin results ----------------------
SPAM: This mail is probably spam.  The 
original message has been altered
SPAM: so you can recognise or block similar unwanted mail in 
future.
SPAM: See http://spamassassin.org/tag/ for more details.
SPAM:
SPAM: Content 
analysis details:   (5.2 hits, 5 required)
SPAM: Hit! (0.0 points)  Subject: ends in a question 
mark
SPAM: Hit! (2.7 points)  BODY: A WHOLE LINE OF YELLING DETECTED
SPAM: Hit! (0.7 points)  
BODY: Contains a line >=199 characters long
SPAM: Hit! (1.8 points)  No MX records for the From: 
domain
SPAM:
SPAM: -------------------- End of SpamAssassin results ---------------------

Hi Eric,

I have a bug i think...i was 
able to reproduce the sb corruption after
compiling new kernel.

Updated my xfs tree with 
todays CVS (no changes) then i generated a diff
against clean 2.4.18 kernel patched with xfs and 
jfs patches,did make dep
then make bzImage followed by make modules...all of these steps went 
fine.
I rerun /sbin/lilo to update the loader and made a quick boot disk using:
dd 
if=/dev/sda2 of=/dev/fd0 ibs=1440 count=1 (sda2 is the partition with xfs).
Again there was 
no crashes or forced shutdowns...rebooted the box and when
new kernel booted it showed these 
errors:

XFS: bad magic number
XFS: SB validate failed
VFS: unable to mount block device 
on (8,2) or something close.

Again this is on Slackware Linux 8.0 with kernel 2.4.18 and gcc 
2.95.3.

This is what xfs_repair shows:

xfs_repair -n /dev/sda2
Phase 1 - find and verify 
superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary 
superblock...
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
.............................!
....................found
candidate 
secondary superblock...
verified secondary superblock...
would write modified primary 
superblock
primary superblock would have been modified.
cannot proceed further in 
no_modify mode.
exiting now.

I did not make any changes to the fs yet...how would i pull the 
first few kb
off of the fs you mentioned earlier? Thanks again for your 
help.

Regards,

Paul



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to