Re: AUTH when sending
- From: "Steve W. Jackson" <stevewjackson@xxxxxxxxxxx>
- Date: Fri, 30 Jun 2006 15:46:12 -0500
In article
<net-news99-E7C305.15552830062006@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Matt Simpson <net-news99@xxxxxxxxx> wrote:
In article
<ericp06-C845E0.12030530062006@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
"Eric P." <ericp06@xxxxxxxxxxxxx> wrote:
My feeling is that your only hope is to trash Eudora prefs and reset
everything. I hesitate to recommend that, for the most part, but
in this case, that's my vote.
I found the problem. Too many changes at once makes it tough to figure
out what screwed things up. I changed from a server that ran on port 25
and didn't require auth to one that ran on port 587 (the submission
port) and did require auth. I got tired of futzing with the auth stuff
and turned it off, still using the server on port 587.
Apparently (as in I have nothing except my experience to "prove" it),
Eudora assumes that any server running on port 587 will require auth.
When I have the "use submission port" box checked, it always tells me
the server requires auth before it tries to send. When I uncheck that
box, it's happy.
It probably makes sense that a submission server listening to port 587
SHOULD require auth, and that's how I eventually intend to set it up.
I'm not sure it makes sense for Eudora to automatically assume the
server WILL require auth without asking it (unless there's an RFC
somewhere that says so), but that seems to be the way it works.
RFC 2476 addresses this port, but I have no idea what it may say about
whether authentication is mandated or merely allowed.
= Steve =
--
Steve W. Jackson
Montgomery, Alabama
.
- References:
- AUTH when sending
- From: Matt Simpson
- Re: AUTH when sending
- From: Eric P.
- Re: AUTH when sending
- From: Matt Simpson
- AUTH when sending
- Prev by Date: Re: AUTH when sending
- Previous by thread: Re: AUTH when sending
- Index(es):
Relevant Pages
|
