mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-15 10:30:25 -08:00
Update citations of Internet RFCs
For example, RFC 822 has been obsoleted by RFC 2822, which in turn has been obsoleted by RFC 5322. * doc/emacs/ack.texi, doc/lispref/os.texi: * doc/misc/emacs-mime.texi, doc/misc/gnus-coding.texi: * doc/misc/gnus.texi, doc/misc/sc.texi: * lisp/calendar/parse-time.el, lisp/gnus/gnus-cite.el: * lisp/gnus/gnus-util.el, lisp/gnus/message.el: * lisp/gnus/mm-bodies.el, lisp/gnus/nnrss.el: * lisp/mail/feedmail.el, lisp/mail/ietf-drums.el: * lisp/mail/mail-extr.el, lisp/mail/mail-utils.el: * lisp/mail/mailclient.el, lisp/mail/mailheader.el: * lisp/mail/rfc2047.el, lisp/mail/rfc822.el, lisp/mail/rmail.el: * lisp/mail/sendmail.el, lisp/mail/smtpmail.el: * lisp/mail/supercite.el, lisp/mh-e/mh-e.el: * lisp/mh-e/mh-utils.el, lisp/net/imap.el: * lisp/net/newst-backend.el, lisp/org/org-id.el: * lisp/ps-samp.el, lisp/simple.el, lisp/url/url-util.el: Update RFC citations.
This commit is contained in:
parent
57ece2a052
commit
b5e66f46a6
32 changed files with 159 additions and 151 deletions
|
|
@ -560,7 +560,7 @@ but common in some proprietary systems."
|
|||
;; maybe some distant mail system needs it. Really, though, if you
|
||||
;; want a sender line in your mail, just put one in there and don't
|
||||
;; wait for feedmail to do it for you. (Yes, I know all about
|
||||
;; RFC-822 and RFC-1123, but are you *really* one of those cases
|
||||
;; RFC-822-or-later and RFC-1123, but are you *really* one of those cases
|
||||
;; they're talking about? I doubt it.)
|
||||
(defcustom feedmail-sender-line nil
|
||||
"If non-nil and the email has no Sender: header, use this value.
|
||||
|
|
@ -786,7 +786,7 @@ 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.
|
||||
what you're doing. Study the relevant parts of RFC-822-or-later and RFC-1123.
|
||||
Don't make me come up there!
|
||||
|
||||
You should let feedmail generate a Date: for you unless you are sure
|
||||
|
|
@ -1514,7 +1514,7 @@ function, for example, to archive all of your sent messages someplace
|
|||
|
||||
|
||||
(defvar feedmail-is-a-resend nil
|
||||
"Non-nil means the message is a Resend (in the RFC-822 sense).
|
||||
"Non-nil means the message is a Resend (in the RFC-822-or-later sense).
|
||||
This affects the composition of certain headers. feedmail sets this
|
||||
variable as soon as it starts prepping the message text buffer, so any
|
||||
user-supplied functions can rely on it. Users shouldn't set or change this
|
||||
|
|
@ -2454,7 +2454,7 @@ mapped to mostly alphanumerics for safety."
|
|||
|
||||
(let ((case-fold-search t) (addr-regexp))
|
||||
(goto-char (point-min))
|
||||
;; There are some RFC-822 combinations/cases missed here,
|
||||
;; There are some RFC-822-or-later combinations/cases missed here,
|
||||
;; but probably good enough and what users expect.
|
||||
;;
|
||||
;; Use resent-* stuff only if there is at least one non-empty one.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue