From: Wolfram Fenske <Wolfram.Fenske@Student.Uni-Magdeburg.DE>
To: ding@gnus.org
Subject: The return of starttls doesn't work in smtpmail
Date: Fri, 17 Aug 2007 04:21:48 +0200 [thread overview]
Message-ID: <86d4xmyk77.fsf@hondo.cadr.de> (raw)
Hello!
After upgrading my Gnus I couldn't send mail via smtpmail+starttls
anymore. The reason was that it uses the function `with-no-warnings',
which isn't defined in XEmacs. After finding and fixing the problem
myself it turns out this is a known problem:
<http://calypso.tux.org/pipermail/xemacs-beta/2007-March/010883.html>
Back then, Simon Josefsson's response was:
--8<---------------cut here---------------start------------->8---
> Simon, I think that the best thing would be to just get rid of the
> with-no-warnings call (unless you know of bogus warnings that will
> definitely be issued), and we probably ought to change the
> condition-case to catch 'io-error, which will catch all exceptions due
> to expectable process failures.
There are several uses of with-no-warnings in modern elisp, how about
if XEmacs implements it? The implementation seems straight forward,
here is what my Emacs has:
(put 'with-no-warnings 'lisp-indent-function 0)
(defun with-no-warnings (&rest body)
"Like `progn', but prevents compiler warnings in the body."
;; The implementation for the interpreter is basically trivial.
(car (last body)))
Thanks for the CC.
--8<---------------cut here---------------end--------------->8---
According to
<http://quimby.gnus.org/cgi-bin/cvsweb.cgi/gnus/contrib/smtpmail.el>,
smptmail.el still isn't fixed. Since I can't change XEmacs, as Simon
proposed, I suggest to add the following code to smtpmail.el or
gnus.el or whichever place is appropriate, to prevent even more people
from getting bitten by this:
--8<---------------cut here---------------start------------->8---
;;; XEmacs and older Emacs might not have `with-no-warnings'
(unless (fboundp 'with-no-warnings)
;; Taken from Emacs' byte-run.el
(defun with-no-warnings (&rest body)
"Like `progn', but prevents compiler warnings in the body."
;; The implementation for the interpreter is basically trivial.
(car (last body))))
--8<---------------cut here---------------end--------------->8---
--
Wolfram Fenske
A: Yes.
>Q: Are you sure?
>>A: Because it reverses the logical flow of conversation.
>>>Q: Why is top posting frowned upon?
next reply other threads:[~2007-08-17 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 2:21 Wolfram Fenske [this message]
2007-08-17 8:30 ` Reiner Steib
2007-08-19 21:17 ` Wolfram Fenske
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=86d4xmyk77.fsf@hondo.cadr.de \
--to=wolfram.fenske@student.uni-magdeburg.de \
--cc=ding@gnus.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).