Messaging Server: New MTA Technical Note

What started as a blog discussion here has resulted in the following technical note, published to BigAdmin:

Preferred Practices for Deploying Sun Java System MTA

Synopsis:

Typically, a Sun Java System Messaging Server deployment consists of front-end and back-end services. The front-end services enable users access to the system, while the back-end services store and provide access to data. In the past, we've heard disputes about how to deploy the MTA on the front end: either as an entrance gateway to the system, or “behind” an anti-spam/anti-virus service that also provides an MTA functionality. This article describes the recommended way to deploy your MTA with respect to anti-spam/anti-virus services.
Comments:

Here is a question.... What would be the best common practice/typical recommendation for _where_ the AV/AS "engine" should live when integrating using the MTA plugin model? i.e. You have 4 boxes. They are all behind a network "load balancer". Do you have two boxes that act as MTAs that then "load balance" to the other two boxes doing AV/AS via the plugin or do you have all 4 boxes acting as MTAs calling the AV/AS engine via a localhost socket? (2 MTA + 2 AV/AS or 4 MTA/AV/AS)

Posted by Derek Diget on January 21, 2008 at 12:44 PM MST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Reporting about Unified Communications Suite Documentation, including news, Comms 101, documentation updates, and tips and tricks.

Search

Archives
« July 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today