On 18/04/12 09:18, Sam Varshavchik wrote: >> So is the bottom line there is no way for courier to provide a binding to >> the virtual interface so that it would pass SPF checks without having to >> add the default eth0 IP of 206.221.219.122 to the SPF record for eth-os.org? > > If you're looking to have /all/ outgoing mail sent from a socket that's > bound to that IP address, this would be the SOURCE_ADDRESS > (or SOURCE_ADDRESS_IPV6) setting in the courierd configuration file.
No, not /all/ outgoing mail via any one single SOURCE_ADDRESS, I have been doing that for quite a while. That postfix config example allowed for MULTIPLE bindings to MULTIPLE IPs with each providing it's own outgoing hostname and SSL certificate. That was the "magic" according to the subject of this thread. What about the possibility of running separate instances of courier each with it's own SOURCE_ADDRESS and set of config files? ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
