The way I had assumed it earlier was the client authenticates via 993 (dovecot IMAP in our case), crafts an email to another user and this email is delivered instantly via lmtp (in our case, dovecot LDA), but now I see that in reality, the client sends the email via the smtp port instead making a direct connection with the mail server. Its still secure but the other way sounds more secure.
On Sun, Mar 30, 2014 at 5:22 PM, cybermass < cybermassproductioncen...@gmail.com> wrote: > Ok I just noticed I can even comment out the regular smtp protocol from > master.cf to remove listening from port 25. I get alot of hits to our > server, we are an open domain but looking to close soon. We dont intendto > make anyone's life difficult but we have complaints from clients that > cannot send outbound. It is because their ISP blocks outgoing 25 and 465. > So we use a custom port. They may know about 587 as well. > > > On Sun, Mar 30, 2014 at 5:17 PM, li...@rhsoft.net [via Postfix] < > ml-node+s1071664n66505...@n5.nabble.com> wrote: > > > > > Am 31.03.2014 02:07, schrieb cybermass: > > > 587 is dedicated for submission but is it any different if I have > > > configured smtps to be port 8809 and just have the clients use that > port > > > with STARTTLS instead of 587? > > > > technically you can use whatever port but why not > > use standars and make users life difficult? > > > > BTW: don't talk about SMTPS and STARTTLS in conext > > of the same port especially if you instrcut your > > users because that leads to non-working configs > > > > http://en.wikipedia.org/wiki/STARTTLS > > > > > > >> Am 31.03.2014 01:54, schrieb cybermass: > > >>> Interesting, that is something I never even thought of > > >> > > >> why should a server hosting example.com relay a to him > > >> submitted message from [hidden email]< > > http://user/SendEmail.jtp?type=node&node=66502&i=0>to [hidden > > >> email] <http://user/SendEmail.jtp?type=node&node=66502&i=1> > > >> trough a foreign server? > > > > your node.js application breaks quotes! > > > > >> what should that foreign server do with that message > > >> other than bounce it back again to the origin which > > >> is the MX or throw it way if there is no MX reachable > > >> from outside? > > >> > > >>> Yes the clients are configured to only go through our custom > > >>> smtps port since some ISP's block outgoing 25 and even 465. > > >> > > >> 587 is dedicated for mail-submission > > >> > > >>> These clients just need to have only one account in their > > >>> mail client I understand. Is there any other configuration > > >>> I would need to do on the server side? > > >> > > >> for the case above - no, mail from one gmail user to another > > >> gamil user is not routed trough hotmail and that behavior is > > >> logical and as expected > > > > > > ------------------------------ > > If you reply to this email, your message will be added to the discussion > > below: > > > > > http://postfix.1071664.n5.nabble.com/Unclear-of-smtp-protocol-in-a-restricted-domain-tp66494p66505.html > > To unsubscribe from Unclear of smtp protocol in a restricted domain, > click > > here< > http://postfix.1071664.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=66494&code=Y3liZXJtYXNzcHJvZHVjdGlvbmNlbnRlckBnbWFpbC5jb218NjY0OTR8NTE3NzI5OTA0 > > > > . > > NAML< > http://postfix.1071664.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > > > -- > View this message in context: > http://postfix.1071664.n5.nabble.com/Unclear-of-smtp-protocol-in-a-restricted-domain-tp66494p66506.html > Sent from the Postfix Users mailing list archive at Nabble.com. >
