[25296] in Athena Bugs
Re: Emacs and SMTP Authentication
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Nov 4 11:44:00 2003
From: Greg Hudson <ghudson@mit.edu>
To: Tom Cavin <cavin@mit.edu>
In-Reply-To: <16295.51781.214745.877555@lap1-wccf.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1067964232.29272.134.camel@error-messages.mit.edu>
Mime-Version: 1.0
Date: Tue, 04 Nov 2003 11:43:52 -0500
cc: Athena Bugs list <bugs@mit.edu>
Errors-To: bugs-bounces@mit.edu
On Tue, 2003-11-04 at 10:48, Tom Cavin wrote:
> Please correct me if I'm wrong, but I thought we were seeing more and more
> sites blocking traffic from random *.mit.edu hosts in an effort to reduce
> spam.
To some extent yes, but how will SMTP authentication help there? You
can't authenticate to another domain's mail servers (there's no basis
for authentication), and outgoing.mit.edu is just as much of a *.mit.edu
host as any other.
> If that's the case, there may be some need to immediately bounce
> mail back that can not be authenticated instead of holding it in a local
> queue.
We found it difficult to arrange that with sendmail. However, if direct
delivery fails, you'll get a bounce message.
> One of the reasons I'm asking about Emacs and the smtpmail.el file is that
> it does its own SMTP submission and queing in user space, and will
> therefore be able to try to authenticate on later attempts.
Does it actually have queuing, or does it just tell the user about
failures and punt?
> Is there an update scheduled for Athena's Emacs lisp code?
We normally update packages like emacs during a full release, but I
can't imagine there's an upstream emacs release with either SSL or
GSSAPI capability in the elisp code; crypto and elisp don't generally
mix. Do you have information to the contrary?
_______________________________________________
Bugs@mit.edu
http://mailman.mit.edu/mailman/listinfo/bugs
