On 02/Dec/10 02:40, Sam Varshavchik wrote: > Perhaps some historical context will clear this up. > > SMTP over SSL on port 465 was intended to be nothing more than > SSL-ified port 25, and identically configured.
That port number is not in any IETF's RFC, AFAIK. > MSA on port 587's purpose was to simplify the dual role of the same > server both handling incoming mail, and acting as a smarthost for > authorized clients. The idea behind port 587 is not to futz around > with maintaining authorized RELAYCLIENT ranges for clients with > relaying privileged. Drop all relaying privileged for port 25, that's > your incoming mail, and have your clients use port 587, which simply > requires authentication, and does not have to be configured with > RELAYCLIENT ranges. Anything that goes to port 587 will require > authentication, end of story. Yup, it'd be handy to have some means to check migration has actually been completed, i.e. no clients are logging-in on port 25 any more... JM2C -- ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
