From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Riley Newsgroups: gmane.emacs.devel Subject: Re: Changing the default for `send-mail-function' Date: Wed, 29 Jun 2011 15:42:29 +0200 Organization: aich tea tea pea dicky riley dot net Message-ID: References: Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1309361434 11365 80.91.229.12 (29 Jun 2011 15:30:34 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 29 Jun 2011 15:30:34 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 29 17:30:30 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Qbwij-0005VI-PN for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2011 17:30:29 +0200 Original-Received: from localhost ([::1]:49557 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qbwii-0003no-KB for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2011 11:30:28 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:39238) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qbv19-0006ym-3W for emacs-devel@gnu.org; Wed, 29 Jun 2011 09:41:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qbv14-0002vp-WD for emacs-devel@gnu.org; Wed, 29 Jun 2011 09:41:22 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:51835) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qbv14-0002vI-7l for emacs-devel@gnu.org; Wed, 29 Jun 2011 09:41:18 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Qbv12-0002FK-AV for emacs-devel@gnu.org; Wed, 29 Jun 2011 15:41:16 +0200 Original-Received: from 85.183.18.158 ([85.183.18.158]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Jun 2011 15:41:16 +0200 Original-Received: from rileyrg by 85.183.18.158 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Jun 2011 15:41:16 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 31 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 85.183.18.158 Mail-Copies-To: never User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux) Cancel-Lock: sha1:g7l37tj47mKcTob9FQ+Co256ps0= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:141176 Archived-At: Lars Magne Ingebrigtsen writes: > Richard Stallman writes: > >> Times have moved on. All other modern mail readers have moved on from >> trying to use the local MTA to send email out, because the world has >> changed. These days, it's way more likely that you need to talk to your >> ISPs local servers directly, and you need to fill out some credentials >> tied to your account. >> >> If a client program can do that, why can't Exim do that? > > Because SMTP is slowly moving towards a regime of per-user > authentication. > > That is, to send someone email these days, you often have to provide a > user name and a password. If you're the only one sending mail from your > machine, it's theoretically possible to configure exim to provide these > credentials to the upstream MTA. (At least I think it's possible -- I > haven't actually checked.) If there are two people sending email from > your machine, that obviously isn't what you want to do, what with the > password then being shared and stuff. Assuming I havent got completely lost here, exim4 "smart hosts" are a doddle to configure. But only for one user. For more than one email account/smtp smarthost there are a plethora of google hits some of which might work - matching email and/or user to the corect authentication details needed for that user/email specific smarthost. If thats not relevant excuse the intrusion.