Simon, > > Right. This is a duty of a front-end MTA, > > Well the front-end MTA (MX host) is doing this, it's just the recipient > callout it makes stops at amavis and doesn't get through to the internal > mail host. It would have been really convenient to have been able to do > this :-)
I misunderstood, thinking that amavisd was exposed to the world. So we have a normal dual-MTA setup, which is fine, as long as the front-end MTA keeps the number of parallel SMTP sessions to amavisd at $max_servers or below. If there are several MX hosts, the limit applies to the estimated sum of their SMTP sessions. So your choice is either to use advice from Noel, or make a list of valid users available to front-end MTAs through some other mechanism (SQL, LDAP, periodically copying a fresh list from internal to MX). Mark ------------------------------------------------------------------------- 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 _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
