403Webshell
Server IP : 217.160.0.212  /  Your IP : 216.73.216.141
Web Server : Apache
System : Linux www 6.18.51-i1-ampere #1196 SMP Fri Sep 11 20:43:55 CEST 2026 aarch64
User : sws1073854427 ( 1073854427)
PHP Version : 8.4.23
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : OFF  |  Pkexec : OFF
Directory :  /usr/share/emacs/28.2/lisp/mh-e/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /usr/share/emacs/28.2/lisp/mh-e/mh-junk.elc
;ELC
;;; Compiled
;;; in Emacs version 28.2
;;; with all optimizations.



(byte-code "\300\301!\210\300\302!\210\303\304\305\"\207" [require mh-e mh-scan autoload mail-header-parse-address "mail-parse"] 3)
#@492 Blocklist 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-blocklist'
  - `mh-bogofilter-blocklist'
  - `mh-spamprobe-blocklist'

(fn RANGE)
(defalias 'mh-junk-blocklist #[257 "\211\247\203\303\304\211#\203\256\305\306!\210\202\256\211:\203L\211@\247\203L\211A\247\203L\212\211@b\210\307 \210`AX\203Hm\204H\310!\203B\305\306!\210\311y\210\202-)\202\256\211\203[\2119\203[\312!\202h\211;\203g\313	\"\202h\211\314 \211\203~\211@\315\304#\210A\266\202\202k\210\212eb\210\307 \210`dX\203\253m\204\253\310!\203\245\316\304!\317\"\203\244\305\306!\210\210\311y\210\202\206)\266\310\n!\205\266\320 \207" [mh-scan-valid-regexp mh-current-folder mh-scan-blocklisted-msg-regexp mh-goto-msg t mh-junk-blocklist-a-msg nil beginning-of-line looking-at 1 mh-seq-to-msgs mh-translate-range make-hash-table puthash mh-get-msg-num gethash mh-next-msg] 9 (#$ . 217) (byte-code "\300\301!C\207" [mh-interactive-range "Blocklist"] 2)])
#@180 Blocklist MESSAGE.
If MESSAGE is nil then the message at point is blocklisted.
The hook `mh-blocklist-msg-hook' is called after you mark a message
for blocklisting.

(fn MESSAGE)
(defalias 'mh-junk-blocklist-a-msg #[257 "\212\211\247\203\306\307\310#\210\202\311 \210\312\310!\262\313!\203$\314\315\"\202e\313	!\2031\314\316\"\202e\313\n!\203>\314\317\"\202e\313!\203H\307\202e\320\310!\210\211\fB\211
>\204Z\211
B\321\307#\210\322\323!)\207" [mh-scan-refiled-msg-regexp mh-scan-deleted-msg-regexp mh-scan-allowlisted-msg-regexp mh-scan-blocklisted-msg-regexp mh-blocklist mh-seen-list mh-goto-msg nil t beginning-of-line mh-get-msg-num looking-at error "Message %d is refiled; undo refile before blocklisting" "Message %d is deleted; undo delete before blocklisting" "Message %d is allowlisted; undo before blocklisting" mh-set-folder-modified-p mh-notate run-hooks mh-blocklist-msg-hook mh-note-blocklisted mh-cmd-note] 5 (#$ . 1528)])
#@43 Determines the fate of the selected spam.
(defalias 'mh-junk-blocklist-disposition #[0 "\302\267\202\n\303\207\304\207\305H\306=\203\207\305H\307=\203$	\310\311\303OQ\207\304P\207" [mh-junk-disposition mh-current-folder #s(hash-table size 2 test equal rehash-size 1.5 rehash-threshold 0.8125 purecopy t data (nil 6 "" 8)) nil "+" 0 43 64 "/" 1] 5 (#$ . 2498)])
#@225 Blocklist 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'.

(fn RANGE)
(defalias 'mh-junk-process-blocklist #[257 "\304	\"A@\211\204\305\306!\210\247\203 \307\310\211#\205\300\211K!\207:\203\\@\247\203\\A\247\203\\\212@b\210\311 \210`AX\205Zm?\205Z\312\n!\203T\313\310!K!\266\314y\210\2029)\207\203k9\203k\315!\202x;\203w\316\"\202x\317 \211\203\216\211@\320\310#\210A\266\202\202{\210\212eb\210\311 \210`dX\205\275m?\205\275\312\n!\203\267\313\310!\321\"\203\266K!\210\210\314y\210\202\226)\266\202\207" [mh-junk-choice mh-junk-function-alist mh-scan-valid-regexp mh-current-folder assoc error "Customize `mh-junk-program' appropriately" mh-goto-msg t beginning-of-line looking-at mh-get-msg-num 1 mh-seq-to-msgs mh-translate-range make-hash-table puthash gethash] 10 (#$ . 2876)])
#@81 Old name for `mh-junk-allowlist'; use \[mh-junk-allowlist] instead.

(fn RANGE)
(defalias 'mh-junk-whitelist #[257 "\300\301N\204\302\303\304\305!\304\306!#\210\307\300\301\310#\210\311!\207" [mh-junk-whitelist command-execute-obsolete-warned message "%s is an obsolete key (as of 28.1); use %s instead" substitute-command-keys "\\[mh-junk-whitelist]" "\\[mh-junk-allowlist]" put t mh-junk-allowlist] 6 (#$ . 3868) (byte-code "\300\301!C\207" [mh-interactive-range "Allowlist"] 2)])
#@313 Allowlist RANGE as ham.

This command reclassifies the RANGE as ham if it has been 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.

(fn RANGE)
(defalias 'mh-junk-allowlist #[257 "\211\247\203\303\304\211#\203\256\305\306!\210\202\256\211:\203L\211@\247\203L\211A\247\203L\212\211@b\210\307 \210`AX\203Hm\204H\310!\203B\305\306!\210\311y\210\202-)\202\256\211\203[\2119\203[\312!\202h\211;\203g\313	\"\202h\211\314 \211\203~\211@\315\304#\210A\266\202\202k\210\212eb\210\307 \210`dX\203\253m\204\253\310!\203\245\316\304!\317\"\203\244\305\306!\210\210\311y\210\202\206)\266\310\n!\205\266\320 \207" [mh-scan-valid-regexp mh-current-folder mh-scan-allowlisted-msg-regexp mh-goto-msg t mh-junk-allowlist-a-msg nil beginning-of-line looking-at 1 mh-seq-to-msgs mh-translate-range make-hash-table puthash mh-get-msg-num gethash mh-next-msg] 9 (#$ . 4361) (byte-code "\300\301!C\207" [mh-interactive-range "Allowlist"] 2)])
#@180 Allowlist MESSAGE.
If MESSAGE is nil then the message at point is allowlisted. The
hook `mh-allowlist-msg-hook' is called after you mark a message
for allowlisting.

(fn MESSAGE)
(defalias 'mh-junk-allowlist-a-msg #[257 "\212\211\247\203\306\307\310#\210\202\311 \210\312\310!\262\313!\203$\314\315\"\202Z\313	!\2031\314\316\"\202Z\313\n!\203>\314\317\"\202Z\313!\203H\307\202Z\320\310!\210\211\fB\321\307
#\210\322\323!)\207" [mh-scan-refiled-msg-regexp mh-scan-deleted-msg-regexp mh-scan-blocklisted-msg-regexp mh-scan-allowlisted-msg-regexp mh-allowlist mh-note-allowlisted mh-goto-msg nil t beginning-of-line mh-get-msg-num looking-at error "Message %d is refiled; undo refile before allowlisting" "Message %d is deleted; undo delete before allowlisting" "Message %d is blocklisted; undo before allowlisting" mh-set-folder-modified-p mh-notate run-hooks mh-allowlist-msg-hook mh-cmd-note] 5 (#$ . 5494)])
#@159 Allowlist RANGE as ham.

This command reclassifies the RANGE as ham if it were incorrectly
classified as spam (see the option `mh-junk-program').

(fn RANGE)
(defalias 'mh-junk-process-allowlist #[257 "\304\305	\"8\211\204\306\307!\210\247\203 \310\311\211#\205\300\211K!\207:\203\\@\247\203\\A\247\203\\\212@b\210\312 \210`AX\205Zm?\205Z\313\n!\203T\314\311!K!\266\315y\210\2029)\207\203k9\203k\316!\202x;\203w\317\"\202x\320 \211\203\216\211@\321\311#\210A\266\202\202{\210\212eb\210\312 \210`dX\205\275m?\205\275\313\n!\203\267\314\311!\322\"\203\266K!\210\210\315y\210\202\226)\266\202\207" [mh-junk-choice mh-junk-function-alist mh-scan-valid-regexp mh-current-folder 2 assoc error "Customize `mh-junk-program' appropriately" mh-goto-msg t beginning-of-line looking-at mh-get-msg-num 1 mh-seq-to-msgs mh-translate-range make-hash-table puthash gethash] 10 (#$ . 6432)])
(defvar mh-spamassassin-executable (executable-find "spamassassin"))
(defvar mh-sa-learn-executable (executable-find "sa-learn"))
#@2772 Blocklist MSG with SpamAssassin.

SpamAssassin is one of the more popular spam filtering programs.
Get it from your local distribution or from the SpamAssassin web
site at URL `https://spamassassin.apache.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".

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-blocklist] and
\[mh-junk-allowlist].

The command \[mh-junk-blocklist] 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-allowlist] 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 blocklisting 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

(fn MSG)
(defalias 'mh-spamassassin-blocklist #[257 "\204\306\307!\210	\310	\"\311\312\313\"\210\314 \210r\nq\210\315\311\316\317&\210\f\203;\312\320\"\210\314 \210\315\f\311\321\322\323&\210)\312\324\"\210r\325
!q\210\326 \210\315\327%&\"\311\330\311\331\332\n\"\333\334&\210eb\210\335\336\311\330#\203|\337\340!\262\341\342\"\210\312\343\"\202\200\312\344\")\207" [mh-spamassassin-executable mh-current-folder mh-log-buffer mh-junk-background mh-sa-learn-executable mh-temp-buffer error "Unable to find the spamassassin executable" mh-msg-filename nil message "Reporting message %d as spam with spamassassin..." mh-truncate-log-buffer call-process "--report" "-R" "Recategorizing message %d as spam with sa-learn..." "--spam" "--local" "--no-sync" "Blocklisting 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" "Blocklisting sender of message %d...done" "Blocklisting sender of message %d...not done (from my address)" mh-scan-prog mh-progs] 13 (#$ . 7495)])
#@286 Allowlist MSG with SpamAssassin.

The \[mh-junk-allowlist] 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-blocklist' for more information.

(fn MSG)
(defalias 'mh-spamassassin-allowlist #[257 "\204\306\307!\210\310	\"\311\n!\312r\313!q\210\314 \210\315\316\"\210\317\320\312\321%\210\203.\322!\210\323!\210\f\203O\315\324\"\210\325 \210r
q\210\317\f#\312\326\327\330&\210)\315\331\"\210\332\333\334!!@\262\322\312!\210\211\203j\211\335\232\203r\315\336\337#\202{\340\341\"\210\315\342\")\207" [mh-spamassassin-executable mh-current-folder mh-show-buffer mh-temp-buffer mh-sa-learn-executable mh-log-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 "--remove-markup" kill-buffer write-file "Recategorizing message %d as ham with sa-learn..." mh-truncate-log-buffer "--ham" "--local" "--no-sync" "Allowlisting sender of message %d..." mail-header-parse-address mh-get-header-field "From:" "" "Allowlisting sender of message %d...%s" "not done (cannot identify sender)" mh-spamassassin-add-rule "whitelist_from" "Allowlisting sender of message %d...done" mh-junk-background] 12 (#$ . 11428)])
#@116 Add a new rule to "~/.spamassassin/user_prefs".
The name of the rule is RULE and its body is BODY.

(fn RULE BODY)
(defalias 'mh-spamassassin-add-rule #[514 "\301 \302\303\"\216\304\305#\306\307\310!\311!\312!\210\313\304\314\"\315\306#\2046db\210n\203.\316\202/\317\261\210\320 \210\211?\205>\321\315!)\266\203)\207" [case-fold-search current-window-configuration make-closure #[0 "\301\300!\207" [V0 set-window-configuration] 2] 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] 10 (#$ . 12830)])
#@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 #[0 "\300\301!\302\303\304\"\305!\210dSb\210\306\307!\210\212\310\311\312\313#\203S\314\315!\312\316\317\320\"!A\262\203N\321@\"\262@\322\204@\323\202AT#\266A\262\202)\266\202)\324 \210\325\326\327!!\210\330 \210\331\332\"\210\333\315ed#\210\334ed\"\210eb\207" [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 #[514 "\211\300V\205\f\301\302#c\207" [2 format "%s %s\n"] 6 "\n\n(fn KEY VALUE)"] sort-numeric-fields reverse-region] 9 (#$ . 13454) nil])
(defvar mh-bogofilter-executable (executable-find "bogofilter"))
#@1381 Blocklist MSG with bogofilter.

Bogofilter is a Bayesian spam filtering program. Get it from your
local distribution or from the bogofilter web site at URL
`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-blocklist] and \[mh-junk-allowlist]
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.

(fn MSG)
(defalias 'mh-bogofilter-blocklist #[257 "\204\304\305!\210\306\307\"\210\310	\"\311 \210r\nq\210\312\313\314%\210\306\315\")\207" [mh-bogofilter-executable mh-current-folder mh-log-buffer mh-junk-background error "Unable to find the bogofilter executable" message "Blocklisting message %d with bogofilter..." mh-msg-filename mh-truncate-log-buffer call-process nil "-s" "Blocklisting message %d with bogofilter...done"] 8 (#$ . 14744)])
#@95 Allowlist MSG with bogofilter.

See `mh-bogofilter-blocklist' for more information.

(fn MSG)
(defalias 'mh-bogofilter-allowlist #[257 "\204\304\305!\210\306\307\"\210\310	\"\311 \210r\nq\210\312\313\314%\210\306\315\")\207" [mh-bogofilter-executable mh-current-folder mh-log-buffer mh-junk-background error "Unable to find the bogofilter executable" message "Allowlisting message %d with bogofilter..." mh-msg-filename mh-truncate-log-buffer call-process nil "-n" "Allowlisting message %d with bogofilter...done"] 8 (#$ . 16577)])
(defvar mh-spamprobe-executable (executable-find "spamprobe"))
#@645 Blocklist MSG with SpamProbe.

SpamProbe is a Bayesian spam filtering program. Get it from your
local distribution or from the SpamProbe web site at URL
`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-blocklist] and \[mh-junk-allowlist] to
update SpamProbe's training.

(fn MSG)
(defalias 'mh-spamprobe-blocklist #[257 "\204\304\305!\210\306\307\"\210\310	\"\311 \210r\nq\210\312\313\314%\210\306\315\")\207" [mh-spamprobe-executable mh-current-folder mh-log-buffer mh-junk-background error "Unable to find the spamprobe executable" message "Blocklisting message %d with spamprobe..." mh-msg-filename mh-truncate-log-buffer call-process nil "spam" "Blocklisting message %d with spamprobe...done"] 8 (#$ . 17188)])
#@93 Allowlist MSG with SpamProbe.

See `mh-spamprobe-blocklist' for more information.

(fn MSG)
(defalias 'mh-spamprobe-allowlist #[257 "\204\304\305!\210\306\307\"\210\310	\"\311 \210r\nq\210\312\313\314%\210\306\315\")\207" [mh-spamprobe-executable mh-current-folder mh-log-buffer mh-junk-background error "Unable to find the spamprobe executable" message "Allowlisting message %d with spamprobe..." mh-msg-filename mh-truncate-log-buffer call-process nil "good" "Allowlisting message %d with spamprobe...done"] 8 (#$ . 18282)])
(provide 'mh-junk)

Youez - 2016 - github.com/yon3zu
LinuXploit