When setting up a forwarding on a mailbox with 2 or more forwarding addresses SolidCP sends the command through with a comma as entered into the solidcp.
This causes issues with version 17 of smartermail and higher as the forwarding api commands have changed.
See below example when creating a forward within SolidCP and specifying two or more forwarding email addresses
When setting two or more forwarding addresses within smartermail, SolidCP is unable to read the second or subsequent forwarding addresses.
Hello,
It does sound like they have changed their legacy API. I presume this did work? We are using the UpdateUserForwardingInfo2 in the current code for updating forwarding.
The Smartermail provider does need to be rewriten to the newer REST API however smartermail have not as of yet finalized the new API or added all the features to it.
Regards,
Trevor
Hi Trevor,
Would it be possible to at least update the forwarding method in the next release as this is causing issues.
Hello,
It is not possible to move from the legacy to new API for just one method due to the fact its going from SOAP to REST which requires different login methods etc.
In the next few days we will be announcing a way of the community helping to fund a rewrite of the entire module to the newer API.
Regards,
Trevor
@trobinson Did this ever happen? Now I am properly using EAS and MAPI, I would be interested in the upgrade 🙂
@maoxiong Hello, We did enable bounty source on our Git issues. If your looking to place a bounty on smartermail being updated you can find it at https://www.bountysource.com/issues/97032844-smartermail-update-provider-with-smartermail-json-api.
You are also able to discuss with us if you would like to sponsor an piece of work using the contact button above.
Regards,
Trevor
@maoxiong There is no set goal. The idea of the bug bounty is that it can be picked up by any developer when it reaches a goal they are happy to accept for the work.
