unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: bug-gnu-emacs@gnu.org
Subject: bug#7789: cannot send smtpmail using gmail & tls on woe32
Date: Mon, 17 Jan 2011 17:47:28 -0500	[thread overview]
Message-ID: <E1PexrE-0005Hf-Qo@fencepost.gnu.org> (raw)
In-Reply-To: <84k4i4x87t.wl%claudio.bley@gmail.com>

> From: claudio.bley@gmail.com (Claudio Bley)
> Date: Mon, 17 Jan 2011 09:09:10 +0100
> 
> gnutls-cli waits for a SIGALRM to initiate the STARTTLS handshake --
> which Emacs isn't able to send -- or, alternatively, an EOF -- which
> doesn't work because communication is done over a pipe instead of a
> PTY.

Is this a bug in the ported gnutls, in Emacs, or in both?

> I'm using cygwin's gnutls-cli and have hacked ssl.el in order to
> replace the signal-process calls with (call-process "kill.exe" nil nil
> nil "-ALRM" PID). This works because cygwin provides its own layer of
> signal handling and is able to send / receive the SIGALRM signal.

How about making that hack part of Emacs?  It could be conditioned on
running on Windows.

TIA





  reply	other threads:[~2011-01-17 22:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 15:05 bug#7789: cannot send smtpmail using gmail & tls on woe32 Sam Steingold
2011-01-05 16:16 ` Eli Zaretskii
2011-01-05 17:55   ` Sam Steingold
2011-01-05 20:06     ` Sam Steingold
2011-01-05 21:02       ` Eli Zaretskii
2011-06-26  1:52         ` Glenn Morris
2011-01-05 23:09     ` Jason Rumney
2011-01-05 23:31       ` Sam Steingold
2011-01-06  9:29         ` Eli Zaretskii
2011-01-06 23:13           ` Sam Steingold
2011-01-07  7:43             ` Eli Zaretskii
2011-01-07 18:55               ` Sam Steingold
2011-01-07 20:09                 ` Eli Zaretskii
2011-01-17  8:09             ` Claudio Bley
2011-01-17 22:47               ` Eli Zaretskii [this message]
2011-01-18 15:33                 ` Claudio Bley
2011-01-18 22:45                   ` Eli Zaretskii
2011-01-21 14:32                     ` Claudio Bley
2011-02-06 21:42                       ` Claudio Bley

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1PexrE-0005Hf-Qo@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=bug-gnu-emacs@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).