At 3/4/04 12:14 PM, Colin Viebrock wrote: >It's the second part of that equation where the problem lies. It's not >configuring your client to send on port 587, it's getting your >receiving mailservers to start listening on port 587.
Yes, of course. That's why I brought this up: to suggest that Tucows make their mail servers listen on port 587 as the standard suggests (instead of, or at least in addition to, port 8025). It would cut down on a few support questions for resellers who offer Tucows e-mail (not me) if knowledgeable end-users were able to just try using the standard port 587 and succeed, instead of having to ask which nonstandard port number they should use. -- Robert Mathews, Tiger Technologies Millions long for immortality who don't know what to do with themselves on a rainy Sunday afternoon. -- Susan Ertz
