2
SmarterMail: Signature doesn't show the standard sender mail address
Problem reported by Stefan Mössner - 1/26/2024 at 11:37 AM
Submitted
Hi all,

since SmarterMail build 8776 the standard sender mail address isn't added to the signature any more. This issue is related to the webmail UI.

My users are logging in with a local, not public routable domain. They all have selectable profiles for different public mail provider. And one of these profiles is set as standard. And this provider profile is selected when you write new mails but in the signature there's the mail address of local domain and not the mail address of the selected profile. You have to change the profile to another one and change it back to get the correct mail address in the singature.

This doesn't change with other web browsers. This issue happens with Microsoft Edge (Chromium), Google Chrome and Mozilla Firefox.

Can anyone confirm this issue?

Have a nice weekend an kind Regards.

6 Replies

Reply to Thread
0
Stefan Mössner Replied
Even with the newest release 8797 (Feb. 1, 2024) there's the issue.
0
Stefan Mössner Replied
What about this issue?
0
Stefan Mössner Replied
Why does nobody give an answer?
0
Zach Sylvester Replied
Employee Post
Hey Stefan, 

I'm sorry to hear that you're having this issue. Please log in to your SmarterTools.com account then go to My Tickets after this click new ticket. Opening a support ticket is our official channel to provide support to customers. Support is also part of what is included when you purchase/renew a license. 

Kind Regards, 
Zach Sylvester System/Network Administrator SmarterTools Inc. (877) 357-6278 www.smartertools.com
0
Stefan Mössner Replied
As always, I'm a user of the free edition.
And this worked for a very long time without issues. But with the last updates it doesn't.
0
Stefan Mössner Replied
It looks like build 8818 (Feb. 22, 2024) solved this issue.

In the release notes I found:
  • Fixed: Signature is not properly selected when replying when "Use to address for replies" is enabled.
This doesn't exactly describe the issue that I had but it seems to have fixed it. I will see the next days and give feedback.

Reply to Thread