Re: [cobalt-developers] E-mail names on RaQ4

[Cruzio Research <research@xxxxxxxxxx>]

It's been awhile since I worked on this, but this might be able to get
you started.

Each domain has to have it's own password file, in it's own directory
(like maybe
/home/sites/www.domain.com/passwd and
/home/sites/www.domain2.com/passwd).  You can
create the password entries with the htpasswd program (or write a script
to allow the
end user to do so).

Each domain also needs to have it's own mail directory, so that there
isn't any collision
with mailboxes from other domains.

You tell sendmail where to find the mail, qpopper where to find the
password file and mail, and 
ftp where to find the password file on each domain.

With Sendmail, you have to change the .mc file to tell it where to find
this stuff.
With qpopper and ftp you should be able to add an entry for each domain
to hosts.allow to exec
the pop and ftp programs with command line switches that allow you to
define the password file
and the where to find the mailbox directory for a domain.

Hopefully that will get you started.  I don't have specific instructions
for exactly how to do this written
up, and I'm not sure there isn't something about Linux that I don't
understand that would make this impossible,
but that's how we've configured it on our BSDi boxes.

fun fun fun.

Mark Hanford



Richard Badua wrote:
> 
> How do you make your bsdi box authenticate to different shadow files?  I
> want to try and do that put don't know where to start?
> 
> Richard
> 
> -----Original Message-----
> From: Cruzio Research [mailto:research@xxxxxxxxxx]
> Sent: Friday, October 19, 2001 7:37 AM
> To: cobalt-developers@xxxxxxxxxxxxxxx
> Subject: Re: [cobalt-developers] E-mail names on RaQ4
> 
> Yes, but you could have individual password files for each domain, which
> would allow each
> domain to have e-mail accounts (not aliases) unique to a host, not the
> entire server.  That's
> what we've done with our (heavily customized) BSDi servers that we are
> currently running.
> 
> I was wondering if anyone here had done anything of that sort, because I
> don't want to have to
> start at ground zero.
> 
> However, I also don't want to have to rewrite the GUI to interface with
> everything, otherwise there
> is very little reason for us to switch, so I may just have to tell our
> IS department that the way
> things work is gonna change a bit.
> 
> Thanks for the replies.
> 
> Mark
> 
> Steve Werby wrote:
> >
> > "Cruzio Research" <research@xxxxxxxxxx> wrote:
> > > Has anyone managed to change a RaQ4 to allow e-mail names that are
> > > unique only to domains and not
> > > to the entire RaQ?
> > >
> > > I'm familiar with the workaround of creating an alias, but that doesn't
> > > work for my situation.
> >
> > On Linux servers usernames are unique.  As you know, you can create email
> > aliases unique to a host, not the entire server.
> >
> > > We are an ISP looking to switch our web servers to the RaQ and we would
> > > be hosting several different customers on a machine.  Customers are not
> > > going to want to hear that they can't have a specific e-mail address
> > > under their domain (without a workaround) when our current platform
> > > allows that.
> >
> > Do you mean that they won't be happy that their username (used for login)
> > has to change because usernames are unique?  I think most customers would
> > tolerate this, but you know your customers better than I do.  Even if
> there
> > is a way to allow logins to include the domain name as a workaround it
> would
> > surely breakly most of the GUI.  If you aren't planning on using the GUI
> and
> > the users are email only there's probably a solution that can be
> > implemented, but since you said "web servers" and I get the feeling you
> > won't be abandoning the GUI I'll take it that's not the case.
> >
> > --
> > Steve Werby
> > President, Befriend Internet Services LLC
> > http://www.befriend.com/
> >
> > _______________________________________________
> > cobalt-developers mailing list
> > cobalt-developers@xxxxxxxxxxxxxxx
> > http://list.cobalt.com/mailman/listinfo/cobalt-developers
> 
> --
> 
> Mark Hanford
> research@xxxxxxxxxx
> 
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers
> 
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers

-- 

Mark Hanford
research@xxxxxxxxxx