From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Reitter Newsgroups: gmane.emacs.devel Subject: Re: mailclient-send-it usage of browse-url Date: Tue, 13 Apr 2010 18:06:25 -0400 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1271197118 26360 80.91.229.12 (13 Apr 2010 22:18:38 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 13 Apr 2010 22:18:38 +0000 (UTC) Cc: emacs-devel@gnu.org To: Christian Lynbech Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 14 00:18:36 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1O1oRH-0003St-SH for ged-emacs-devel@m.gmane.org; Wed, 14 Apr 2010 00:18:36 +0200 Original-Received: from localhost ([127.0.0.1]:49600 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O1oRG-0003U6-Jm for ged-emacs-devel@m.gmane.org; Tue, 13 Apr 2010 18:18:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O1oNr-0002a0-OM for emacs-devel@gnu.org; Tue, 13 Apr 2010 18:15:03 -0400 Original-Received: from [140.186.70.92] (port=45375 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O1oNq-0002Ru-Dp for emacs-devel@gnu.org; Tue, 13 Apr 2010 18:15:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O1oFd-00051F-15 for emacs-devel@gnu.org; Tue, 13 Apr 2010 18:06:34 -0400 Original-Received: from mail-vw0-f41.google.com ([209.85.212.41]:49909) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O1oFc-000515-T2 for emacs-devel@gnu.org; Tue, 13 Apr 2010 18:06:32 -0400 Original-Received: by vws14 with SMTP id 14so1048532vws.0 for ; Tue, 13 Apr 2010 15:06:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=Yer7XWBAQtydifryUYl0VlekxYW9vaKVmoWDXkKJbOU=; b=iydan9gncQ+GlZW1cNqss1OUrWNj1SwheaAOMRgmj/Y3lCaBV8ii5hicDWf21VIr8v CYSbzFW8ChUDZbq5wQ7PJ/Up63s5Iqg5De3yZpiX/SnRJ5OJN4qJC/OzdyYWm6YED2Qd hur7pj7+oiL4fqa7Utie8hT3hc/cUEeqebxj0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=KkYh1guAylZdYvcpGJVhcJv24sHzNKwdxezrNVd5K+9tJb9jJ3m62MZI7IMIFvjWWH +7DyvBqvqXGkMy7zURj8NzdTSQ7F/wsSyWMyUHZyd6qBvAcfWMLoHd37IETO8WoqGh9+ +dds+POc+rS9jVzs3ehfzSv4oVOmxRt8CnS3A= Original-Received: by 10.220.128.16 with SMTP id i16mr3491085vcs.0.1271196388569; Tue, 13 Apr 2010 15:06:28 -0700 (PDT) Original-Received: from [192.168.1.42] (pool-96-236-188-251.pitbpa.east.verizon.net [96.236.188.251]) by mx.google.com with ESMTPS id 23sm3750494qyk.7.2010.04.13.15.06.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 13 Apr 2010 15:06:27 -0700 (PDT) In-Reply-To: X-Mailer: Apple Mail (2.1078) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:123601 Archived-At: Christian, On Apr 13, 2010, at 3:51 PM, Christian Lynbech wrote: > I would like to question the wisdom of letting `mailclient-send-it' > blindly relying on `browse-url' to send mail, especially since this is > set up as the default mail sending client on mac and windows. > I am certainly not fully on top of how emacs-w3m is supposed to handle > mailto. My `w3m-mailto-url-function' variable is nil and then the > documentation says control goes back to `mail-user-agent' which sort = of > looks like the receipe of an infinite loop to me. > Browse-url seems a shaky foundation > for mail sending given it is anyway not well-specified what it really > points to. first of all, the reason why we don't go via `sendmail' is that mail = gets swallowed by firewalls and spam filters. I have recent first-hand = experience with this when a user complained about bug reports vanishing = after the send mail function got accidentally switched back to sendmail = in a beta release of Aquamacs. I thought of recommending to switch back to `sendmail' when Apple fixed = their sendmail mechanism (it was broken at some point, prompting = mailclient.el), but the above experience made me discard that thought. Second, as you state, the "from" field isn't filled in right (at least = on the two systems you mention), and third, users will have configured = their preferred mail client, where the message is supposed to be = archived. "mailto:" URLs are an established standard ( = http://www.ietf.org/rfc/rfc1738.txt ) and most browsers handle it = correctly, i.e. by calling the system's mail function. I know of no = more appropriate system-specific mechanism to let the default mail = client handle mail on OS X. I think there was a way to send e-mail on = Windows, which was very populars among writers of viruses and trojans. There are issues with long messages not going through GMail (via "Google = Mail Notifier"), but this is due to Google's servers and long URLs, and = a bug on their side. So, the problem lies in the infinite loop that you point out and one = could and should do something about it. Perhaps "mailclient" shouldn't = use browse-url in case of an infinite loop, but that may be difficult to = detect (asynchronous API in some situations). =20 Perhaps w3m (being a third party package) should detect the = send-mail-function setting and temporarily bind it to `sendmail-send-it' = or so. Sending mail isn't trivial. But we really don't want to lose bug = reports or user's mail. The mailclient solution is standards-compliant = and does the right thing in the majority of configurations. I agree: = pretty it is not.