On Thu, 23 Oct 2003, Pat Lashley wrote:--On Thursday, October 23, 2003 14:53:38 -0400 [EMAIL PROTECTED] wrote:
I'm not sure how the vacation functionality is implemented; but if it goes through your normal MTA instead of attempting a direct SMTP connection; then you should be able to have your MTA rewrite the From address on the way out. This is fairly trivial with exim; I'm not sure how hard it would be with other MTAs.
We use sendmail, and we could re-write the outgoing addresses, but it's not easy, and it involves either (a) another flat file of mappings to maintain or (b) another LDAP lookup (and I'm not sure that's even possible); either way it's hard. Perhaps it's time to switch to exim? :)
Ease and flexability of configuration was the major reason I switched to Exim several years ago. I've never had cause to regret it. (It has several other advantages too. The recent versions have ACL sections that can be used to reject messages while the SMTP connection is still open. That reduces the chances that you'll be stuck with a queue full of undeliverable bounce messages aimed at forged addresses. The exiscan-acl patch from http://duncanthrax.net/exiscan-acl makes it easy to integrate SpamAssassin and/or virus checking at ACL time.)
With Exim, you would still need a lookup for the rewrite; but it makes such lookups quite easy. I assume that you already have some sort of database that has the full.name -> mailbox translations. (I'm guessing LDAP from your messages.) Depending on your schema, you may be able to easily do the reverse lookup in the same database. If not, you'd need a script to create a new database or table with the reverse info; and to update it whenever the existing db is updated. I don't think there's any way around that with any MTA; other than exposing the mailbox names as you mentioned earlier.
-Pat
