AMS for external spam filtering?

[waterman34]

Hi guys

Is there a way or an option planned in future releases of AMS so that it can be used as an external spam filtering client for external domains? I'm not even sure how external spam filtering works to be quite honest so here is probably as good a place to start as any!

[rob]

If you mean to be referring to use AMS as a front end SMTP, then this should already be possible. As it is now AMS can act as a backup server, and there is no reason why you cant actually just have it being a the recipient of mail, and forward it to sepcific IP/host via static routes. This also means you could enable the SPAM filters. Additionally, the backup domains can be configured to only allow certain users to be accepted.

[waterman34]

If you mean to be referring to use AMS as a front end SMTP, then this should already be possible. As it is now AMS can act as a backup server, and there is no reason why you cant actually just have it being a the recipient of mail, and forward it to sepcific IP/host via static routes. This also means you could enable the SPAM filters. Additionally, the backup domains can be configured to only allow certain users to be accepted.

Hi Rob

I can't seem to get my head around this, must be one of those days!

We have a client who uses their own exchange mail server but wish to use our mail server for their external spam filtering prior to it hitting their inboxes, how in this example would you set this up on AMS?

[rob]

To do this firstly you would need to create a backup domain for each of the domains they host, then in the outgoing mail service settings, set it to relay directly to the exchange server. Of course all the MX records should then point to AMS. At this point basically AMS will not relay all mail to the exchange server, but of course you may want to reduce the load danger by managing a list of users allowed on the domains (each backiup domain will allow anything@yourdomain.com through by default), which can be managed in a external text file per domain. The final step is of coures to enable the various SPAM features you require.