Michael,
Haven't yet seen a response, so I'll write one. :)
You can do this fairly easily by setting up the following:
virtualdomains:
corp.rocketcash.com:alias-corp_rocketcash_com/
Then, you'll need to 'mkdir ~alias/.qmail-corp_rocketcash_com'
Inside that directory, you'll want to create a file called '-default'
(this can be tricky, as most programs see - as a switch delimiter. You
will probably need to specify the file as ./-default while in that
directory.) Inside this file, place the line:
|forward ${DEFAULT}@corp.netzero.net
The above file acts as a .qmail-default for that domain, forwarding
anything not already specified to the same [EMAIL PROTECTED]
You can now create specific user files in the same directory to override
this behaviour.
Say you wanted [EMAIL PROTECTED] to forward to
[EMAIL PROTECTED] You would create a file called -jamin in the
~alias/.qmail-corp_rocketcash_com directory, and inside it place:
&jbrown@@corp.netzero.net
Hope this makes sense to you.
Jamin
On Mon, 5 Feb 2001, Michael Boyiazis wrote:
> I have a situation which leaves me (I think) caught between
> virtualdomain and smtproute files...
>
> We have qmail running on a firewall box and forwarding
> to the corporate exchange server...
>
> We have users from one domain:
> aimtv.com which we use smtproutes to forward directly
> to a virus scan box... all the email addresses in the aimtv
> domain match those found on the forwarding domain, so
> smtproutes is appropriate.
>
> I'd like all our domains to be that way, but each domain that
> the virus scan box checks needs extra licensing ($$)...
>
> so, we have another domain, corp.rocketcash.com...
> some email addresses are [EMAIL PROTECTED]
>
> the mail comes in and I use a .qmail file to forward these to
> [EMAIL PROTECTED]
>
> future new addresses will be along the line of
> [EMAIL PROTECTED] which will forward
> to the equivalent on corp.netzero.net....
>
> is there a way to catch all those future addresses and forward them to
> @corp.netzero.net w/o using smtproutes and without creating a separate
> .qmail for each new employee? would a catchall .qmail
> file be able to do that? i don't see how. it makes sense to use smtproutes
> but i cannot from what i can see.
>
> any suggestions?
>
> Thanks,
> --
> Michael Boyiazis
> [EMAIL PROTECTED]
> Mail Architect, NetZero, Inc.
>
>
-----------------------------------------------------------------
Jamin A. Brown Systems Operations Department
[EMAIL PROTECTED] * Great Works Internet * 207.286.8686 x142
RSA PGP Key: http://www.gwi.net/~jamin/pgp/jamin.asc
