Authorized TO Web Service

Top  Previous  Next

In addition to supporting a local list of email addresses for the Authorized TO whitelist, SpamFilter can verify the validity of recipient email addresses by querying a webservice hosted in your environment. This is done by entering in SpamFilter the URL that SpamFilter needs to use to test for the validity of an email address using this format:

http://192.168.10.1/test/?e=<%email%>

 

SpamFilter will dynamically replace the <%email%> placeholder with the current email address being checked. You can use https if you'd like, and add other parameters - as long as you have one with <%email%> that will work. For example this will be fine too:

http://192.168.10.1/test/?e=<%email%>&user=bob

 

This is what the GUI looks like. For SpamFilter Enterprise you're able to specify a custom webservice URL for each domain you host:

 

SpamFilter-AuthTO-WebService

 

 

 

You can use any directory you want in the URL, and any parameter name you prefer, for example:

http://192.168.10.1/test/?e=<%email%>

http://192.168.10.1/SpamFilter/?auth=<%email%>

 

 

When you create the webservice, the webserver must just reply with just a "NO" string if the user does not exist. With any other response, or with any type of error, SpamFilter will assume the address is instead valid.

 

So for example, when checking the non-existent email address "roberto333@logsat.com", this would the the request being made to your webserver in the above example:

SpamFilter-AuthTO-WebService-2

 

 

And this is the webserver's response to indicate the user does not exist. Any other response where the body is different than a plain "NO" will be interpreted as a valid user.

SpamFilter-AuthTO-WebService-3