HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Add a new idea Subscribe
Status Already Exists
Workspace Domino
Created by Guest
Created on Dec 11, 2018

RELATED IDEAS

Allow for industry standard SMTP (incoming/submission) configurations

The industry standard configuration is port 25 for unauthenticated connections used for delivery to local email addresses, and port 587 (and 465 for legacy support) for authenticated connections used for relaying your users' messages to external addresses.  Generally port 587 requires authentication, while port 25 doesn't allow it.  Similarly, STARTTLS can be required for port 587, while optional for port 25.

Domino doesn't support this configuration.  Instead, it has one incoming port for unencrypted and STARTTLS, and a second port for legacy SSL.  In addition to basically not being able to use port 587, these two ports also share relay and authentication settings.  Domino does have a setting to allow relaying only when authenticated, without which it would be unusable.  However, it is currently not possible to require SSL/STARTTLS for relaying mail, without also requiring it for incoming unauthenticated connections.

  • Attach files
  • Admin
    Thomas Hampel
    Reply
    |     Nov 27, 2024

    This is an outdated / obsolete request.

    RfC 6409 suggests clients can use port 587 for message delivery to a server, however this is no longer the prefered port.
    The RFC 6409 got replaced by RFC 8314 a long time ago and the standard is to use port 465, which Domino is offering by default (see screenshot below)

    Reference : https://www.rfc-editor.org/rfc/rfc8314.html

    Furthermore, the configuration which users are allowed to relay can be found in the configuration document for that server, where you can configure only authenticated users to relay.


    Closing the request as already exists. If you believe there is anything that can not be done please open a support ticket and let us know the details.

    grafik.png
    grafik.png
    grafik.png
    Open full size
    grafik.png
    Open full size
    grafik.png grafik.png
  • Guest
    Reply
    |     Nov 21, 2024

    Hi, this is very important for us. I'm afraid that our management will choose for another mail system if we don't have a quick solution. thx

  • Guest
    Reply
    |     Jul 21, 2023

    Any update on this enhancement?

  • Guest
    Reply
    |     May 31, 2022

    4 years later. Any update HCL? I need this. Workarounds are very expensive and messy.
    -DH

  • Guest
    Reply
    |     Dec 22, 2021

    In Panagenda webinar, we were told to disable the port 465.
    But we still can not configure the 587 and use it correctly. What is the position of HCL ?

Copyright © 2023 HCL Technologies Limited