On Mon, 26 Jul 1999, Martijn Koster wrote:
> On Mon, Jul 26, 1999 at 12:09:21PM +0300, Ira Abramov wrote:
> >
> >
> > In a new installation I'm doing for a client, I found the need for the
> > /var/qmail/control/recipientmap I used to use back in the 1.01 days. now
> > it seems not to respond, it's not even in the qmail-control manpage. was
> > it really canceled? is there an equivalent, i.e. so I won't need to break
> > up the old sendmail rules file into 11300 little .qmail files!!!
>
> A grep through the source 1.03 directory turns up UPGRADE:
>
> WARNING for upgrades from 1.01: recipientmap is gone. The virtualdomains
> mechanism has been expanded to support virtual users.
it doesn't really give the same functionality since it adds a prepend
instead of translating...
to illustrate: my current set of rules for sendmail looks like this:
@bothers.com [EMAIL PROTECTED]
@building.com [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
@stooge.com [EMAIL PROTECTED]
.
.
.
so user or entire domain (full or as fallback) are forwarded to local
users. I don't need prepends here. furthermore, it's rare but I may
sometimes need to forward one of those users' Email out (and not to
mail.inter.net.il)
right now the only compact solution I see is to send this file to a filter
that will chop up and 'sort -u' to forward them all to virtualdomains
which in turn will send them all to virforward-<user>@localhost, then
~alias/.qmail-virforward-default will peel $LOCAL and change the '@' into
'=', then forward it to a fastforward patched to look at a special
aliases.cdb which I made from the original rules file by changing @ to =
and changing the double <tab> to a colon.
as for catch-all @domain.com domains, they even complicate things further.
seems like I'll have to break it down to a gazillion .qmail files, which
is something that will not be fun to manage.
anyone knows a better, cleaner way? :-(
