[BUG] Smartermail 13.1.5451 svcDomainAdmin webservice SetRequestedDomainSettings not working

Problem reported by Evan Heller - 12/25/2014 at 7:18 PM

Resolved

Hi,

Has anyone tried the following?

enablemailsigning=True

as part of SetRequestedDomainSettings? I can succesfully generate a domainkeys cert using GenerateDomainKeysCert, however in the latest Smartermail I cannot seem to get it to enable the email signing.

Interestingly if you run GetRequestedDomainSettings with the value of enablemailsigning, it does come back as true but the domain.Config.xml file however does not show the change.

Can anyone else confirm this bug?

Additionally I tried the enabledomainkeys=true and found that even though the GUI does not show a change, the domainConfig_bak.xml shows a change.

Thanks.

7 Replies

Reply to Thread

Employee Replied

1/9/2015 at 3:36 PM

Employee Post

Evan, are you still having this issue? I cannot duplicate it. I have tested setting enablemailsigning to both true and false via the domain admin web service call, SetRequestedDomainSettings. I verified this by both calling GetRequestedDomainSettings and examining the domainConfig.xml. Also, if I edit the domain as a system admin, under Features the Mail Signing is unchecked. When this is set to false, in the web UI under DomainAdmin | Settings | Domain Settings | Advanced Settings, the Mail Signing option should not appear.

Evan Heller Replied

1/11/2015 at 9:02 PM

Hi, so it looks like the bug I'm running into is NOT enablemailsigning but rather enabledomainkeys. I was able to run GenerateDomainKeysCert and produce a domainkey however, when I run SetRequestedDomainSettings with enabledomainkeys=True , I do not see the domainkey checkbox checked nor the Enable DKIM Signing checkbox checked. What is the proper way to get both of those checkboxes to be checked on?

Employee Replied

1/12/2015 at 11:41 AM

Employee Post

Evan,

The DomainAdmin web services failed to expose methods to get/set enabling DomainKey signing and DKIM signing. This has been remedied and will be fixed in the next minor release. Two new settings can be passed to SetRequestedDomainSettings and GetRequestedDomainSettings: enabledomainkeysigning and enabledkimsigning.

Evan Heller Replied

1/12/2015 at 12:34 PM

I knew I wasn't going insane :) Thanks. Can you also look into adding the ability to delete ip bindings in the admin interface as well? I have a case where the original ip for Smartermail was set to a local ip 192.168.1.X and then changed later to an external ip however Smartermail appears to remember both ips in the bindings screen and it's available for use in the domain defaults.

Employee Replied

1/12/2015 at 12:56 PM

Employee Post

Evan, if you wouldn't mind, please create another idea thread with that suggestion. It would facilitate implementation tracking. Regardless, I have added to it our feature requests list.

Employee Replied

1/29/2015 at 4:52 PM

Employee Post

Today, we have released SM 13.2. You can now pass and receive enabledomainkeysigning and enabledkimsigning to/from SetRequestedDomainSettings and GetRequestedDomainSettings.

Andreas Huber Replied

3/18/2016 at 10:58 AM

Hello Robert,

I have the Version 11.7.5318.

Is there any way to correct this bug on my version?

Thank you!

Back to Community Threads

Please leave this box unchecked

7 Replies

Reply to Thread

Tags

Related Knowledge Base Articles