http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5508
------- Additional Comments From [EMAIL PROTECTED] 2007-08-07 09:04 -------
> ok, sounds like we have a problem then!(In reply to comment #7)
> ok, that's a problem then! I can't repro the bug with 0.13.0 and SA 3.2.2 on
> Linux/x86, so it may be a platform-specific
here,
osx 10.4.10
perl 588
re2c 0.13.0
sa-compile --version
SpamAssassin version 3.2.3-r559432
fwiw, this is 100% reproducible on 6 similar boxes. so, at least it's not
single-box-weirdness.
also, fyi, new release version, re2c 0.12.2 "works" fine ...
>, or ruleset-specific problem.
>
> What rulesets do you have installed? just the SA default,
of COURSE not.
that would be too easy ;-)
> or additional SARE ones?
atm,
SA-distro rules
+ SARE-rules
{
70_sare_obfu.cf.sare.sa-update.dostech.net
72_sare_redirect_post3.0.0.cf.sare.sa-update.dostech.net
70_sare_evilnum0.cf.sare.sa-update.dostech.net
70_sare_evilnum1.cf.sare.sa-update.dostech.net
70_sare_bayes_poison_nxm.cf.sare.sa-update.dostech.net
70_sare_header.cf.sare.sa-update.dostech.net
70_sare_header_eng.cf.sare.sa-update.dostech.net
99_sare_fraud_post25x.cf.sare.sa-update.dostech.net
70_sare_spoof.cf.sare.sa-update.dostech.net
70_sare_random.cf.sare.sa-update.dostech.net
70_sc_top200.cf.sare.sa-update.dostech.net
70_sare_oem.cf.sare.sa-update.dostech.net
70_sare_unsub.cf.sare.sa-update.dostech.net
70_sare_uri.cf.sare.sa-update.dostech.net
70_sare_specific.cf.sare.sa-update.dostech.net
70_sare_oem.cf.sare.sa-update.dostech.net
70_sare_html.cf.sare.sa-update.dostech.net
70_sare_genlsubj.cf.sare.sa-update.dostech.net
72_sare_bml_post25x.cf.sare.sa-update.dostech.net
70_sare_stocks.cf.sare.sa-update.dostech.net
99_FVGT_Tripwire.cf.sare.sa-update.dostech.net
bogus-virus-warnings.cf.sare.sa-update.dostech.net
}
+ fuzzy-ocr
+ botnet
+ freemail
+ kam
> I would recommend running "sa-compile --sudo --keep-tmps" and once it fails,
> tar
> up the temporary dir mentioned in the last line of the output, e.g.:
>
> temporary dir left due to --keep-tmps: /tmp/.spamassassin3353b3oFKDtmp
>
> also, take a copy of the output on stdout from sa-compile. Attach both here,
> and possibly as a new bug report at re2c.org (although it may be best to check
> it out here first).
>
> It would be really helpful if you could cp /usr/share/spamassassin ~/tstrules,
> then gradually rm rule files in ~/tstrules, running "sa-compile --sudo -C
> ~/tstrules" after each one, until you have a minimal ruleset that still
> exhibits
> the bug.
well, snort!
i'll start the process in-between meetings ... will post when done.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
