In the latest versions of SmarterMail, automated forwarding is a feature that can be disabled per domain or per user.
Even if this feature is enabled in the domain and default settings for new users in SM, when a new user is created in SCP the automated forwarding is not active.
I’m not too familiour with Smartermail my self but the feature isn’ t related to the “Forwardings” feature that is enabled/disabled on hosting plan?
It has nothing to do with the hosting plans.
In SCP we can enter an email address to automatically forward all incoming messages on a particular email account. However, SCP does not know whether or not this feature is active for the user in SmarterMail.
In newer versions of SmarterMail (17.x/100.x) the automatic forwarding feature is inactive by default. These must be enabled in SmarterMail at the default settings for new domains and for new users.
So far so good. If this feature is enabled, when we create a new mailbox in SmarterMail the new user will be able to create forwardings.
However, when creating a new mail account in SCP this feature will not be active in SM.
Ok i understand.
I will add this to our bug tracker shortly and link back here.
we should be able to make a fix for that (atleast to automatically enable it as a quick fix, or preferably depending on a hosting plan setting).
Same issue here.
I think it worked correctly in SmarterMail 14, but apparently fails since we upgraded to SmarterMail Build 7125. That was a couple of months ago, but I wasn’t aware of the problem until this week.
Just to clarify Jade’s post, the Domain actually has Automated Forwarding enabled:
… and the email account has Automated Forwarding disabled:
Even though forwarding is disabled, I can see that the forwarding address (and “delete when forwarded” setting) were saved in SmarterMail. These settings are revealed when I go into SmarterMail and “Enable Automated Forwarding” for the user:
If I use SolidCP to make any change to the email account, it reverts back to disabling Automated Forwarding for that email account.
I have logged a ticket with Smartertools about this issue so hopefully we get some kind of resolution, be it from Smartertools or SolidCP.
I suspect that this is what is happening.
Smartermail has a new api function called enableMailForwarding and SolidCP is not setting this value.
Based on the above assumption, smartermail is not enabling forwarding if the user defaults are set to true for this option.
For now, we’ll have to manually enable forwarding for each user that logs a support request or use the propagate function on a daily bases to enforce this setting
@Dolphyn5 – this worked correctly up until a few versions back on the latest Smartermail.
please add my vote to get this fixed. i think smarterTools has forgotten about being able to be backwards compatible.
They mentioned this api cal to enable below. But I checked the api call Jade pointed out and saw that is also have the “enableMailForwarding” option.
Update: We have now confirmed the issue and logged a bug at https://github.com/FuseCP/SolidCP/issues/19. You can track any updates here but no ETA has been set.
- Views871 times
- Answers9 answers