[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] Second VIRTUSERTABLE
- Subject: Re: [cobalt-developers] Second VIRTUSERTABLE
- From: John Keegan <john@xxxxxxxxxxxxx>
- Date: Sat Mar 23 00:07:24 2002
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
> I don't believe so; you can add additional alias files, but only one
> virtusertable, as far as I can tell. You can add anything you need to
> the bottom of the virtusertable and then rehash it yourself.
>
> May I ask why you need/want to do it?
Thanks for your reply, Jeff.
What I am looking to do is to create a system for managing mail forwards for
domains that are hosted outside of the Raq GUI. My thought was to create a
second file formatted in the VIRTUSERTABLE style, and to have that included
as part of the sendmail configuration.
Then it would be a simple matter to have those mail forwards maintained in a
MySQL database, for example, and just have a script pull out the forwards
and write them out to this file.
The advantages to having a second file (lets call it MAILFORWARDTABLE) and
hashing that instead of including this info in the actual VIRTUSERTABLE:
a) This second file would not be used by the GUI, or by any other
process, therefore there would be no file locking issues.
b) It would be easier (simpler and more reliable programming) to simply
rewrite this second file straight out of a database, than to rewrite chunks
of the VIRTUSERTABLE whenever we need to update some of the mail
forwardings.
So I am just looking for tips for creating additional alias files, I
obviously don't need a second VIRTUSERTABLE, just another file that works in
the same way. Or if anyone has a suggestion for doing this another way, I
would appreciate any insight.
--
John Keegan
john@xxxxxxxxxxxxx
http://RackShare.com
>> Does anyone know if it is possible to create a second VIRTUSERTABLE style
>> file and have that included as part of the sendmail configuration? If so, I
>> would appreciate any tips or pointers to info on how to go about creating a
>> separate additional file for routing mail.