J.R. Oldroyd wrote: > > So that'd be: > > MUA --> MTA (587) --> ASSP --> MTA --> destination > > > > This is a four-stage configuration: > 587/MTA - 26/ASSP - 24/MTA - destination > > This is a three-stage configuration: > 587/ASSP - 226/MTA - destination > > Up to you which is simpler and less trouble. > > ASSP is designed to be in front of the MTA. A lot of > features have been put into ASSP, to make this possible, > including EnforceAuth and now also client-side SSL. The > former set-up may have been needed before these features > existed, but the shorter set-up is now possible. > > -jr
I don't use AUTH currently, but I feel I have a good grasp of how it works. I guess the thing to realize here is that there's no real point in having your endusers connect to the spam filter first (they're most likely not intentional spammers). There are all kinds of different case scenarios. In the case of an ISP hosted ASSP, they're probably forwarding chainmail, but I wouldn't imagine anything much worse than that (and if there is worse than that, other actions can be taken). In the case of a business, more than likely people are sending work emails. The only thing I can see either of these cases affecting is the Bayesian database. And that is full of whatever is being sent/received (created by the users of the system). In the example Jeroen provided, you want them to connect to the MTA which in turn sends their outbound messages through ASSP back to the MTA (or another MTA) and then out to the Internet (he provided the whole path from start to finish). In your 3-step example, you forgot to include ASSP on the way out. So, it's really a 4 step process entirely. Back in the early days of ASSP, it was not recommended to have more than a small number people directly connected to ASSP (at one time) because it would lockup ASSP. Now, with version 2.0, I guess it's not that important anymore, but I'd still keep it to just the MTA doing the connecting (personal preference). Kind Regards, Brett ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
