Re: HTML_FONT_SIZE_HUGE firing on html that looks ok

I can reproduce on Ubuntu 26.04 with spamassasin 4.0.2.

On Tue, 12 May 2026, Matija Nalis wrote:

>
> On Mon, May 11, 2026 at 09:54:23PM -0400, Greg Troxel wrote:
>> Matija Nalis <[email protected]> writes:
>>
>>> On Mon, May 11, 2026 at 06:45:03PM -0400, Greg Troxel wrote:
>
>> It's a problem because it's asserting something about the message that
>> is not true and makes no sense.  That's a bug even if the default config
>> only counts it for one millipoint.
>
> I would agree that is a bug; but I can't reproduce your problem in my
> environment.
>
>> Thanks for pushing me to do that.  I went through and trimmed and
>> trimmed, checking each time, and converted identifiers to dummy values.
>> The result is super short and it still fires.
>
>> But the big deal is I'm still getting HTML_FONT_SIZE_HUGE.
>
> That definitely sound wrong; that example of your (while it has HTML)
> has nothing font-related, so i wouldn't expect HTML_FONT_SIZE_HUGE to
> trigger.
>
> The HTML_FONT_SIZE_HUGE is NOT triggering on my SA 3.4.1 with your
> ham.000 (only HTML_MESSAGE and DMARC/etc stuff is).
>
> I know this might sound annoying (that is not my intention!); but are you sure that:
>
> - this is really the exact file you've checking with "spamassassin -D -t" ?
> - that something in your extra rules did not override HTML_FONT_SIZE_HUGE test?
>
>
>>   May 11 21:50:45.236 [29438] dbg: rules: ran eval rule HTML_FONT_SIZE_HUGE ======> got hit (1)
>>
>> SA 4.0.2, perl 5.42.2, NetBSD 10 amd64.  sa-update nightly: rule files
>> have mod time of 0500 EDT today.  This setup otherwise works well.
>
>
> Well, maybe someone with SA 4.0.2 can check how it behaves for them;
> maybe it's a bug there (maybe only on NetBSD?)
>
> If I were you, I'd:
>
> - wait a little if someone can reproduce the issue with SA 4.0.2
>
> - if nobody reproduces the bug, I'd setup a new NetBSD VM with
>  completely bare SA (i.e. no custom rules / extra plugins) and try
>  to reproduce problem there:
>
>  - if you can't reproduce the bug there, there there is something in
>    your custom setup that is broken, and you need to track it down
>    by looking at differences to pristine SA (change by change)
>
>  - however if bug is successfully reproduced in pristine NetBSD
>    Spamassassin 4.0.2, I'd fire up my editor and start adding dbg()
>    statements in that Mail/SpamAssassin/HTML.pm in anything
>    mentioning "size" (i.e. sub text_style() primarily) until I found
>    out what exactly is changing those $self->{max_size} and/or
>    $self->{min_size})
>
>    If you get to this point but don't know what to add, ask and I'll
>    try to help.
>
> -- 
> Opinions above are GNU-copylefted.
>

-- 
Andrew C. Aitchison                      Kendal, UK
                    [email protected]