Uploaded image for project: 'Red Hat Advanced Cluster Security'
  1. Red Hat Advanced Cluster Security
  2. ROX-30654

Add support for configuring the EHLO/HELO hostname for SMTP notifiers in RHACS

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Hide
      RHACS SMTP notifiers now support configuring the EHLO/HELO hostname.
      This allows for better compatibility with strict mail relay servers in secured environments.
      Show
      RHACS SMTP notifiers now support configuring the EHLO/HELO hostname. This allows for better compatibility with strict mail relay servers in secured environments.
    • Feature
    • Yes
    • Rox Sprint 4.9F - Global, Rox Sprint 4.9G - Global

      Goal Summary:

      Allow customization of the SMTP EHLO/HELO hostname in RHACS Email Notifier

      Goals and expected user outcomes:

      RHACS (v4.7.4) does not currently allow users to configure the EHLO hostname when sending emails via SMTP. By default, RHACS sends either:

      • EHLO localhost
      • Or the container's internal hostname

      In some secured enterprise environments the mail relay server (relay2.itm.lan) enforces strict SMTP policies that reject connections with generic or unauthorized EHLO values.

      RHACS should introduces an option in the Email Notifier configuration to explicitly define the value sent in the SMTP EHLO command (e.g., smtpHeloName, similar to Alertmanager or Postfix).

      Other Red Hat products like Alertmanager and Postfix already support this.

      Acceptance Criteria:

      Customization of the SMTP EHLO/HELO hostname in RHACS Email Notifier is allowed

      Success Criteria or KPIs measured:

      A list of specific, measurable criteria that will be used to determine if the feature is successful. Include key performance indicators (KPIs) or other metrics., etc. Initial completion during Refinement status.

      <enter success criteria and/or KPIs here>

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios together with user type/persona. Initial completion during Refinement status.

      <your text here>

      Out of Scope (Optional):

      High-level list of items that are out of scope. Initial completion during Refinement status.

      <your text here>

              ksanchet@redhat.com Khushboo Sancheti
              saledort@redhat.com Sabina Aledort
              Sabina Aledort Sabina Aledort
              ACS Core Workflows
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: