Linux ns8.secondary29.go.th 2.6.32-754.28.1.el6.x86_64 #1 SMP Wed Mar 11 18:38:45 UTC 2020 x86_64
Apache/2.2.15 (CentOS)
: 122.154.134.11 | : 122.154.134.9
Cant Read [ /etc/named.conf ]
5.6.40
apache
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
emacs /
23.1 /
lisp /
mail /
[ HOME SHELL ]
Name
Size
Permission
Action
binhex.elc
9.01
KB
-rw-r--r--
blessmail.el
2.51
KB
-rw-r--r--
emacsbug.elc
7.55
KB
-rw-r--r--
feedmail.elc
79.59
KB
-rw-r--r--
footnote.elc
21.09
KB
-rw-r--r--
hashcash.elc
10.81
KB
-rw-r--r--
mail-extr.elc
33.9
KB
-rw-r--r--
mail-hist.elc
13.74
KB
-rw-r--r--
mail-utils.elc
9.55
KB
-rw-r--r--
mailabbrev.elc
13.96
KB
-rw-r--r--
mailalias.elc
13.52
KB
-rw-r--r--
mailclient.elc
3.56
KB
-rw-r--r--
mailheader.elc
5.92
KB
-rw-r--r--
mailpost.elc
2.3
KB
-rw-r--r--
metamail.elc
4.44
KB
-rw-r--r--
mspools.elc
7.25
KB
-rw-r--r--
reporter.elc
9.65
KB
-rw-r--r--
rfc2368.elc
2.46
KB
-rw-r--r--
rfc822.elc
5.71
KB
-rw-r--r--
rmail-spam-filter.elc
13.24
KB
-rw-r--r--
rmail.elc
113.93
KB
-rw-r--r--
rmailedit.elc
8.83
KB
-rw-r--r--
rmailkwd.elc
5.12
KB
-rw-r--r--
rmailmm.elc
11.05
KB
-rw-r--r--
rmailmsc.elc
1.56
KB
-rw-r--r--
rmailout.elc
15.73
KB
-rw-r--r--
rmailsort.elc
6.33
KB
-rw-r--r--
rmailsum.elc
52.51
KB
-rw-r--r--
sendmail.elc
51.72
KB
-rw-r--r--
smtpmail.elc
21.58
KB
-rw-r--r--
supercite.elc
58.99
KB
-rw-r--r--
uce.elc
7.66
KB
-rw-r--r--
undigest.elc
7.88
KB
-rw-r--r--
unrmail.elc
4.69
KB
-rw-r--r--
uudecode.elc
6.19
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : feedmail.elc
;ELC ;;; Compiled by mockbuild@c6b8.bsys.dev.centos.org on Thu Feb 19 13:04:21 2015 ;;; from file /builddir/build/BUILD/emacs-23.1/lisp/mail/feedmail.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 "`feedmail.el' was compiled for Emacs 19.29 or later")) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; (byte-code "\301B\302\303!\210\304\305\306\"\210\307\310\311\312\313\314\313\315\316\317& \210\307\320\311\321\316\310%\210\307\322\311\323\316\310%\210\307\324\311\325\316\310%\207" [current-load-list feedmail-patch-level (lambda (#1=#:defconst-tmp-var) (defconst feedmail-patch-level #1#)) "8" autoload mail-do-fcc "sendmail" custom-declare-group feedmail nil "Assist other email packages to massage outgoing messages." :link (url-link "http://www.carpenter.org/feedmail/feedmail.html") (emacs-commentary-link "feedmail") :group mail feedmail-misc "Miscellaneous feedmail options that don't fit in other groups." feedmail-headers "Options related to manipulating specific headers or types of headers." feedmail-queue "Options related to queuing messages for later sending."] 10) #@648 *If non-nil, give a y-or-n confirmation prompt before sending mail. This is done after the message is completely prepped, and you'll be looking at the top of the message in a buffer when you get the prompt. If set to the symbol 'queued, give the confirmation prompt only while running the queue (however, the prompt is always suppressed if you are processing the queue via `feedmail-run-the-queue-no-prompts'). If set to the symbol 'immediate, give the confirmation prompt only when sending immediately. For any other non-nil value, prompt in both cases. You can give a timeout for the prompt; see variable `feedmail-confirm-outgoing-timeout'. (custom-declare-variable 'feedmail-confirm-outgoing 'nil '(#$ . -1396) :group 'feedmail-misc :type 'boolean) #@310 *If non-nil, a timeout in seconds at the send confirmation prompt. If a positive number, it's a timeout before sending. If a negative number, it's a timeout before not sending. This will not work if your version of Emacs doesn't include the function `y-or-n-p-with-timeout' (e.g., some versions of XEmacs). (custom-declare-variable 'feedmail-confirm-outgoing-timeout 'nil '(#$ . -2159) :group 'feedmail-misc :type '(choice (const nil) integer)) #@227 *If non-nil remove Bcc: lines from the message headers. In any case, the Bcc: lines do participate in the composed address list. You may want to leave them in if you're using sendmail (see `feedmail-buffer-eating-function'). (custom-declare-variable 'feedmail-nuke-bcc 't '(#$ . -2613) :group 'feedmail-headers :type 'boolean) #@241 *If non-nil remove Resent-Bcc: lines from the message headers. In any case, the Resent-Bcc: lines do participate in the composed address list. You may want to leave them in if you're using sendmail (see `feedmail-buffer-eating-function'). (custom-declare-variable 'feedmail-nuke-resent-bcc 't '(#$ . -2948) :group 'feedmail-headers :type 'boolean) #@1233 *Where Bcc:/Resent-Bcc: addresses should appear in the envelope list. Addresses for the message envelope are deduced by examining appropriate address headers in the message. Generally, they will show up in the list of deduced addresses in the order that the headers happen to appear (duplicate addresses are eliminated in any case). This variable can be set to the symbol 'first, in which case the Bcc:/Resent-Bcc: addresses will appear at the beginning in the list; or, it can be set to the symbol 'last, in which case they will appear at the end of the list. Why should you care? Well, maybe you don't, and certainly the same things could be accomplished by affecting the order of message headers in the outgoing message. Some people use Bcc: as a way of getting their own "come back" copy of each message they send. If Bcc: addresses are not handled first, there can be substantial delays in seeing the message again. Some configurations of sendmail, for example, seem to try to deliver to each addressee at least once, immediately and serially, so slow SMTP conversations can add up to a delay. There is an option for either 'first or 'last because you might have a delivery agent that processes the addresses backwards. (custom-declare-variable 'feedmail-deduce-bcc-where 'nil '(#$ . -3305) :group 'feedmail-headers :type 'boolean) #@386 *If non-nil do smart filling of addressee header lines. Smart filling means breaking long lines at appropriate points and making continuation lines. Despite the function name, it includes To:, Cc:, Bcc: (and their Resent-* forms), as well as From: and Reply-To: (though they seldom need it). If nil, the lines are left as-is. The filling is done after mail address alias expansion. (custom-declare-variable 'feedmail-fill-to-cc 't '(#$ . -4656) :group 'feedmail-headers :type 'boolean) #@45 *Fill column used by `feedmail-fill-to-cc'. (custom-declare-variable 'feedmail-fill-to-cc-fill-column 'default-fill-column '(#$ . -5151) :group 'feedmail-headers :type 'integer) #@288 *If non-nil remove [Resent-]Bcc: lines in message copies saved via Fcc:. This is independent of whether the Bcc: header lines are actually sent with the message (see feedmail-nuke-bcc). Though not implied in the name, the same Fcc: treatment applies to both Bcc: and Resent-Bcc: lines. (custom-declare-variable 'feedmail-nuke-bcc-in-fcc 'nil '(#$ . -5336) :group 'feedmail-headers :type 'boolean) #@280 *If non-nil remove body of message in copies saved via Fcc:. If a positive integer value, leave (up to) that many lines of the beginning of the body intact. The result is that the Fcc: copy will consist only of the message headers, serving as a sort of an outgoing message log. (custom-declare-variable 'feedmail-nuke-body-in-fcc 'nil '(#$ . -5741) :group 'feedmail-headers :type '(choice (const nil) (const t) integer)) #@333 *If non-nil, force the calling of `expand-mail-aliases'. Normally, feedmail tries to figure out if you're using mailalias or mailabbrevs and only calls `expand-mail-aliases' if it thinks you're using the mailalias package. This user option can be used to force the issue since there are configurations which fool the figuring out. (custom-declare-variable 'feedmail-force-expand-mail-aliases 'nil '(#$ . -6170) :group 'feedmail-headers :type 'boolean) #@368 *If non-nil, remove header lines which have no contents. A completely empty Subject: header is always removed, regardless of the setting of this variable. The only time you would want them left in would be if you used some headers whose presence indicated something rather than their contents. This is rare in Internet email but common in some proprietary systems. (custom-declare-variable 'feedmail-nuke-empty-headers 't '(#$ . -6630) :group 'feedmail-headers :type 'boolean) #@1218 *If non-nil and the email has no Sender: header, use this value. May be nil, in which case nothing in particular is done with respect to Sender: lines. By design, will not replace an existing Sender: line, but you can achieve that with a fiddle-plex 'replace action. NB: it makes no sense to use the value t since there is no sensible default for Sender:. If not nil, it may be a string, a fiddle-plex, or a function which returns either nil, t, a string, or a fiddle-plex (or, in fact, another function, but let's not be ridiculous). If a string, it should be just the contents of the header, not the name of the header itself nor the trailing newline. If a function, it will be called with no arguments. For an explanation of fiddle-plexes, see the documentation for the variable `feedmail-fiddle-plex-blurb'. In all cases the name element of the fiddle-plex is ignored and is hardwired by feedmail to either "X-Sender" or "X-Resent-Sender". You can probably leave this nil, but if you feel like using it, a good value would be a string of a fully-qualified domain name form of your address. For example, "bill@bubblegum.net (WJCarpenter)". The Sender: header is fiddled after the From: header is fiddled. (custom-declare-variable 'feedmail-sender-line 'nil '(#$ . -7117) :group 'feedmail-headers :type '(choice (const nil) string)) #@452 *If non-nil, force writing file as binary (this applies to queues and Fcc:). On systems where there is a difference between binary and text files, feedmail will temporarily manipulate the values of `buffer-file-type' and/or `default-buffer-file-type' to make the writing as binary. If nil, writing will be in text mode. On systems where there is no distinction or where it is controlled by other variables or other means, this option has no effect. (custom-declare-variable 'feedmail-force-binary-write 't '(#$ . -8468) :group 'feedmail-misc :type 'boolean) #@1418 *If non-nil and the email has no From: header, use this value. May be t, in which case a default is computed (and you probably won't be happy with it). May be nil, in which case nothing in particular is done with respect to From: lines. By design, will not replace an existing From: line, but you can achieve that with a fiddle-plex 'replace action. If neither nil nor t, it may be a string, a fiddle-plex, or a function which returns either nil, t, a string, or a fiddle-plex (or, in fact, another function, but let's not be ridiculous). If a string, it should be just the contents of the header, not the name of the header itself nor the trailing newline. If a function, it will be called with no arguments. For an explanation of fiddle-plexes, see the documentation for the variable `feedmail-fiddle-plex-blurb'. In all cases the name element of the fiddle-plex is ignored and is hardwired by feedmail to either "X-From" or "X-Resent-From". A good value would be a string fully-qualified domain name form of your address. For example, "bill@bubblegum.net (WJCarpenter)". The default value of this variable uses the standard elisp variable `user-mail-address' which should be set on every system but has a decent chance of being wrong. It also honors `mail-from-style'. Better to set this variable explicitly to the string you want or find some other way to arrange for the message to get a From: line. (custom-declare-variable 'feedmail-from-line 't '(#$ . -9036) :group 'feedmail-headers :type '(choice (const t) (const nil) string)) #@1348 *If non-nil, deduce message envelope "from" from header From: or Sender:. In other words, if there is a Sender: header in the message, temporarily change the value of `user-mail-address' to be the same while the message is being sent. If there is no Sender: header, use the From: header, if any. Address values are taken from the actual message just before it is sent, and the process is independent of the values of `feedmail-from-line' and/or `feedmail-sender-line'. There are many and good reasons for having the message header From:/Sender: be different from the message envelope "from" information. However, for most people and for most circumstances, it is usual for them to be the same (this is probably especially true for the case where the user doesn't understand the difference between the two in the first place). The idea behind this feature is that you can have everything set up some normal way for yourself. If for some reason you want to send a message with another From: line, you can just type it at the top of the message, and feedmail will take care of "fixing up" the envelope "from". This only works for mail senders which make use of `user-mail-address' as the envelope "from" value. For some mail senders (e.g., feedmail-buffer-to-bin-mail), there is no simple way to influence what they will use as the envelope. (custom-declare-variable 'feedmail-deduce-envelope-from 't '(#$ . -10594) :group 'feedmail-headers :type 'boolean) #@30 *See feedmail-x-mailer-line. (custom-declare-variable 'feedmail-x-mailer-line-user-appendage 'nil '(#$ . -12062) :group 'feedmail-headers :type '(choice (const nil) (const t) string)) #@1339 *Control the form of an X-Mailer: header in an outgoing message. Moderately useful for debugging, keeping track of your correspondents' mailer preferences, or just wearing your MUA on your sleeve. You should probably know that some people are fairly emotional about the presence of X-Mailer: lines in email. If nil, nothing is done about X-Mailer:. If t, an X-Mailer: header of a predetermined format is produced, combining its efforts with any existing X-Mailer: header. If you want to take the default construct and just add a little blob of your own at the end, define the variable feedmail-x-mailer-line-user-appendage as that blob string. A value of t is equivalent to using the function feedmail-default-x-mailer-generator. If neither nil nor t, it may be a string, a fiddle-plex, or a function which returns either nil, t, a string, or a fiddle-plex (or, in fact, another function, but let's not be ridiculous). If a string, it should be just the contents of the header, not the name of the header itself nor the trailing newline. If a function, it will be called with no arguments. For an explanation of fiddle-plexes, see the documentation for the variable `feedmail-fiddle-plex-blurb'. In all cases the name element of the fiddle-plex is ignored and is hardwired by feedmail to either "X-Mailer" or "X-Resent-Mailer". (custom-declare-variable 'feedmail-x-mailer-line 't '(#$ . -12254) :group 'feedmail-headers :type '(choice (const t) (const nil) string function)) #@1318 *Specifies the creation of a Message-Id: header field. If nil, nothing is done about Message-Id:. If t, a Message-Id: header of a predetermined format is produced, but only if there is not already a Message-Id: in the message. A value of t is equivalent to using the function feedmail-default-message-id-generator. If neither nil nor t, it may be a string, a fiddle-plex, or a function which returns either nil, t, a string, or a fiddle-plex (or, in fact, another function, but let's not be ridiculous). If a string, it should be just the contents of the header, not the name of the header itself nor the trailing newline. If a function, it will be called with one argument: the possibly-nil name of the file associated with the message buffer. For an explanation of fiddle-plexes, see the documentation for the variable `feedmail-fiddle-plex-blurb'. In all cases the name element of the fiddle-plex is ignored and is hardwired by feedmail to either "Message-Id" or "Resent-Message-Id". You should let feedmail generate a Message-Id: for you unless you are sure that whatever you give your messages to will do it for you (e.g., most configurations of sendmail). Even if the latter case is true, it probably won't hurt you to generate your own, and it will then show up in the saved message if you use Fcc:. (custom-declare-variable 'feedmail-message-id-generator 't '(#$ . -13747) :group 'feedmail-headers :type '(choice (const t) (const nil) function)) #@554 *If non-nil, used as a suffix for generating unique Message-Id: headers. The function `feedmail-default-message-id-generator' creates its work based on a formatted date-time string, a random number, and a domain-looking suffix. You can control the suffix used by assigning a string value to this variable. If you don't supply one, the value of the variable `user-mail-address' will be used. If the value of `feedmail-message-id-suffix' contains an "@" character, the string will be used verbatim, else an "@" character will be prepended automatically. (custom-declare-variable 'feedmail-message-id-suffix 'nil '(#$ . -15218) :group 'feedmail-headers :type '(choice (const nil) string)) #@1444 *Specifies the creation of a Date: header field. If nil, nothing is done about Date:. If t, a Date: header of a predetermined format is produced, but only if there is not already a Date: in the message. A value of t is equivalent to using the function `feedmail-default-date-generator'. If neither nil nor t, it may be a string, a fiddle-plex, or a function which returns either nil, t, a string, or a fiddle-plex (or, in fact, another function, but let's not be ridiculous). If a string, it should be just the contents of the header, not the name of the header itself nor the trailing newline. If a function, it will be called with one argument: the possibly-nil name of the file associated with the message buffer. For an explanation of fiddle-plexes, see the documentation for the variable `feedmail-fiddle-plex-blurb'. In all cases the name element of the fiddle-plex is ignored and is hardwired by feedmail to either "Date" or "Resent-Date". If you decide to format your own date field, do us all a favor and know what you're doing. Study the relevant parts of RFC-822 and RFC-1123. Don't make me come up there! You should let feedmail generate a Date: for you unless you are sure that whatever you give your messages to will do it for you (e.g., most configurations of sendmail). Even if the latter case is true, it probably won't hurt you to generate your own, and it will then show up in the saved message if you use Fcc:. (custom-declare-variable 'feedmail-date-generator 't '(#$ . -15913) :group 'feedmail-headers :type '(choice (const t) (const nil) function)) #@352 *Non-nil means fiddled header fields should go at the top of the header. nil means insert them at the bottom. This is mostly a novelty issue since the standards define the ordering of header fields to be immaterial and it's fairly likely that some MTA along the way will have its own idea of what the order should be, regardless of what you specify. (custom-declare-variable 'feedmail-fiddle-headers-upwardly 't '(#$ . -17504) :group 'feedmail-headers :type 'boolean) #@626 If non-nil, should be a list of one or more fiddle-plexes. Each element of the list can also be a function which returns a fiddle-plex. feedmail will use this list of fiddle-plexes to manipulate user-specified message header fields. It does this after it has completed all normal message header field manipulation and before calling `feedmail-last-chance-hook'. For an explanation of fiddle-plexes, see the documentation for the variable `feedmail-fiddle-plex-blurb'. In contrast to some other fiddle-plex manipulation functions, in this context, it makes no sense to have an element which is nil, t, or a simple string. (custom-declare-variable 'feedmail-fiddle-plex-user-list 'nil '(#$ . 17980) :group 'feedmail-headers :type '(repeat (choice function) sexp)) #@1077 If non-nil, transmit message separately to each addressee. feedmail normally accumulates a list of addressees and passes the message along with that list to a buffer-eating function which expects any number of addressees. If this variable is non-nil, however, feedmail will repeatedly call the same buffer-eating function. Each time, the list of addressees will be just one item from the original list. This only affects the message envelope addresses and doesn't affect what appears in the message headers except as noted. Spray mode is usually pointless, and if you can't think of a good reason for it, you should avoid it since it is inherently less efficient than normal multiple delivery. One reason to use it is to overcome mis-featured mail transports which betray your trust by revealing Bcc: addressees in the headers of a message. Another use is to do a crude form of mailmerge, for which see `feedmail-spray-address-fiddle-plex-list'. If one of the calls to the buffer-eating function results in an error, what happens next is carelessly defined, so beware. (custom-declare-variable 'feedmail-enable-spray 'nil '(#$ . 18754) :group 'feedmail-spray :type 'boolean) #@85 Do not set or change this variable. See `feedmail-spray-address-fiddle-plex-list'. (defvar feedmail-spray-this-address nil (#$ . 19942)) #@2241 User-supplied specification for a crude form of mailmerge capability. When spraying is enabled, feedmail composes a list of envelope addresses. In turn, `feedmail-spray-this-address' is temporarily set to each address (stripped of any comments and angle brackets) and calls a function which fiddles message headers according to this variable. See the documentation for `feedmail-fiddle-plex-blurb', for an overview of fiddle-plex data structures. May be nil, in which case nothing in particular is done about message headers for specific addresses. May be t, in which case a "To:" header is added to the message with the stripped address as the header contents. The fiddle-plex operator is 'supplement. May be a string, in which case the string is assumed to be the name of a message header field with the stripped address serving as the value. The fiddle-plex operator is 'supplement. May be a function, in which case it is called with no arguments and is expected to return nil, t, a string, another function, or a fiddle-plex. The result is used recursively. May be a list of any combination of the foregoing and fiddle-plexes. (A value for this variable which consists of a single fiddle-plex must be nested inside another list to avoid ambiguity.) If a list, each item is acted on in turn as described above. For example, (setq feedmail-spray-address-fiddle-plex-list 'my-address-embellisher) The idea of the example is that, during spray mode, as each message is about to be transmitted to an individual address, the function will be called and will consult `feedmail-spray-this-address' to find the stripped envelope email address (no comments or angle brackets). The function should return an embellished form of the address. The recipe for sending form letters is: (1) create a message with all addressees on Bcc: headers; (2) tell feedmail to remove Bcc: headers before sending the message; (3) create a function which will embellish stripped addresses, if desired; (4) define `feedmail-spray-address-fiddle-plex-list' appropriately; (5) send the message with `feedmail-enable-spray' set non-nil; (6) stand back and watch co-workers wonder at how efficient you are at accomplishing inherently inefficient things. (custom-declare-variable 'feedmail-spray-address-fiddle-plex-list 'nil '(#$ . 20088) :group 'feedmail-spray :type 'sexp) #@1235 *If non-nil, provide for stashing outgoing messages in a queue. This is the master on/off switch for feedmail message queuing. Queuing is quite handy for laptop-based users. It's also handy if you get a lot of mail and process it more or less sequentially. For example, you might change your mind about contents of a reply based on a message you see a bit later. There is a separate queue for draft messages, intended to prevent you from accidentally sending incomplete messages. The queues are disk-based and intended for later transmission. The messages are queued in their raw state as they appear in the mail-mode buffer and can be arbitrarily edited later, before sending, by visiting the appropriate file in the queue directory (and setting the buffer to mail-mode or whatever). If you visit a file in the queue directory and try to queue it again, it will just get saved in its existing file name. You can move a message from the draft to the main queue or vice versa by pretending to send it and then selecting whichever queue directory you want at the prompt. The right thing will happen. To transmit all the messages in the queue, invoke the command `feedmail-run-the-queue' or `feedmail-run-the-queue-no-prompts'. (custom-declare-variable 'feedmail-enable-queue 'nil '(#$ . -22457) :group 'feedmail-queue :type 'boolean) #@283 *If non-nil, give a y-or-n confirmation prompt before running the queue. Prompt even if the queue is about to be processed as a result of a call to `feedmail-run-the-queue-no-prompts'. This gives you a way to bail out without having to answer no to the individual message prompts. (custom-declare-variable 'feedmail-queue-runner-confirm-global 'nil '(#$ . -23805) :group 'feedmail-queue :type 'boolean) #@172 *Name of a directory where messages will be queued. Directory will be created if necessary. Should be a string that doesn't end with a slash. Default is "$HOME/mail/q". (custom-declare-variable 'feedmail-queue-directory '(concat (getenv "HOME") "/mail/q") '(#$ . -24216) :group 'feedmail-queue :type 'string) #@182 *Name of a directory where draft messages will be queued. Directory will be created if necessary. Should be a string that doesn't end with a slash. Default is "$HOME/mail/draft". (custom-declare-variable 'feedmail-queue-draft-directory '(concat (getenv "HOME") "/mail/draft") '(#$ . -24534) :group 'feedmail-queue :type 'string) #@366 *If non-nil, feedmail will ask what you want to do with the message. Default choices for the message action prompt will include sending it immediately, putting it in the main queue, putting it in the draft queue, or returning to the buffer to continue editing. Only matters if queuing is enabled. If nil, the message is placed in the main queue without a prompt. (custom-declare-variable 'feedmail-ask-before-queue 't '(#$ . -24872) :group 'feedmail-queue :type 'boolean) #@161 *A string which will be used for the message action prompt. If it contains a "%s", that will be replaced with the value of `feedmail-ask-before-queue-default'. (custom-declare-variable 'feedmail-ask-before-queue-prompt '"FQM: Message action (q, i, d, e, ?)? [%s]: " '(#$ . -25353) :group 'feedmail-queue :type 'string) #@166 *A string which will be used for repompting after invalid input. If it contains a "%s", that will be replaced with the value of `feedmail-ask-before-queue-default'. (custom-declare-variable 'feedmail-ask-before-queue-reprompt '"FQM: Please type q, i, d, or e; or ? for help [%s]: " '(#$ . -25679) :group 'feedmail-queue :type 'string) #@239 *Meaning if user hits return in response to the message action prompt. Should be a character or a string; if a string, only the first character is significant. Useful values are those described in the help for the message action prompt. (custom-declare-variable 'feedmail-ask-before-queue-default '"queue" '(#$ . -26021) :group 'feedmail-queue :type '(choice string integer)) #@571 An alist of choices for the message action prompt. All of the values are function names, except help, which is a special symbol that calls up help for the prompt (the help describes the actions from the standard alist). To customize your own choices, define a similar alist called `feedmail-prompt-before-queue-user-alist'. The actual alist used for message action will be the standard alist overlaid with the user-alist. To neutralize an item in the standard alist without providing a replacement, define an appropriate element in the user alist with a value of nil. (defvar feedmail-prompt-before-queue-standard-alist '((113 . feedmail-message-action-queue) (81 . feedmail-message-action-queue-strong) (100 . feedmail-message-action-draft) (114 . feedmail-message-action-draft) (68 . feedmail-message-action-draft-strong) (82 . feedmail-message-action-draft-strong) (101 . feedmail-message-action-edit) (69 . feedmail-message-action-edit) (7 . feedmail-message-action-edit) (110 . feedmail-message-action-edit) (78 . feedmail-message-action-edit) (105 . feedmail-message-action-send) (73 . feedmail-message-action-send-strong) (115 . feedmail-message-action-send) (83 . feedmail-message-action-send-strong) (42 . feedmail-message-action-toggle-spray) (22 . feedmail-message-action-help) (63 . feedmail-message-action-help)) (#$ . 26405)) #@52 See `feedmail-prompt-before-queue-standard-alist'. (custom-declare-variable 'feedmail-prompt-before-queue-user-alist 'nil '(#$ . 27753) :group 'feedmail-queue :type '(repeat (cons character function))) #@577 User-provided supplementary help string for the message action prompt. When the message action prompt is shown, the user can as for verbose help, at which point a buffer pops up describing the meaning of possible responses to the prompt. Through various customizations (see, for example, `feedmail-prompt-before-queue-user-alist'), the available responses and the prompt itself can be changed. If this variable is set to a string value, that string is written to the help buffer after the standard info. It may contain embedded line breaks. It will be printed via `princ'. (custom-declare-variable 'feedmail-prompt-before-queue-help-supplement 'nil '(#$ . 27962) :group 'feedmail-queue :type '(choice (const nil) string)) #@32 See `feedmail-queue-reminder'. (custom-declare-variable 'feedmail-queue-reminder-alist ''((after-immediate . feedmail-queue-reminder-brief) (after-queue . feedmail-queue-reminder-medium) (after-draft . feedmail-queue-reminder-medium) (after-run . feedmail-queue-reminder-brief) (on-demand . feedmail-run-the-queue-global-prompt)) '(#$ . 28693) :group 'feedmail-queue :type '(repeat (cons (choice :tag "Event" (const on-demand) (const after-immediate) (const after-queue) (const after-draft) (const after-run)) function))) #@322 *If non-nil, blat a few status messages and such in the mini-buffer. If nil, just do the work and don't pester people about what's going on. In some cases, though, specific options inspire mini-buffer prompting. That's not affected by this variable setting. Also does not control reporting of error/abnormal conditions. (custom-declare-variable 'feedmail-queue-chatty 't '(#$ . -29222) :group 'feedmail-queue :type 'boolean) #@200 *Duration of pause after most queue-related messages. After some messages are divulged, it is prudent to pause before something else obliterates them. This value controls the duration of the pause. (custom-declare-variable 'feedmail-queue-chatty-sit-for '2 '(#$ . -29655) :group 'feedmail-queue :type 'integer) #@504 *If non-nil, name a function which will sort the queued messages. The function is called during a running of the queue for sending, and takes one argument, a list of the files in the queue directory. It may contain the names of non-message files, and it's okay to leave them in the list when reordering it; they get skipped over later. When nil, the default action processes the messages in normal sort order by queued file name, which will typically result in the order they were placed in the queue. (custom-declare-variable 'feedmail-queue-run-orderer 'nil '(#$ . -29974) :group 'feedmail-queue :type '(choice (const nil) function)) #@317 *If non-nil, use send time for the Date: header value. This variable is used by the default date generating function, feedmail-default-date-generator. If nil, the default, the last-modified timestamp of the queue file is used to create the message Date: header; if there is no queue file, the current time is used. (custom-declare-variable 'feedmail-queue-use-send-time-for-date 'nil '(#$ . -30618) :group 'feedmail-queue :type 'boolean) #@344 *If non-nil, use send time for the Message-Id: header value. This variable is used by the default Message-Id: generating function, `feedmail-default-message-id-generator'. If nil, the default, the last-modified timestamp of the queue file is used to create the message Message-Id: header; if there is no queue file, the current time is used. (custom-declare-variable 'feedmail-queue-use-send-time-for-message-id 'nil '(#$ . -31064) :group 'feedmail-queue :type 'boolean) #@705 *If non-nil, prompt user for part of the queue file name. The file will automatically get the FQM suffix and an embedded sequence number for uniqueness, so don't specify that. feedmail will get rid of all characters other than alphanumeric and hyphen in the results. If this variable is nil or if you just hit return in response to the prompt, feedmail queuing will take care of things properly. At the prompt, completion is available if you want to see what filenames are already in use, though, as noted, you will not be typing a complete file name. You probably don't want to be bothered with this prompting since feedmail, by default, uses queue file names based on the subjects of the messages. (custom-declare-variable 'feedmail-ask-for-queue-slug 'nil '(#$ . -31543) :group 'feedmail-queue :type 'boolean) #@406 *If non-nil, a function which creates part of the queued file name. Takes a single argument giving the name of the directory into which the message will be queued. The returned string should be just the non-directory filename part, without FQM suffix or uniquifying sequence numbers. The current buffer holds the raw message. The default function creates the slug based on the message subject, if any. (custom-declare-variable 'feedmail-queue-slug-maker ''feedmail-queue-subject-slug-maker '(#$ . -32367) :group 'feedmail-queue :type '(choice (const nil) function)) #@843 *Indicates what to use for subject-less messages when forming a file name. When feedmail queues a message, it creates a unique file name. By default, the file name is based in part on the subject of the message being queued. If there is no subject, consult this variable. See documentation for the function `feedmail-queue-subject-slug-maker'. If t, an innocuous default is used. If a string, it is used directly. If a function, it is called with no arguments from the buffer containing the raw text of the message. It must return a string (which may be empty). If the symbol 'ask, you will be prompted for a string in the mini-buffer. Filename completion is available so that you can inspect what's already been used, but feedmail will do further manipulation on the string you return, so it's not expected to be a complete filename. (custom-declare-variable 'feedmail-queue-default-file-slug 't '(#$ . -32943) :group 'feedmail-queue :type '(choice (const :tag "Default" t) string function (const ask))) #@356 *The FQM suffix used to distinguish feedmail queued message files. You probably want this to be a period followed by some letters and/or digits. The distinction is to be able to tell them from other random files that happen to be in the `feedmail-queue-directory' or `feedmail-queue-draft-directory'. By the way, FQM stands for feedmail queued message. (custom-declare-variable 'feedmail-queue-fqm-suffix '".fqm" '(#$ . -33962) :group 'feedmail-queue :type 'string) #@419 *If non-nil, silently kill the buffer after a message is queued. You might like that since a side-effect of queueing the message is that its buffer name gets changed to the filename. That means that the buffer won't be reused for the next message you compose. If you are using VM for creating messages, you probably want to leave this nil, since VM has its own options for managing the recycling of message buffers. (custom-declare-variable 'feedmail-nuke-buffer-after-queue 'nil '(#$ . -34437) :group 'feedmail-queue :type 'boolean) #@391 *If non-nil, automatically delete queue files when a message is sent. Normally, feedmail will notice such files when you send a message in immediate mode (i.e., not when you're running the queue) and will ask if you want to delete them. Since the answer is usually yes, setting this variable to non-nil will tell feedmail to skip the prompt and just delete the file without bothering you. (custom-declare-variable 'feedmail-queue-auto-file-nuke 'nil '(#$ . -34980) :group 'feedmail-queue :type 'boolean) (byte-code "\301B\302\301!\204 \303\301\304\"\210\305B\302\305!\204 \303\305\304\"\210\306B\302\306!\204- \303\306\304\"\210\307B\302\307!\204<