unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: chad <yandros@gmail.com>
To: "christian.lynbech@tieto.com>" <christian.lynbech@tieto.com>,
	emacs-devel@gnu.org
Subject: Fwd: mailclient-send-it usage of browse-url
Date: Thu, 15 Apr 2010 09:49:37 -0700	[thread overview]
Message-ID: <86DDDA9D-2655-4B6C-A54E-AA87521C74E9@gmail.com> (raw)
In-Reply-To: D6FDF877-2199-48E7-8B06-4E6325EDEAC9@mit.edu

On Apr 15, 2010, at 1:14 AM, <christian.lynbech@tieto.com> <christian.lynbech@tieto.com> wrote:

>>>>>> "Stefan" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
> 
> Stefan> The problem is that for most users configuring sendmail is difficult
> 
> This is true but it could be that there are ways of using sendmail where
> one would be less reliant of its configuration.
> 
> This was the situation for me when trying to change to using the
> sendmail client. The default value of `mail-specify-envelope-from' is
> nil meaning that we rely on sendmail to generate the envelope and this
> requires sendmail to be setup correctly which apparently isn't the
> default on OSX. However, by setting the variable to true, emacs
> generates the envelope and now mails are getting delivered since they
> have a legitimate envelope which many mailservers wisely seem to
> require.
> 
> The point I am trying ot make here (without being a great sendmail
> expert) that it may be possible to excert enough external control over
> sendmail to ensure delivery, at least for nodes directly connected to
> the internet. If you are in a situation where you need to authenticate,
> other approaches must be used.
> 
> The biggest problem with sendmail (at least on OSX) is that (as David
> mentioned) it may fail silently. Sendmail will in a number of cases
> happily put the mail into the queue and then fail to deliver it later.

As has previously been mentioned, a great number of users have internet 
connections that cannot use sendmail without arcane configuration, because
their network connection blocks the straightforward connection in an attempt
at spam-bot mitigation.  No emacs default variable will fix this.  The user will
not notice that their mail was dropped into a black hole, because the system 
will not inform them -- it will simply and silently drop the mail.  This is not an
abstract concern -- David mentioned that it happened recently that a tester
complained about bug reports going unanswered when in fact his bug reports
were being swallowed by this sort of firewall when the send-mail function was
accidentally set to use sendmail in a beta release.

Until someone writes M-x telepathically-fix-smtp-auth-settings, sendmail cannot
easily be configured by end users.  Until sendmail can easily be configured by 
end users, using `open' is a far, far better choice.

*Chad





       reply	other threads:[~2010-04-15 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D6FDF877-2199-48E7-8B06-4E6325EDEAC9@mit.edu>
2010-04-15 16:49 ` chad [this message]
2010-04-15 17:15   ` mailclient-send-it usage of browse-url Lennart Borgman
2010-04-15 17:22     ` Chad Brown
2010-04-15 19:00       ` Lennart Borgman
2010-04-16  0:14     ` Stefan Monnier
2010-04-16  0:34       ` Lennart Borgman
2010-04-16  1:08         ` Stefan Monnier
2010-04-16 11:13           ` Lennart Borgman
2010-04-16 12:49             ` Stefan Monnier

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=86DDDA9D-2655-4B6C-A54E-AA87521C74E9@gmail.com \
    --to=yandros@gmail.com \
    --cc=christian.lynbech@tieto.com \
    --cc=emacs-devel@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).