<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><pre class="tw-data-text vk_txt tw-ta tw-text-small" data-placeholder="Tradução" id="tw-target-text" data-fulltext="" dir="ltr" style="unicode-bidi: -webkit-isolate; border: none; padding: 0px 0.14em 0px 0px; position: relative; margin-top: 0px; margin-bottom: 0px; resize: none; font-family: inherit; overflow: hidden; width: 237.5px; white-space: pre-wrap; word-wrap: break-word; color: rgb(33, 33, 33); height: 120px; line-height: 24px !important; background-color: rgb(255, 255, 255);">When the user clicks " Not Spam" in thunderbird. -E<span style="font-family: inherit; font-size: 12pt;">-mail goes to your inbox.
</span><span style="font-family: inherit; font-size: 12pt;">These e- mails from the inbox would like to add them to a whitelist .</span></pre><br><div>> Date: Tue, 24 Feb 2015 10:55:21 +0300<br>> From: ta@geuka.net<br>> To: amavis-users@amavis.org<br>> Subject: The nonsense of training spam filters and spam folders [was: training spamsassin]<br>> <br>> <br>> > I would like to spend a script in each user box by adding the sender<br>> > on the whitelist .<br>> <br>> Please try at least to understand how a spamfilter is working. Read the<br>> amavis introduction section in the documentation to understand what<br>> amavis is, does and what is not, does not.<br>> Understand how Bayesian filters are working.<br>> Start with the wikipedia articles<br>> http://en.wikipedia.org/wiki/Naive_Bayes_spam_filtering and<br>> http://en.wikipedia.org/wiki/Bayes%27_theorem<br>> <br>> When you have understood how this filter is working you don't want to<br>> train it any more because the you have understood that you push the<br>> detection in a direction where you usual don't want it.<br>> <br>> The kind of "white" listing you might want is amavis' pen pal feature.<br>> The documentation for amavis is poor: Is known. Read the change logs and<br>> have a look at the source code. This is the real documentation.<br>> For finding out how a feature has to be configured you don't have to be<br>> Perl Guru. Some basic Perl knowledge is usual fine.<br>> <br>> White listing? Why?<br>> If a mail is tagged as spam then in 99.999% of all cases it is spam. And<br>> in 99.999% of all cases of "false" positives the sender has done<br>> something really wrong or his mail client/mail server is fucked up.<br>> Why should I white list them?<br>> If they are not able to send a at least somehow correct mail they don't<br>> want to communicate.<br>> It is like on a road section a few idiots are driving on the wrong side.<br>> Are the other drivers accepting this? Will they also start driving on<br>> the wrong side on this section? Sure not.<br>> And in case there is a serious real reason why I must white list a<br>> sender (at the moment no idea what this should be, never needed it):<br>> Don't mess around with the filter.<br>> Exclude them before the spam filter or write a spamassassin rule and<br>> deduct some points if this rule is matching.<br>> Samples and a how to write rules you find in the online spamassassin<br>> documentation https://wiki.apache.org/spamassassin/WritingRules<br>> <br>> And when you have understood this and you think it all to the end then<br>> you don't want any white list, spam folder or quarantine.<br>> All incoming mail you filter during delivery in real time and reject all<br>> spam hard with 5xx.<br>> All mail from authenticated users you filter (yes we filter all mails.<br>> In and out) post-queue (maybe all spam filters are busy at the moment<br>> and I know no mail client able to handle 4xx errors proper). If the<br>> sender restrictions are correct (sender_mismatch and so on) it is save<br>> to bounce them so your client getting a report why his mail was<br>> rejected. You might have to change the report templates to make them<br>> more client understandable.<br>> My experience is: Time on the sending computer is not set correct<br>> combined with several other mistakes like: This is a important mail, so<br>> I write EVERYTHING IN CAPITAL LETTERS or a home brew software is<br>> creating simply completely broken mails. Assembling a correct formatted<br>> mail is more difficult than it looks like.<br>> <br>> Real time filtering. You don't want to support spammers.<br>> If you first accept with a 250 response code and then filter: 250 means<br>> accepted for delivery. If it ends up in the inbox, quarantine is<br>> discarded: Does not matter it is delivered and the spammers gets paid.<br>> What to do with the accepted spam?<br>> I can not bounce it: Sender usual faked, backscatter and I end up on a RBL.<br>> I can not discard it: I don't know one country where this would be not a<br>> crime.<br>> I have to deliver it.<br>> So I throw it in a quarantine or spam folder where it will be lost.<br>> Which client is checking the spam folder frequently? None.<br>> From time to time (quota warning: Mailbox nearly full) the entire spam<br>> folder is deleted: Mails are lost.<br>> Ever checked on a quarantine system like maya how often users are<br>> checking it? I can tell you: Never.<br>> What is with rarely happening false positives?<br>> Might be a really important mail. Who will pay for the potential damage?<br>> Sender: "I informed you about changes in time. I have a 250 delivered.<br>> You got the mail."<br>> Receiver: "I did not get this mail."<br>> Court: "250 response code means: Delivered to your premises. If you<br>> loose it in house: Your problem."<br>> <br>> If I have to check a quarantine or spam folder frequently for what do I<br>> need it?<br>> I want this all in my inbox. Making it easier.<br>> If I get all this crap in my inbox: For what do I need a spam filter? It<br>> is absolute useless.<br>> And don't tag mails as spam by changing the subject: You break DKIM<br>> signatures.<br>> <br>> If I do pre-queue real time filtering: The rarely bounced false<br>> positives giving the sender within seconds the information: Not<br>> delivered. He can try again, pick the phone or whatever but the<br>> information will not be lost.<br>> <br>> Andreas<br>> <br>> <br>> <br></div> </div></body>
</html>