Gecko [ 122.154.134.11 ]

Name	Size	Permission
mh-acros.el	12.65 KB	-rw-r--r--
mh-alias.elc	17.61 KB	-rw-r--r--
mh-buffers.elc	2.74 KB	-rw-r--r--
mh-comp.elc	33.6 KB	-rw-r--r--
mh-compat.el	12.07 KB	-rw-r--r--
mh-e.elc	113.81 KB	-rw-r--r--
mh-folder.elc	61.68 KB	-rw-r--r--
mh-funcs.elc	12.23 KB	-rw-r--r--
mh-gnus.el	6.07 KB	-rw-r--r--
mh-identity.elc	7.9 KB	-rw-r--r--
mh-inc.elc	2.11 KB	-rw-r--r--
mh-junk.elc	15.3 KB	-rw-r--r--
mh-letter.elc	27.93 KB	-rw-r--r--
mh-limit.elc	10.43 KB	-rw-r--r--
mh-loaddefs.el	103.32 KB	-rw-r--r--
mh-mime.elc	55.16 KB	-rw-r--r--
mh-print.elc	8.59 KB	-rw-r--r--
mh-scan.elc	16.45 KB	-rw-r--r--
mh-search.elc	59.54 KB	-rw-r--r--
mh-seq.elc	37.48 KB	-rw-r--r--
mh-show.elc	130.77 KB	-rw-r--r--
mh-speed.elc	16.67 KB	-rw-r--r--
mh-thread.elc	43.78 KB	-rw-r--r--
mh-tool-bar.elc	26.7 KB	-rw-r--r--
mh-utils.elc	28.26 KB	-rw-r--r--
mh-xface.elc	14 KB	-rw-r--r--

Code Editor : mh-junk.elc

;ELC���
;;; Compiled by mockbuild@c6b8.bsys.dev.centos.org on Thu Feb 19 13:04:26 2015
;;; from file /builddir/build/BUILD/emacs-23.1/lisp/mh-e/mh-junk.el
;;; in Emacs version 23.1.1
;;; with all optimizations.

;;; This file uses dynamic docstrings, first added in Emacs 19.29.
(if (and (boundp 'emacs-version)
	 (< (aref emacs-version (1- (length emacs-version))) ?A)
	 (or (and (boundp 'epoch::version) epoch::version)
	     (string-lessp emacs-version "19.29")))
    (error "`mh-junk.el' was compiled for Emacs 19.29 or later"))

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

(byte-code "\300\301!\210\300\302!\207" [require mh-e mh-scan] 2)
#@480 Blacklist RANGE as spam.

This command trains the spam program in use (see the option
`mh-junk-program') with the content of RANGE and then handles the
message(s) as specified by the option `mh-junk-disposition'.

Check the documentation of `mh-interactive-range' to see how RANGE is
read in interactive use.

For more information about using your particular spam fighting
program, see:

- `mh-spamassassin-blacklist'
  - `mh-bogofilter-blacklist'
  - `mh-spamprobe-blacklist'
(defalias 'mh-junk-blacklist #[(range) "\306	\"A@\211\204�\307\310!\210\204�\311\202B�\312\232\203!�\313\202B�\314H\315=\203-�\202B�\314H\316=\203?�\f\317\320\311OQ\202B�\313P\"\247\203\215�\321\"\322\211#\203\257\"#\323\324#\"\210\nK#!\210\323\325#\"\210#$>\204w�#$B$
\203\205�\326\311\327
!\"\210\202\211�\330\311!\210)\202\257\":\203�\"@\247\203�\"A\247\203�\212\"@b\210\331 \210`\"AX\203\374�m\204\374�\332%!\203\366�\333\322!#\323\324#\"\210\nK#!\210\323\325#\"\210#$>\204\343�#$B$
\203\361�\326\311\327
!\"\210\202\365�\330\311!\210)\320y\210\202\252�)\202\257\"\203\"9\203\334\"!\202\"\";\203 \335\f\"\"\202\"\"\336 &\211'\311#\211(\203H(@#\337#\322&#\210(A\211(\2042*\212eb\210\331 \210`dX\203\256m\204\256\332%!\203\250\333\322!)\340)&\"\203\247)#\323\324#\"\210\nK#!\210\323\325#\"\210#$>\204\224#$B$
\203\242\326\311\327
!\"\210\202\246\330\311!\210))\320y\210\202P+\341 *\207" [mh-junk-choice mh-junk-function-alist blacklist-func mh-junk-disposition mh-current-folder dest assoc error "Customize `mh-junk-program' appropriately" nil "" "+" 0 43 64 "/" 1 mh-goto-msg t message "Blacklisting message %d..." "Blacklisting message %d...done" mh-refile-a-msg intern mh-delete-a-msg beginning-of-line looking-at mh-get-msg-num mh-seq-to-msgs mh-translate-range make-hash-table puthash gethash mh-next-msg range msg mh-seen-list mh-scan-valid-regexp #1=#:seq-hash-table #2=#:msgs #3=#:--cl-dolist-temp-- v] 6 (#$ . 677) (list (mh-interactive-range "Blacklist"))])
#@297 Whitelist RANGE as ham.

This command reclassifies the RANGE as ham if it were incorrectly
classified as spam (see the option `mh-junk-program'). It then
refiles the message into the "+inbox" folder.

Check the documentation of `mh-interactive-range' to see how
RANGE is read in interactive use.
(defalias 'mh-junk-whitelist #[(range) "\306\307	\"8\211\204�\310\311!\210\247\2038�\312\313\211#\203\314\315\f\"\210\nK\f!\210\314\316\f\"\210\317\320\321
!\"\210)\202:\203\210�@\247\203\210�A\247\203\210�\212@b\210\322 \210`AX\203\204�m\204\204�\323!\203~�\324\313!\314\315\f\"\210\nK\f!\210\314\316\f\"\210\317\320\321
!\"\210)\325y\210\202Q�)\202\203\227�9\203\227�\326!\202\245�;\203\244�\327\"\202\245�\330 \211\320\211 \203\310� @\331\f\313#\210 A\211 \204\264�*\212eb\210\322 \210`dX\203m\204\323!\203\n\324\313!!\332!\"\203	!\314\315\f\"\210\nK\f!\210\314\316\f\"\210\317\320\321
!\"\210))\325y\210\202\320�+\333 )\207" [mh-junk-choice mh-junk-function-alist whitelist-func range msg mh-inbox 2 assoc error "Customize `mh-junk-program' appropriately" mh-goto-msg t message "Whitelisting message %d..." "Whitelisting message %d...done" mh-refile-a-msg nil intern beginning-of-line looking-at mh-get-msg-num 1 mh-seq-to-msgs mh-translate-range make-hash-table puthash gethash mh-next-msg mh-scan-valid-regexp mh-current-folder #1=#:seq-hash-table #2=#:msgs #3=#:--cl-dolist-temp-- v] 6 (#$ . 2725) (list (mh-interactive-range "Whitelist"))])
(byte-code "\301B\302\301!\204�\303\301\304\305!\"\210\306B\302\306!\204\"�\303\306\304\307!\"\210\301\207" [current-load-list mh-spamassassin-executable default-boundp set-default executable-find "spamassassin" mh-sa-learn-executable "sa-learn"] 4)
#@3134 Blacklist MSG with SpamAssassin.

SpamAssassin is one of the more popular spam filtering programs.
Get it from your local distribution or from
http://spamassassin.org/.

To use SpamAssassin, add the following recipes to
".procmailrc":

PATH=$PATH:/usr/bin/mh
    MAILDIR=$HOME/`mhparam Path`

# Fight spam with SpamAssassin.
    :0fw
    | spamc

# Anything with a spam level of 10 or more is junked immediately.
    :0:
    * ^X-Spam-Level: ..........
    /dev/null

:0:
    * ^X-Spam-Status: Yes
    spam/.

If you don't use "spamc", use "spamassassin -P -a".

Note that one of the recipes above throws away messages with a
score greater than or equal to 10. Here's how you can determine a
value that works best for you.

First, run "spamassassin -t" on every mail message in your
archive and use Gnumeric to verify that the average plus the
standard deviation of good mail is under 5, the SpamAssassin
default for "spam".

Using Gnumeric, sort the messages by score and view the messages
with the highest score. Determine the score which encompasses all
of your interesting messages and add a couple of points to be
conservative. Add that many dots to the "X-Spam-Level:" header
field above to send messages with that score down the drain.

In the example above, messages with a score of 5-9 are set aside
in the "+spam" folder for later review. The major weakness of
rules-based filters is a plethora of false positives so it is
worthwhile to check.

If SpamAssassin classifies a message incorrectly, or is unsure,
you can use the MH-E commands \[mh-junk-blacklist] and
\[mh-junk-whitelist].

The command \[mh-junk-blacklist] adds a "blacklist_from" entry
to "~/spamassassin/user_prefs", deletes the message, and sends
the message to the Razor, so that others might not see this spam.
If the "sa-learn" command is available, the message is also
recategorized as spam.

The command \[mh-junk-whitelist] adds a "whitelist_from" rule
to the "~/.spamassassin/user_prefs" file. If the "sa-learn"
command is available, the message is also recategorized as ham.

Over time, you'll observe that the same host or domain occurs
repeatedly in the "blacklist_from" entries, so you might think
that you could avoid future spam by blacklisting all mail from a
particular domain. The utility function
`mh-spamassassin-identify-spammers' helps you do precisely that.
This function displays a frequency count of the hosts and domains
in the "blacklist_from" entries from the last blank line in
"~/.spamassassin/user_prefs" to the end of the file. This
information can be used so that you can replace multiple
"blacklist_from" entries with a single wildcard entry such as:

blacklist_from *@*amazingoffersdirect2u.com

In versions of SpamAssassin (2.50 and on) that support a Bayesian
classifier, \[mh-junk-blacklist] uses the program "sa-learn"
to recategorize the message as spam. Neither MH-E, nor
SpamAssassin, rebuilds the database after adding words, so you
will need to run "sa-learn --rebuild" periodically. This can be
done by adding the following to your crontab:

0 * * * *   sa-learn --rebuild > /dev/null 2>&1
(defalias 'mh-spamassassin-blacklist #[(msg) "\204�\306\307!\210	\310\n	\"\311\312\313\n\"\210\314 \210r&q\210\315\f'\311\316\317&\210(\203D�\312\320\n\"\210\314 \210\315(\f'\311\321\322\323\324&\210)\312\325\n\"\210r\326)!q\210\327 \210\315\330*+\"\311\331\311\332\333\n\"
\334\335&\210eb\210\336\337\311\331#\203\203�\340\341!\342\343\"\210\312\344\n\"\202\207�\312\345\n\",\207" [mh-spamassassin-executable mh-current-folder msg sender msg-file current-folder error "Unable to find the spamassassin executable" mh-msg-filename nil message "Reporting message %d..." mh-truncate-log-buffer call-process "-r" "-R" "Recategorizing message %d as spam..." "--single" "--spam" "--local" "--no-rebuild" "Blacklisting sender of message %d..." get-buffer-create erase-buffer expand-file-name t format "%d" "-format" "%<(mymbox{from})%|%(addr{from})%>" search-forward-regexp "^\$.+\$$" match-string 0 mh-spamassassin-add-rule "blacklist_from" "Blacklisting sender of message %d...done" "Blacklisting sender of message %d...not done (from my address)" mh-log-buffer mh-junk-background mh-sa-learn-executable mh-temp-buffer mh-scan-prog mh-progs] 9 (#$ . 4488)])
#@276 Whitelist MSG with SpamAssassin.

The \[mh-junk-whitelist] command adds a "whitelist_from" rule to
the "~/.spamassassin/user_prefs" file. If the "sa-learn" command
is available, the message is also recategorized as ham.

See `mh-spamassassin-blacklist' for more information.
(defalias 'mh-spamassassin-whitelist #[(msg) "\204�\306\307!\210\310	\n\"\311!\312r\313 !q\210\314 \210\315\316	\"\210\317\320\312\321%\210
\2034�\322
!\210\323!\210!\203[�\315\324	\"\210\325 \210r\"q\210\317!#\312\326\327\330\331&\210)\315\332	\"\210\312\322\312!\210\f\203u�\f\333\232\204u�\334\335\f\"\210\315\336	\",\207" [mh-spamassassin-executable msg mh-current-folder mh-show-buffer from show-buffer error "Unable to find the spamassassin executable" mh-msg-filename get-buffer nil get-buffer-create erase-buffer message "Removing spamassassin markup from message %d..." call-process t "-d" kill-buffer write-file "Recategorizing message %d as ham..." mh-truncate-log-buffer "--single" "--ham" "--local" "--no-rebuild" "Whitelisting sender of message %d..." "" mh-spamassassin-add-rule "whitelist_from" "Whitelisting sender of message %d...done" msg-file mh-temp-buffer mh-sa-learn-executable mh-log-buffer mh-junk-background] 9 (#$ . 8802)])
#@100 Add a new rule to "~/.spamassassin/user_prefs".
The name of the rule is RULE and its body is BODY.
(defalias 'mh-spamassassin-add-rule #[(rule body) "\300\213\207" [((byte-code "\306\307	#\310\311\312!\313\f!\314\f!\210\315\306\316\n\"\317\310#\2042�db\210n\203*�\320\202+�\321\n\261\210\322 \210
?\205:�\323\317!,\207" [rule body line case-fold-search file buffer-exists format "%s	%s\n" t expand-file-name "~/.spamassassin/user_prefs" find-buffer-visiting find-file search-forward "\n%s" nil "" "\n" save-buffer kill-buffer] 4))] 1 (#$ . 10056)])
#@399 Identify spammers who are repeat offenders.

This function displays a frequency count of the hosts and domains
in the "blacklist_from" entries from the last blank line in
"~/.spamassassin/user_prefs" to the end of the file. This
information can be used so that you can replace multiple
"blacklist_from" entries with a single wildcard entry such as:

blacklist_from *@*amazingoffersdirect2u.com
(defalias 'mh-spamassassin-identify-spammers #[nil "\304\305!\306\307\310\"\311!\210dSb\210\312\313!\210\212\314\315\316\317#\203Q�\320\321!\316\322\323\324\"!A\211\203M�\325@	\"\326@\n\204A�\327\202B�\nT	#\210A\211\2040�*\202�)\330 \210\331\332\333!!\210\334 \210\335\336	\"\210\337\321ed#\210\340ed\"\210eb*\207" [file domains value host expand-file-name "~/.spamassassin/user_prefs" make-hash-table :test equal find-file search-backward-regexp "^$" search-forward-regexp "^blacklist_from\\s-*\$.*\$@\$.*\$$" nil t match-string 2 reverse split-string "\\." gethash puthash 0 delete-other-windows pop-to-buffer get-buffer-create "*MH-E Spammer Frequencies*" erase-buffer maphash #[(key value) "\302V\205\f�\303\304	#c\207" [value key 2 format "%s %s\n"] 4 ""] sort-numeric-fields reverse-region] 5 (#$ . 10618) nil])
(byte-code "\301B\302\301!\204�\303\301\304\305!\"\210\301\207" [current-load-list mh-bogofilter-executable default-boundp set-default executable-find "bogofilter"] 4)
#@1338 Blacklist MSG with bogofilter.

Bogofilter is a Bayesian spam filtering program. Get it from your
local distribution or from http://bogofilter.sourceforge.net/.

Bogofilter is taught by running:

bogofilter -n < good-message

on every good message, and

bogofilter -s < spam-message

on every spam message. This is called a full training; three other
training methods are described in the FAQ that is distributed with
bogofilter. Note that most Bayesian filters need 1000 to 5000 of each
type of message to start doing a good job.

To use bogofilter, add the following recipes to ".procmailrc":

PATH=$PATH:/usr/bin/mh
    MAILDIR=$HOME/`mhparam Path`

# Fight spam with bogofilter.
    :0fw
    | bogofilter -3 -e -p

:0:
    * ^X-Bogosity: Yes, tests=bogofilter
    spam/.

:0:
    * ^X-Bogosity: Unsure, tests=bogofilter
    spam/unsure/.

If bogofilter classifies a message incorrectly, or is unsure, you can
use the MH-E commands \[mh-junk-blacklist] and \[mh-junk-whitelist]
to update bogofilter's training.

The "Bogofilter FAQ" suggests that you run the following
occasionally to shrink the database:

bogoutil -d wordlist.db | bogoutil -l wordlist.db.new
    mv wordlist.db wordlist.db.prv
    mv wordlist.db.new wordlist.db

The "Bogofilter tuning HOWTO" describes how you can fine-tune Bogofilter.
(defalias 'mh-bogofilter-blacklist #[(msg) "\204�\306\307!\210\310	\n\"\311 \210r\fq\210\312
\313\314%*\207" [mh-bogofilter-executable msg mh-current-folder msg-file mh-log-buffer mh-junk-background error "Unable to find the bogofilter executable" mh-msg-filename mh-truncate-log-buffer call-process nil "-s"] 6 (#$ . 12032)])
#@85 Whitelist MSG with bogofilter.

See `mh-bogofilter-blacklist' for more information.
(defalias 'mh-bogofilter-whitelist #[(msg) "\204�\306\307!\210\310	\n\"\311 \210r\fq\210\312
\313\314%*\207" [mh-bogofilter-executable msg mh-current-folder msg-file mh-log-buffer mh-junk-background error "Unable to find the bogofilter executable" mh-msg-filename mh-truncate-log-buffer call-process nil "-n"] 6 (#$ . 13707)])
(byte-code "\301B\302\301!\204�\303\301\304\305!\"\210\301\207" [current-load-list mh-spamprobe-executable default-boundp set-default executable-find "spamprobe"] 4)
#@603 Blacklist MSG with SpamProbe.

SpamProbe is a Bayesian spam filtering program. Get it from your local
distribution or from http://spamprobe.sourceforge.net.

To use SpamProbe, add the following recipes to ".procmailrc":

PATH=$PATH:/usr/bin/mh
    MAILDIR=$HOME/`mhparam Path`

# Fight spam with SpamProbe.
    :0
    SCORE=| spamprobe receive

:0 wf
    | formail -I "X-SpamProbe: $SCORE"

:0:
    *^X-SpamProbe: SPAM
    spam/.

If SpamProbe classifies a message incorrectly, you can use the
MH-E commands \[mh-junk-blacklist] and \[mh-junk-whitelist] to
update SpamProbe's training.
(defalias 'mh-spamprobe-blacklist #[(msg) "\204�\306\307!\210\310	\n\"\311 \210r\fq\210\312
\313\314%*\207" [mh-spamprobe-executable msg mh-current-folder msg-file mh-log-buffer mh-junk-background error "Unable to find the spamprobe executable" mh-msg-filename mh-truncate-log-buffer call-process nil "spam"] 6 (#$ . 14299)])
#@83 Whitelist MSG with SpamProbe.

See `mh-spamprobe-blacklist' for more information.
(defalias 'mh-spamprobe-whitelist #[(msg) "\204�\306\307!\210\310	\n\"\311 \210r\fq\210\312
\313\314%*\207" [mh-spamprobe-executable msg mh-current-folder msg-file mh-log-buffer mh-junk-background error "Unable to find the spamprobe executable" mh-msg-filename mh-truncate-log-buffer call-process nil "good"] 6 (#$ . 15238)])
(provide 'mh-junk)

${this.title}

Code Editor : mh-junk.elc