RE: Authenticated Outgoing Mail

  • From: "Michael B. Smith" <michael@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 15 Sep 2005 21:19:31 -0400

Randall Gellens and myself, in the mid-1980's, wrote a mainframe-based
e-mail system together. :-) I was shocked to see him listed as one of
the principal authors. I'll have to give him a call.
 
Anyway, you are right, I am wrong. In the final RFC, it no longer says
"must".
 
That aside, my basic point remains -- if you require separate
authentication requirements, you need multiple virtual servers. In my
experience, if you've implemented 587, you require auth on it, whether
the RFC says so or not.
 
You still get the point, tho. :-)  I hate being wrong in a public forum.
:-(

________________________________

From: Carl Houseman [mailto:c.houseman@xxxxxxxxx] 
Sent: Thursday, September 15, 2005 8:47 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Authenticated Outgoing Mail


http://www.MSExchange.org/

Are you finding this "'must' require SMTP auth" in RFC 2476?
 
It's not there in the one I'm reading.
http://www.faqs.org/rfcs/rfc2476.html
 
Section 6, "Optional actions" covers "Require authentication".
 
 
On the single setup, I agree, for those types of clients.  But we have
no indication that OP has that type of client, though, so, my question
remains open for the OP.
 
 


________________________________

From: Michael B. Smith [mailto:michael@xxxxxxxxxx] 
Sent: Thursday, September 15, 2005 8:31 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Authenticated Outgoing Mail


http://www.MSExchange.org/

The draft-RFC says that you "must" require SMTP auth for port 587.
 
Most of my clients want a single set up. They don't want to have to
change anything, regardless of whether they are home, timbuktoo, or
china too.

________________________________

From: Carl Houseman [mailto:c.houseman@xxxxxxxxx] 
Sent: Thursday, September 15, 2005 8:17 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Authenticated Outgoing Mail


http://www.MSExchange.org/

Why should it be necessary to have different authentication requirements
for the different ports?
 
Just set up on VS to listen on 25 and 587 and require authentication for
relaying purposes.
 
I would guess he's already requiring authentication to relay for his
clients that can still come in on 25.
 
 
A better question is, "Why bother using the Exchange server?  Just use
the ISP's mail server for outbound SMTP".
(One possible response is "ISP limits message size or volume" but if not
that, then what?)
 
 

________________________________

From: Michael B. Smith [mailto:michael@xxxxxxxxxx] 
Sent: Thursday, September 15, 2005 7:58 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Authenticated Outgoing Mail


http://www.MSExchange.org/

How do you set one to require authentication and the other "not to"?
 
:-)

________________________________

From: Carl Houseman [mailto:c.houseman@xxxxxxxxx] 
Sent: Thursday, September 15, 2005 7:54 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Authenticated Outgoing Mail


http://www.MSExchange.org/

Huh?
 
At least, in Exchange 2003:
 
Default SMTP Virtual Server
Properties
Advanced
"Configure multiple identities for this Virtual Server"
 
Mine shows
 
IP Address   TCP Port
192.168.0.10 2525
192.168.0.10 25
 
Two ports, one IP address, one VS.


________________________________

From: Michael B. Smith [mailto:michael@xxxxxxxxxx] 
Sent: Thursday, September 15, 2005 7:43 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Authenticated Outgoing Mail


Yes, but each SMTP VS can only listen on a single port. So you'd
probably want to add an additional SMTP VS.

________________________________

From: John Tolmachoff (Lists) [mailto:johnlist@xxxxxxxxxxxxxxxxxxx] 
Sent: Thursday, September 15, 2005 6:09 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Authenticated Outgoing Mail


http://www.MSExchange.org/


I am not sure if Exchange can be configured to listen on 587 in addition
to 25, but it is accepting inbound authenticated connections is what you
meant. 

 

A work around (as long as your Exchange server is properly configured)
is to add an inbound rule to your firewall (you are running a firewall
aren't you) to redirect incoming port 587 traffic on the external
interface to port 25 on the internal destination.

 

John T

eServices For You

 

-----Original Message-----
From: EIS Lists [mailto:eis_lists@xxxxxxxxxxxxx] 
Sent: Thursday, September 15, 2005 2:54 PM
To: [ExchangeList]
Subject: [exchangelist] Authenticated Outgoing Mail

 

http://www.MSExchange.org/

Hello:

 

We have several users who access their Exchange accounts via POP and
SMTP. Recently, several large ISPs have started blocking outbound
traffic that does not use their servers. Is there a way to tell Exchange
2000 to use authenticated outbound connections (e.g., over port 587)?

 

Thanks.

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp 
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
michael@xxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx 

Other related posts: