This web service contains functions that modify spam settings.

The following operations are supported. For a formal definition, please review the Service Description.

• AddRBL
  Adds an RBL check
• EditRBL
  Edits properties of an RBL check
• GetCommtouchSettings
  Returns settings for Commtouch
• GetDKIMSettings
  Returns settings for DKIM
• GetDecludeSettings
  Returns settings for Declude integration
• GetDomainKeysSettings
  Returns settings for DomainKeys
• GetMessageSnifferSettings
  Returns settings for MessageSniffer
• GetRBL
  Returns details about an RBL check
• GetRemoteSASettings
  Returns settings for Remote SpamAssassin
• GetReverseDNSSettings
  Returns settings for Reverse DNS
• GetSABPMSettings
  Returns settings for SpamAssassin-based Pattern Matching
• GetSPFSettings
  Returns settings for SPF
• GetSpamFilteringSettings
  Get spam filtering options within Antispam administration
• ListRBLs
  Lists information about all RBL checks
• ListSpamChecks
  Lists information about all known spam checks, similar to the Antispam Administration page
• RemoveRBL
  Removes an RBL check
• SetAntispamOptions
  Configure options for Antispam Administration
• SetCommtouchSettings
  Configures settings for Commtouch
• SetDKIMSettings
  Configures settings for DKIM
• SetDecludeSettings
  Configures settings for Declude integration
• SetDomainKeysSettings
  Configures settings for DomainKeys
• SetMessageSnifferSettings
  Configures settings for MessageSniffer
• SetRemoteSASettings
  Configures settings for Remote SpamAssassin
• SetReverseDNSSettings
  Configures settings for Reverse DNS
• SetSABPMSettings
  Configures settings for SpamAssassin-based Pattern Matching
• SetSPFSettings
  Configures settings for SPF
• SetSpamFilteringSettings
  Set spam filtering options within Antispam administration
• SetSpamWizardLevel
  Sets the spam checks and weights to predefined wizard levels

This web service is using http://tempuri.org/ as its default namespace.

Recommendation: Change the default namespace before the XML Web service is made public.

Each XML Web service needs a unique namespace in order for client applications to distinguish it from other services on the Web. http://tempuri.org/ is available for XML Web services that are under development, but published XML Web services should use a more permanent namespace.

Your XML Web service should be identified by a namespace that you control. For example, you can use your company's Internet domain name as part of the namespace. Although many XML Web service namespaces look like URLs, they need not point to actual resources on the Web. (XML Web service namespaces are URIs.)

For XML Web services creating using ASP.NET, the default namespace can be changed using the WebService attribute's Namespace property. The WebService attribute is an attribute applied to the class that contains the XML Web service methods. Below is a code example that sets the namespace to "http://microsoft.com/webservices/":

C#

[WebService(Namespace="http://microsoft.com/webservices/")]
public class MyWebService {
    // implementation
}

Visual Basic

<WebService(Namespace:="http://microsoft.com/webservices/")> Public Class MyWebService
    ' implementation
End Class

C++

[WebService(Namespace="http://microsoft.com/webservices/")]
public ref class MyWebService {
    // implementation
};

For more details on XML namespaces, see the W3C recommendation on Namespaces in XML.

For more details on WSDL, see the WSDL Specification.

For more details on URIs, see RFC 2396.