From: "Francesco Potortì" <pot@gnu.org>
To: 47616@debbugs.gnu.org
Subject: bug#47616: 27.1; hardening mail-envelope-from
Date: Tue, 06 Apr 2021 14:42:41 +0200 [thread overview]
Message-ID: <87v98z60u4.fsf@tucano.isti.cnr.it> (raw)
in mail-utils.el the function mail-fetch-field thus notes in the doc
string:
The buffer should be narrowed to just the header, else false
matches may be returned from the message body.
In fact, both sendmail-send-it and smtp-send-it use mail-envelope-from,
which calls mail-fetch-field without narrowing, which in fact causes a
false match if:
- you forward a message with "From: " at begining of line
- message-forward-as-mime is nil
- mail-specify-envelope-from is t
- mail-envelope-from is 'header
In this case, both sendmail-send-it and smptmail-send-it try to see if
they should set the From: field and the sender, and both get a false
match from mail-envelope-from.
Apparently, the problem with sendmail-send-it is corrected later in the
code (I don't know where) so the mail is sent correctly, which is why I
had never realised this until I started using smtpmail-send-it, which
sets a wrong From: header copied from the forwarded message.
Hardening mail-envelope-from from sendmail.el by narrowing to the
headers, as the doc says, corrects the problem that I observed.
(defun mail-envelope-from ()
"Return the envelope mail address to use when sending mail.
This function uses `mail-envelope-from'."
(or (if (eq mail-envelope-from 'header)
(nth 1 (mail-extract-address-components
(save-restriction
(save-excursion
(goto-char (point-max))
(re-search-backward
(concat "^" (regexp-quote mail-header-separator) "\n")
nil t)
(narrow-to-region (point-min) (point))
(mail-fetch-field "From")))))
mail-envelope-from)
user-mail-address))
This introduces a small semantic change for the meaning of the
mail-envelope-from variable. Currently, the docs says:
If non-nil, designate the envelope-from address when sending mail.
This only has an effect if `mail-specify-envelope-from’ is non-nil.
The value should be either a string, or the symbol `header’ (in
which case the contents of the "From" header of the message
being sent is used), or nil (in which case the value of
‘user-mail-address’ is used).
The last two lines should be instead:
...
being sent is used, if one exists). If the value is nil, or if it is
`header' and no "From" header is found in the message, the value of
‘user-mail-address’ is used.
next reply other threads:[~2021-04-06 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 12:42 Francesco Potortì [this message]
2021-04-07 15:05 ` bug#47616: 27.1; hardening mail-envelope-from Francesco Potortì
2021-05-06 10:22 ` Lars Ingebrigtsen
2021-05-06 12:16 ` Francesco Potortì
2021-05-07 11:17 ` Lars Ingebrigtsen
2021-05-07 11:33 ` Eli Zaretskii
2021-05-07 12:09 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v98z60u4.fsf@tucano.isti.cnr.it \
--to=pot@gnu.org \
--cc=47616@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.