Skip to Main Content
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

Status No Plans to Implement
Workspace Domino
Categories Administration
Created by Guest
Created on Oct 20, 2022

Add internal counter to message when it is sent to Smarthost so that, Domino can send DFR if the message is returned again from Smarthost

Currently when Domino server is configured with Smarthost, so Domino will send the message to Smarthost if the user is not found in Domino directory. Now some customers have requirement to forward the message again from Smarthost to Domino directory especially when 2 companies have merged.

If the user is not present in Smarthost also and Smarthost again sends this message to Domino then Domino will again send it to Smarthost. This essentially creates a loop between Domino and Smarthost and finally the error comes as "Messages probably in routing loop, fixed maximum hop count exceeded.".

So for incorrect address mail, the mail loops and gives this error to sender. So sender has no way to understand that user address was incorrect. So there is a feature request to add the internal counter when the same message is forwarded to Smarthost multiple times. This can be done using message ID. So if the message is returned from Smarthost to Domino then Domino should send the DFR saying "User not found in Directory". This will not only avoud looping but also give proper DFR to sender.

  • Attach files
  • Admin
    Thomas Hampel
    Oct 21, 2022

    Works as designed / according to the RFC, with no plans to change the behaviour.
    please continue to vote for this idea if you think it should be implemented.