thanks sir.. for the reply... only problem which my boss sees on .forward is we have to create it manually whenever a new user is created.. or could this be automatically done whenever a new a new user is created on the openldap database.
thanks, allan ----- Original Message ----- From: "Gerald Timothy Quimpo" <[EMAIL PROTECTED]> To: "Philippine Linux Users Group Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, June 12, 2003 4:01 AM Subject: Re: Fw: [plug] postfix+openldap problem > On Wednesday 11 June 2003 09:25 am, Ako Ito wrote: > > mail server that runs on redhat 7.3 using postfix-2.10 and > > openldap 2.1.17 to be used for authentication > > any reason for the version numbers? do you have flexibility > to use some other distribution (probably not, that's OK, if > you only use redhat then stick with that, but maybe a newer > version?), some other version of postfix and openldap (just > curious, what if a security vulnerability is found in them and > the software is upgraded? :). > > > > as a database for users info. but his conditions are that mails should be > > > forwarded to a users alternate email address which is in openldap > > > database without using .forward. any ideas on how i can > > > accomplish this? > > why not use .forward? is he concerned about stale forwarding > addresses? i.e., the ldap database has a new email address and > the .forward still has the old forwarding address. > 1. .forward can run programs, so you can dynamically read the > destination address from ldap and then send the email to that. > > 2. .forward can be automatically re-generated when forwarding > addresses change (there will still be races, but they can be > managed and minimized if you set the batch update interval > shorter). > > is the .forward prohibition arbitrary? are you allowed to use .procmailrc > as a .forward replacement? whatever you can do with .forward you > can do with .procmailrc. > > yet another alternative is /etc/postfix/aliases.db. just generate a new > aliases file whenever the forwarding database changes and then run > postmap on it to create aliases.db. i think you need to kick postfix > to get it to reload aliases, it probably won't notice the change by itself. > > hehe, there might be other options. e.g., fetchmail can do forwarding. > but i don't like it since fetchmail has to know the email passwords of > the source email addresses before it can check the mail and forward > to the final destination. fetchmail has its place, but your requirement > is probably not one of them :). some sort of milter might also be an > option. but i don't know what postfix has in the way of milter > architecture and API. > > tiger > > -- > Gerald Timothy Quimpo gquimpo*hotmail.com tiger*sni*ph > Public Key: "gpg --keyserver pgp.mit.edu --recv-keys 672F4C78" > My strength is as the strength of ten, > Because my heart is pure. > Alfred, Lord Tennyson, "Sir Galahad" > -- > Philippine Linux Users' Group (PLUG) Mailing List > [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) > Official Website: http://plug.linux.org.ph > Searchable Archives: http://marc.free.net.ph > . > To leave, go to http://lists.q-linux.com/mailman/listinfo/plug > . > Are you a Linux newbie? To join the newbie list, go to > http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
