2
Question on release notes in new 9245
Question asked by Gabriele Maoret - SERSIS - 4/25/2025 at 6:56 AM
Unanswered
Why this? To me, it is better if the PRIMARY path continue to be changed with the domain name...

Release Notes
  • IMPORTANT: "Rename domain" no longer changes the domain's Primary or Secondary Path.
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)

2 Replies

Reply to Thread
1
Tim Uzzanti Replied
Employee Post

That wasn’t intended to be marked as “IMPORTANT” and will be corrected. 


Once a Domain is created and has been assigned its Primary Path, we will no longer rename the path when you rename the domain. The introduction of the Secondary Path, which allows older mail data for a domain to be automatically moved behind the scenes to slower and more cost-effective media, is one of the reasons.  The ability for SmarterMail to be used on additional OS's, File Systems, and Storage Solutions, which can often perform certain file functions differently, is another reason.  


Domain Renames are not common, but when they are done, system administrators don’t want us involved in the process and often are doing more than just renaming the domain.   It was a request from customers, which timed well with new functionality in SmarterMail.  


Lastly, we will be releasing a major release to SmarterMail, which also requires this change.  We will be sending out some announcements in a couple of weeks and should have this major release out in a month.  

Tim Uzzanti CEO SmarterTools Inc. www.smartertools.com
0
Hi Tim, thanks for the answer
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)

Reply to Thread

Enter the verification text