1st, I'm trying to search image alt tags for a rule because I'm seeing Spammers using Alt tags for when their images are blocked. So I want to confirm that rawbody is the correct rule type to search for this type of html tag. My real concern is that will this search through things like MIME File Attachments, etc?
2nd, I'm looking at these 'errors' from the 3.2.0rc2. I think this means some of the rules are the same as existing rules in my config dirs so it notifies me that it is "merging dupes". Neat feature! [13247] dbg: rules: KAM_STOCKTIP4 merged duplicates: __KAM_STOCKTIP4 [13247] dbg: rules: FS_SILDENAFIL merged duplicates: KAM_SILD [13247] dbg: rules: KAM_STOCKTIP2 merged duplicates: __KAM_STOCKTIP2 [13247] dbg: rules: KAM_STOCKTIP6 merged duplicates: __KAM_STOCKTIP6 [13247] dbg: rules: KAM_STOCKTIP15 merged duplicates: __KAM_STOCKTIP15 [13247] dbg: rules: KAM_STOCKTIP21 merged duplicates: __KAM_STOCKTIP21 However, in find_dup_rules in Conf/Parser.pm, I'm thinking it would be a good idea to add the path & config file name where the dupes were found. Anyone give me a pointer towards where that info might be available and I'll work on a patch? 3rd, are rules like KAM_STOCKTIP2 this just a reflection of the RC status of the tarball or did a few of the sub rules from my stock rule get auto-promoted? I ask because these rules in and of themselves are a little pointless. 4th, Since I run spamassassin -D -t <file> 2>&1 about 400 times a day, I was thinking it would be a good idea to have Logger/Stderr.pm actually have an option to define the STDERR stream = to STDOUT. It seems silly to do it maybe but it would be nice to add something like --DS to change Stderr.pm to do a print to STDOUT instead. Thoughts? Regards, KAM
