Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: Outgoing mail defaults
Date: Sat, 16 Apr 2011 11:51:14 -0500	[thread overview]
Message-ID: <87pqomm96l.fsf@lifelogs.com> (raw)
In-Reply-To: <m3aafqqh66.fsf@quimbies.gnus.org>

On Sat, 16 Apr 2011 18:45:05 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> I was thinking about starting to implement this stuff (with 1) last :-),
LMI> and one problem occurred to me:  Should Emacs do something with mail
LMI> delivery failures?
...
LMI> So would it make sense to put in a simple MTA layer in Emacs itself?
LMI> That is, an mta.el library that's on top of smtpmail.el, which checks
LMI> for transient failures (4xx, I think), queues stuff up, and tries
LMI> resending in the background?

It may be useful on W32 but on Unix I would not need it.

LMI> Or is that too brittle?  If you're not running Emacs, your message will
LMI> just be sitting in the queue.  Currently, if Message gets a "450"
LMI> (greylisting) error, it'll report the error, and you have to try again
LMI> later manually.

The MUA should retry later if it's doing SMTP on its own.  Gnus could
use the Gnus Agent queue, for instance.  I think it's a MUA function,
though, not something for Emacs in general.

Ted




      parent reply	other threads:[~2011-04-16 16:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 17:04 Lars Magne Ingebrigtsen
2011-03-17 17:17 ` Ted Zlatanov
2011-03-17 17:31   ` Lars Magne Ingebrigtsen
2011-03-17 18:18     ` Ted Zlatanov
2011-03-17 18:33       ` Lars Magne Ingebrigtsen
2011-03-17 19:35         ` Ted Zlatanov
2011-03-17 17:25 ` David Reitter
2011-03-17 17:43   ` Lars Magne Ingebrigtsen
2011-03-17 18:22     ` Ted Zlatanov
2011-03-18 14:10       ` John Sullivan
2011-03-17 19:02     ` David Reitter
2011-03-17 22:27       ` chad
2011-03-18  2:38         ` Ted Zlatanov
2011-03-18  4:17           ` chad
2011-03-21 19:46           ` Adam Sjøgren
2011-03-21 19:50             ` Ted Zlatanov
2011-03-17 20:23 ` James Cloos
2011-03-17 20:30   ` Lars Magne Ingebrigtsen
2011-03-17 20:35     ` James Cloos
     [not found] ` <87d3ln9b7y.fsf@stupidchicken.com>
2011-03-20  1:41   ` Ted Zlatanov
2011-03-20  3:06     ` Stefan Monnier
2011-03-20 12:20       ` Ted Zlatanov
2011-03-21 14:20         ` Stefan Monnier
2011-03-21 19:42           ` Ted Zlatanov
2011-03-21 22:14             ` Stefan Monnier
2011-03-22  2:01               ` Ted Zlatanov
2011-03-29 19:22     ` Lars Magne Ingebrigtsen
2011-03-29 19:34       ` Application resource storage (was: Outgoing mail defaults) Lars Magne Ingebrigtsen
2011-03-29 19:58         ` Application resource storage Ted Zlatanov
2011-03-29 20:14           ` Lars Magne Ingebrigtsen
2011-03-29 21:02             ` Ted Zlatanov
2011-03-29 20:51           ` chad
2011-03-22 11:26 ` Outgoing mail defaults Simon Josefsson
2011-04-16 16:45 ` Lars Magne Ingebrigtsen
2011-04-16 16:47   ` Lars Magne Ingebrigtsen
2011-04-16 16:51   ` Ted Zlatanov [this message]

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=87pqomm96l.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --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.
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).