Sometimes a spam message ends up in the inbox or a legit message ends up in the rejects folder. When this happens, I like to inspect the message source to find out what went wrong with a particular message. Mox does indeed provide some information in the X-Mox-Reason header.
Unfortunately, the strings are not really self explainatory. Something like msgfromfull doesn't really tell you anything unless you have been a developer on the project yourself.
Therefore, I propose to change the strings to be a short and concise description in plain english.
For example, msgfromfull would become something like Sender matches previous spam messages.
Sometimes a spam message ends up in the inbox or a legit message ends up in the rejects folder. When this happens, I like to inspect the message source to find out what went wrong with a particular message. Mox does indeed provide some information in the
X-Mox-Reasonheader.Unfortunately, the strings are not really self explainatory. Something like
msgfromfulldoesn't really tell you anything unless you have been a developer on the project yourself.Therefore, I propose to change the strings to be a short and concise description in plain english.
For example,
msgfromfullwould become something likeSender matches previous spam messages.