Frank Heydlauf-2 wrote: > > Would this really help? > Could you tell us a bit more about your problem itself? > > The reason I ask is: the mailbody is a very small part of what is > commonly used for antispam measures. Header is added afterwards, > IP is not yet known, HELO is not known, no reputation, no RBLs, no > phyzor/razor/... > It's not easy to get a SA score >5 if anything else is OK (IP > reputation/RBLs, DNS, Header, HELO, ...) - just try yourself > (spamassassin -t testmail). > So - in my eyes - body-testing will give you little benefit - at > least as long you are not developing a spam toolkit. >
More about my problem: Recently our application Users have started complaining that mails sent from our application are reaching recipient's Junk E-mail folder instead of Inbox. That is rate of "false positives" is high. We've also verified other anti-spam measures from our side like whether our server IP address is blacklisted with any anti-spam websites (Spamhaus, SORBS, etc.) but it was not the case. Then we found that least we can do from application context is by allowing Users to test spam score of their "email content" before they actuall send emails. I agree with you that mailbody is one of the part of what is commonly used for antispam measures but still we want to advise/allow our application Users to test spam score of their "email body/content". Reason I'm saying this is that since the entire email body/content is composed by Users, atleast by running spam score test, spam triggering properties within email content can be avoided. Hope this clarifies the situation. Can SpamAssassin be used to test spam score of .html, .txt file extension types, that is "email body/content" part of the email message? -- View this message in context: http://old.nabble.com/SpamAssassin-Integration-tp28903365p28911147.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
