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

[Cruzio Research <research@xxxxxxxxxx>]

Sendmail can be configured to support virtual pops, which is what I
would need to
do to make this work.  I don't think I'm really in the mood to deal with
it this
afternoon...   8-)

Mark

Will Eberle wrote:
> 
> My two cents worth: As I understand it, usernames cannot be duplicated on
> the entire server as they are a function of the sendmail program. However,
> why can only one instance of that program be running on the server? Why
> can't I run several different copies of the sendmail program on the same
> box? I am not a born-again Linux convert, as you may have noticed by now. I
> come from the dark side (Microsoft stuff). I know how to set up folders,
> files, partitions and other stuff to do this in a Windows environment; can
> this not be done with Unix? Also, what I find most troubling as an
> administrator is, why isn't there a list of all user names already in use on
> that server I can easily call up, (like with a click on an icon in the GUI?)
> so I don't have to try setting up the username only to be told by the GUI
> that that particular user account cannot be configured (also the message why
> isn't very specific).
> 
> -----Original Message-----
> From: cobalt-developers-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-developers-admin@xxxxxxxxxxxxxxx]On Behalf Of Cruzio Research
> Sent: Friday, October 19, 2001 1:37 PM
> 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