> The gateway approach appeals to me on more grounds than just > scalability, because I'm migrating the mailserver from a postfix/cyrus > setup to courier, and I can use the gateway to cleanly decommission > the old mailserver too. > > There is just a backscatter risk to avoid, eg, if the mailserver is > down, make sure that the gateway actually queue's the messages if it > accepts them. > > Any decent gateway should still adhere to RFC2821 section 4.1.1.4 If the gateway issues the 220 after the DATA phase that's it. It has clearly stated that it has accepted responsibility for delivery.
There are other non-technical issues such as legislation (this varies form country to country) which makes a gateway approach attractive. A recent related blog about this is at http://www.avertlabs.com/research/blog/?p=194. A lot can be achieved via courierfilter without resorting to building a separate gateway. Unfortunately adding support for your own filters is still not a straight-forward affair. The latter has been discussed to death on this list alrady, so I am not going to expand on that. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
