Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
1bd6cd6c
Commit
1bd6cd6c
authored
Dec 03, 2008
by
Katsumi Yamaoka
Browse files
(message-idna-to-ascii-rhs-1): Fix previous commit.
(message-idna-to-ascii-rhs): Add a comment. Suggested by RMS.
parent
f7ede2fa
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
5 deletions
+10
-5
lisp/gnus/message.el
lisp/gnus/message.el
+10
-5
No files found.
lisp/gnus/message.el
View file @
1bd6cd6c
...
...
@@ -5635,14 +5635,13 @@ subscribed address (and not the additional To and Cc header contents)."
(
dolist
(
rhs
(
mm-delete-duplicates
(
mapcar
(
lambda
(
rhs
)
(
or
(
cadr
(
split-string
rhs
"@"
))
""
))
(
mapcar
(
lambda
(
domain
)
(
if
domain
(
downcase
domain
)
""
))
(
mapcar
'downcase
(
mapcar
'cadr
(
mail-extract-address-components
field
t
))))))
(
setq
ace
(
if
(
string-match
"\\`[[:ascii:]]+\\'"
rhs
)
;; Note that `rhs' will be "" if the address does not have
;; the domain part, i.e., if it is a local user's address.
(
setq
ace
(
if
(
string-match
"\\`[[:ascii:]]*\\'"
rhs
)
rhs
(
downcase
(
idna-to-ascii
rhs
))))
(
when
(
and
(
not
(
equal
rhs
ace
))
...
...
@@ -5664,6 +5663,12 @@ See `message-idna-encode'."
(
when
message-use-idna
(
save-excursion
(
save-restriction
;; `message-narrow-to-head' that recognizes only the first empty
;; line as the message header separator used to be used here.
;; However, since there is the "--text follows this line--" line
;; normally, it failed in narrowing to the headers and potentially
;; caused the IDNA encoding on lines that look like headers in
;; the message body.
(
message-narrow-to-headers-or-head
)
(
message-idna-to-ascii-rhs-1
"From"
)
(
message-idna-to-ascii-rhs-1
"To"
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment