RE: [cobalt-users] 2 user names - say it aint so

["WebWorksPro.Net, Inc." <heather@xxxxxxxxxxxxxxx>]

Thanks,

Actually a few people were nice to have responded off-list.  Other
suggestions included using a mailing list (but not majordomo...I have been
warned against this), Read more about sendmail (I agree!  You can do
anything if you read...Problem is more-often-than-not lack of time on my
part).

I'm obviously a newbie who is most familiar to shared hosting on an
NT---also a traditional creative (yikes).  But I think this is what you are
saying:

1)  Create a unique user s011u432
2)  Put info in as an alias of this user
3)  Create .forward file with various ISP destinations.

Geez is it that easy?

Heather

-----Original Message-----
From: Rodolfo J. Paiz [mailto:rpaiz@xxxxxxxxxxxxxx]On Behalf Of Rodolfo
J. Paiz (E-mail)
Sent: Tuesday, December 12, 2000 12:05 PM
To: heather@xxxxxxxxxxxxxxx; Cobalt-Users (E-mail)
Subject: RE: [cobalt-users] 2 user names - say it aint so


Double-check, when you reply to the list, that you're actually replying to
the list. That sounds a little odd, but there seems to be a problem
somewhere and your reply came directly to me. So I put the list back on.

> Your responses (for my questions and others) and always
> *extremely* helpful!

Hey, thanks...

> ...But then I ran into another forwarding dilema, of course!

<grin> Don't we always?

> Client wants info@ to forward to several different ISPs.
>
> info@ points to clienthome@xxxxxxx
> info@ points to clientoffice@xxxxxxxxxxxxx
> info@ points to trainingdirector@xxxxxxx
>
> I've already set a user as "info" on another domain with a
> .forward file, so I cannot create another user "info".  So,
> I'm just a little stumped on what to do from here.

<DANGER, WILL ROBINSON -- DANGER!>

What I'm about to say sounds perfectly reasonable to me, but I'm making this
up, OK? I hope this works great; but let's get another opinion in here
before you go trusting my inspirations...

>From what little I know, you're pretty much going to have to delete the
user
info. Assuming that this user only uses your box to check mail and upload
files but doesn't have or need shell access, it's not a major problem.

Copy the encrypted password from /etc/passwd (or /etc/shadow), delete the
user info, set up user s011u432 (or whatever), make sure you copy the
encrypted password back, and set him/her up the alias info. Even better,
write a small script to do that (not difficult) and tell cron to run it at
4:00am. That should work fine, and hopefully your customer won't get any
mail in the 10-second period during which his account is gone.

Note that this *would* cause some problems if the user has files in his/her
directory (such as scripts, a personal website, etc.) that he/she needs. If
this were true then more changes and things would have to be made.

Again, I *think* this is fine. Let's see if someone else adds to the pot.

--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx <mailto:rpaiz@xxxxxxxxxxxxxx>