{"id":179,"date":"2009-10-27T13:58:19","date_gmt":"2009-10-27T05:58:19","guid":{"rendered":"http:\/\/umarzuki.org\/?p=179"},"modified":"2009-10-27T13:58:19","modified_gmt":"2009-10-27T05:58:19","slug":"pasang-spamassassin-pada-debian-5","status":"publish","type":"post","link":"https:\/\/umarzuki.org\/blog\/2009\/10\/27\/pasang-spamassassin-pada-debian-5\/","title":{"rendered":"Pasang Spamassassin pada Debian 5"},"content":{"rendered":"

Sangat mudah, cuma 2 pakej diperlukan; spamassassin dam spamc
\nSebagai root:
\naptitude install spamassassin spamc<\/code>
\n
\nPada pengguna\/akaun e-mel yang ingin dilindungi, buat satu fail .procmailrc pada direktori utama pengguna tersebut dengan kandungan seperti berikut:<\/p>\n

#########################################################################
\n# procmail.sample2
\n#########################################################################<\/p>\n

# sample procmail file for spam filtering (enhanced version)
\n#
\n# Last modified: Thu 08 Jan 2004 01:42:11 PM CST
\n#
\n# CHANGES:
\n#
\n# 1\/8\/04: Added recipe to save “near misses” to a “probablespam”
\n# folder. Added lock file “spamassassin.lock” to recipe, as recommended
\n# in the spamassassin documentation.
\n#
\n# 1\/7\/04: Replaced the standalone version of spamassassin by the client
\n# version, spamc, to reduce the impact on system resources.
\n# Deleted the recipe for filtering the klez virus, as the virus seems
\n# to have runs its course and is no longer a problem.
\n#
\n#
\n# INSTRUCTIONS: Copy this file to .procmailrc in your home directory.
\n# See www.math.uiuc.edu\/~hildebr\/spamfiltering.html for more information.
\n#
\n# NOTE: This file is intended for users of the UIUC Mathematics
\n# Department’s Unix Network and has only been tested on that system.
\n# It will probably work with little or no modification on most standard
\n# Unix installations with SpamAssassin installed and running spamd,
\n# the daemonized version of spamassassin. Feel free to use or adapt
\n# it, but absolutely no warranties.
\n#
\n#
\n# ABOUT SPAMASSASSIN: Information about the SpamAssassin program
\n# that does the spam filtering can be found at www.spamassassin.org.<\/p>\n

#########################################################################
\n# set mail directory
\n#########################################################################<\/p>\n

MAILDIR = $HOME\/mail<\/p>\n

# This sets the directory in which the spam folder gets placed.
\n# The above setting is the one used by the pine mail reader for its
\n# folders. If you use pine, there is no need to change this setting.
\n#
\n# If you use a different mail reader (e.g., elm, mutt, netscape, dtmail,
\n# mail\/mailx), you may want to replace this directory by the one where
\n# your mail reader normally puts its folders. (For example, netscape
\n# mail uses the directory “nsmail” (underneath $HOME), mutt uses
\n# “Mail”; for mail\/mailx\/dtmail check the “folder” setting in the
\n# .mailrc file.)
\n#
\n# [This is merely a matter of convenience to facilitate locating the
\n# spam folder. You can certainly leave the setting as above, or
\n# replace it by any directory of your choice. With most mail readers, you
\n# can access the spam folder directly using the “-f” option with
\n# the full path to the spam folder, e.g., “mail -f $HOME\/mail\/spam”
\n# or “pine -f $HOME\/mail\/spam”]
\n#<\/p>\n

#########################################################################
\n# spam filter
\n#########################################################################<\/p>\n

#########################################################################
\n# First pipe email through spamc (the “client version” of spamassassin)
\n# for markup
\n#########################################################################<\/p>\n

# The condition ” < 256000\" limits spam filtering to messages that\n# are < 250k in size, as recommended in the spamassassin docs (for\n# performance reasons). Virtually all spam is well below that limit,\n# so having this condition there does not make a difference, as far\n# as spam filtering is concerned.\n\n\n:0fw: spamassassin.lock\n* < 256000\n| \/usr\/bin\/spamc\n\n\n#########################################################################\n# Then route all email tagged as spam to a spam folder inside the\n# mail directory defined above\n#########################################################################\n\n:0:\n* ^X-Spam-Status: Yes\n$MAILDIR\/Spam\n\n\n#########################################################################\n# Next, save \"near misses\" to a special folder \"probablespam\".\n#########################################################################\n\n# Having a sufficiently large supply of such misses is useful for later\n# analysis and for training of SpamAssassin using the sa-learn program.\n#\n# The \"c\" flag in the first line of the recipe ensures that only copies\n# of the messages get rerouted in this way; the messages themselves\n# will pass through and show up in the message index of your mail\n# reader just like any other messages not flagged as spam. For that\n# reason there is no need to check the \"probablespam\" folder for false\n# positives. One can simply leave it alone and forget about it until\n# sufficiently many (say, a few hundred) messages have accumulated\n# there to be useful for the training of SpamAssassin with sa-learn.\n#\n# This recipe is optional. There is no harm in leaving it in and, as\n# mentioned, it may help improving the accuracy of SpamAssassin down\n# the road, but if you don't want it, simply delete it or comment it\n# out by putting a hash mark at the beginning of each line.\n\n\n:0c:\n* ^X-Spam-Level: \\*\\*\\*\n$MAILDIR\/probablespam\n\n#########################################################################\n# Finally, remove header inserted by spamassassin\n#########################################################################\n\n# This step is purely cosmetic. It removes the extra headers inserted\n# by spamassassin listing the \"spam score\" of the message and the\n# tests that the message passed or failed. Many legitimate messages\n# fail some of the tests that spamassassin performs, but the resulting\n# scores are usually well below the spam threshold, so the messages\n# will not be identified as spam. With most mail readers, those headers\n# won't be displayed anyway unless you specifically ask the mail\n# reader to display the full headers. However, if you save a message\n# and then print it out, the headers, including those inserted by spam\n# assassin, will get printed.\n#\n#\n:0fhw\n| formail -I \"X-Spam-\"\n#\n\n#########################################################################\n# end of spam filter\n#########################################################################<\/p><\/blockquote>\n

Sekarang cuba hantar mel spam ke pengguna berkenaan. E-mel tersebut akan terus dimasukkan ke dalam folder ~\/Spam<\/p>\n

Sumber rujukan:<\/p>\n

Installing spamassassin in webmin<\/a><\/p><\/blockquote>\n