Empty Mail Header Field "To" in Notification Mails

HCL Connections Connections Forum
,
1

Recently, we are having some problems with delivery failures for mail notifications sent from Connections.

One example: After creating a new blog post we notify certain users with "More Actions -> Notify Other People". By this, Connections sends out an e-mail to the selected users, but there is a problem in the e-mail header field "To:". This field doesn't contain the receivers address, but a blank/whitespace. Some of our users use mail forwarding to external mail providers (e.g. gmx and web.de from United Internet), which seem to reject mails with an empty "To:"-field in the mail header.

This problem does not only occur with notification mails from blogs, but all other applications such as wikis and files or using @mentions. The only mails, that do not have an empty "To:" field are daily newsletter mails.

So where is the difference between notification mails from an application and the newsletter? Why do notification mails have an empty "To:" field? Did anyone have the same problem?

Our version of Connections is Release v6.0.0.0 Build IC6.0_CR4_Integration_20190131-1756.

2

Hi Julian,

I tested and was able to reproduce the issue in both 6.0 and 6.5. I tried to fix it by updating the {WAS_INSTALL_DIR}/profiles/dmgr/config/cells/CellName/LotusConnections-config/notifications/blogs/resources/nls/notification_en.properties file. Within that file there are the following two parameters:

ventura.notification.from=From: {0}
ventura.notification.to=To:

I added {0} to the "To:" parameter, did a full sync and restarted Connections, but that had no effect.

Within the directory above, there's also a notification.properties file with the same parameter, so I made the same change in that file, did another full sync and restarted Connections again, but that also had no effect.

I performed the same steps within the LotusConnections-config/notifications_v2 directory and got the same results.

I tested in both 6.0 and 6.5.


I suggest that you open a case with HCL Connections Support for further investigation.


Tony Dezanet

3

Hi Anthony,

thanks for verifying the problem in your environments. Meanwhile we opened a case with HCL Connections Support. Hope HCL will fix this soo.

Best
Julian

4

Hi Anthony,

a quick update on our issue: We opened a case with HCL. Unfortunately, we do not have a working solution, but HCL is still working on it.

Best
Julian

5

Hi. everyone,

I know this is already a little bit older but I had the same issue using AWS SNS-SMTP gateway.

I opened a ticket and got a fix for CNX 6.5 CR1: LO100060-IC6.5.0.0_CR1-Common-Fix

With this change, the "globalSender" address is always added into the "To" field in the SMTP message. This causes of course some unroutable messages (in case of the sender e-mail noreply@your.domain) or the sender gets a lot of unwanted traffic (in case of a valid e-mail address).