Does it have to be Mutt or can he use Pine?

Matt

> -----Original Message-----
> From: Kit Halsted [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 23, 2001 11:25 AM
> To: Ken Jones
> Cc: [EMAIL PROTECTED]
> Subject: Re: Virtual User, symlink, Mutt...
> 
> 
> Sorry, I really should have been more clear. Here's what I'm 
> looking for:
> 
> A user, let's call him Patrick, has to get POP mail at night when he 
> gets home. He also has to be able to read mail via SSH & Mutt during 
> the day.
> 
> Here's the kicker: it is strictly forbidden for users on this system 
> to send shell passwords out in cleartext, so a .qmail file forwarding 
> to his home dir is out. Use of APOP is also out for various reasons.
> 
> Have I painted myself into a corner, or is there some permissions 
> magic I can work on his vpopmail Maildir to pull this off?
> 
> Thanks,
> -Kit
> 
> At 12:57 PM -0600 2/23/01, Ken Jones wrote:
> >Kit Halsted wrote:
> >>
> >>  Hi-
> >>
> >>  I'm using Qmail 1.03 & vpopmail 4.9.6-1 on OpenBSD 2.8 -stable.
> >>  Everything works as expected & I'm a happy camper. Of 
> course, there
> >>  is one problem, or I wouldn't be writing...
> >>
> >>  I have virtualized our primary domain so shell users 
> won't be sending
> >>  their passwords all over the net in cleartext. This is fine with 5
> >>  out of 6 consultants, but one guy used telnet & Pine 
> extensively on
> >>  our old system & really wants that functionality. I'm 
> thinking it'll
> >>  be fine, just set him up for ssh & Mutt & set a symlink for
> >>  /home/vpopmail/domains/ourdomain.com/user/Maildir in 
> /home/user. Of
> >>  course, he gets a permission denied error. I know the virtual user
> >>  Maildir has to be owned by vpopmail:vchkpw. Is this a Catch-22, or
> >>  does anybody know of a workaround for this?
> >>
> >>  TIA,
> >>  -Kit
> >
> >The easiest work around is to add a forward from the virtual
> >account to his local /etc/passwd account.
> >
> >Either of these two forwards should work
> >&[EMAIL PROTECTED]
> >&user
> >
> >Where user = his shell login.
> >
> >Ken Jones
> 
> 

Reply via email to