MPP and Beyond

What follows is a Message Partners‘ podcast covering our custom rejection feature introduced with MPP 3.4., which gives companies an easy-to-use yet powerful API interface. To learn more about this feature listen to the podcast or simply read the transcript below.

 

 Standard Podcast [2:50m]: Play Now | Play in Popup | Download

Tell me about MPP’s custom rejection feature.

With MPP 3.4 we’ve released a new feature called custom rejection notice. As the name implies, it allows the administrator to build template driven rejection messages that are sent in response to standard conditions like spam infection or virus infections or even clean messages. This was in response to requests from service providers to be able to give more specific information when they reject an email.

It turns out, though, we can also use the same feature as an API Interface to MPP.

Can you detail further how the custom rejection feature can be used as an API.

If you set all of the actions, including “on clean,” “on infection,” “on spam messages,” “on content violations,” every action to reject, then any script can send MPP a message via LMTP or SMTP and MPP will scan the message and then return the template response that you created from your rejection templates. Then the script will parse the response and do whatever it is instructed to do with the message.

The API interface is very simple to implement but very powerful. This gives any script access to all of the MPP scanning modules, as well as the MPP policy engine, which can make differentiated scanning decisions based on domain or email address, etc.

Can you give me an example how a customer would use something like this?

You can now use MPP within Procmail scripts, so say you have on local delivery a Procmail script that says ‘scan all messages,’ this gives you access to all our scanning modules such as Cloudmark or Commtouch. So say you have Procmail script send us the messages, we scan it, send the result back to Promail, then Procmail takes the appropriate action.

This would save a lot of time for the customer because if they want to use Cloudmark in a Procmail script they would have to license the Cloudmark engine, do the development work, and that can very time consuming from a business perspective and a technical perspective.

So we’ve greatly simplified the ability to use the MPP scanning engines and scripts by giving them a very streamlined API to use.

API, Cloudmark, Procmail, API Interface, Commtouch, LMTP, SMTP, custom rejection notice, scanning modules, template response, stop spam, protect email

Technorati Tags: API, Cloudmark, Procmail, API Interface, Commtouch, LMTP, SMTP, custom rejection notice, scanning modules, template response, stop spam, protect email