Created attachment 3546 [details]
Sample message triggering EMPTY_MESSAGE

What's happening is that since there are no text/* or message/* parts in the message, SA considers 
there to be no body content (the Subject is prepended to the body, but is not considered the body in 
and of itself).

EMPTY_MESSAGE looks for a single non-whitespace char in the body, which doesn't exist here, so the 
rule triggers.

So the question is: should EMPTY_MESSAGE pay attention to non-textual MIME parts?  If yes, the rule 
will have to change from body/meta to an evaltest so it can appropriately filter through parts, etc.

I'd be happy enough to change the rule description such that it specifies that there are no textual parts 
in the message as opposed to being a generic "Message appears to be empty with no Subject: text".

Ok, I changed the rule description in 3.2, 3.1.5, and the 3.1 updates.

The test attachment #1 [details] still results in the EMPTY_MESSAGE test returning
"positive" with spamassassin 3.1.7 As this test would at worse add another 2.308
points to the spam score I cannot consider this bug as resolved + fixed.

Not the description but the wrong consideration of PGP/GPG encrypted messages
being empty and adding anoter 2.308 points to the spam score makes this still a
bug from my point of view.