On Tue, 24 Nov 2009 13:48:02 -0700 Michael Saldivar <mike.saldi...@advocatecreditrepair.com> replied:
>On Tue, Nov 24, 2009 at 1:25 PM, Sahil Tandon <sa...@tandon.net> wrote: > >> On Nov 24, 2009, at 3:07 PM, LuKreme <krem...@kreme.com> wrote: >> >> >>> On 24-Nov-2009, at 10:39, Jordi Espasa Clofent wrote: >>> >>> That is easy. >>>>> Have your users connect to the submission port >>>>> >>>> >>>> Yes Wietse, I've considered this simple and clean option, but >>>> we're a hosting company and the costumers are to lazy to >>>> understand and accept an approach like this. >>>> >>> >>> Force them by making 587 the ONLY way to send mail. Tell them it's >>> for security reasons and make sure you enforce it. >>> >> >> That's all fine and well for small sites, but hardly a solution for >> larger environments where such draconian measures are impractical. >> A more reasonable solution is for the OP to push users toward >> submission via 587, and in the (very long) meantime, find other ways >> to bifurcate SASL vs. non-SASL traffic on port 25. >> > >Small sites like Google, where they force their customers to use >specific ports for e-mail submission? > >http://mail.google.com/support/bin/answer.py?answer=77689 > >What's good for the Google is good for the Gander, eh? You could even >copy Google's help docs when writing your own. > >-Mike Google's documentation, as usual, is in error. You can connect to SMTP via port 25; however, you will need to use TLS if sending from your own account. -- Jerry postfix.u...@yahoo.com TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail TO (UN)SUBSCRIBE see http://www.postfix.org/lists.html For some reason, this fortune reminds everyone of Marvin Zelkowitz.
