https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6864
--- Comment #3 from Mark Martinec <mark.marti...@ijs.si> --- > Granted it's valid, but it's apparently very common in spam generated by > sloppy tools and not common in mail from well-written MUAs. Could you get > the X-Mailer from the headers so we know what generated that From: line? > That header was not in the sample you attached. The attached header is pretty much complete, I just replaced the username with xxx and yyy, simplified Subject, and dropped local Received entries. Unfortunately there was no X-Mailer or User-Agent header field. > I also note the lack of a space after the To: - whatever mailer your > colleague is using needs some cleanup. :) Indeed there was no (optional) space after the To: . The message is a user registration procedure confirmation, apparently generated by some automation scripting or some HR management software. Body is all in ascii plain text, doesn't reveal much of its creation procedure, just states their Users Office contact address, a password and a few instructions. > Please see if this message (and any other similar FPs) can be added to a > masscheck ham corpus so that the generated scores can better reflect this. Not sure if I can reveal more of the message beyond what was attached. > I will see about tuning the rules; any change I make will probably be rather > focused, either to having an encoded display name with no space, or using > that specific mailer. I'm not complaining about each of these three rules scores individually, but their cumulative action seems excessive for a simple unusual formatting. -- You are receiving this mail because: You are the assignee for the bug.
