Ken Mink wrote:
A note about the different approaches that Jason and I suggested. My mindset is geared towards high scalability, and his is towards lower maintenance. In fact, significantly lower maintenance. :) It's unlikely that you'll need the scalability afforded by the local mappings vs verify, unless you're pushing more than a few messages per minute on average. If you get up into the range of a few messages per second, start looking at other solutions. Otherwise, verify is likely a simpler option. Just be careful that you configure it correctly. On the other hand, if you only have a dozen or so users in your domain and they change maybe once a year, personally I'd go w/ a simple map file.Thanks to Jason and Aaron. Both of their ideas are spot on. The gateway machine is one of those machines that has just been humming along for quite a while. It's got RH7.3 and running an old postfix. It's time for an upgrade. This has become enough of an issue to put the time in on it.
Thanks,
Ken
There is of course the argument that if you only make user changes once in a blue moon, you'll forget how to make the changes and have to relearn it every time, but hopefully you remember to document, document, document, right? :)
As another side note, relay_recipient_maps was added in Postfix 2.0, verify was added in Postfix 2.1. A link to the verify documentation (as Jason didn't provide one :) is here: http://www.postfix.org/verify.8.html
Aaron S. Joyner -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
