[lug] Awkward server situation

[Justin]

Ahh, I see. So, correct me if I'm wrong, but in my particular 
situation, would I use:
inbox-path={mainbox.jackmoves.com}/var/spool/mail/$USER
Or does "inbox" have some special funtion? Also, would the user need 
to supply a username or password, cause it looks like it would attempt 
an imap or pop connection. I imagine the mail spools are kept on the 
mainbox too, or no? Thanks again...

Justin

> Justin, it's not that wierd, really.  People do it all the time.  If 
a subset of your users have shell accounts on shellbox, that's fine.  
When you set up the pine software (or other MUA) on shellbox, the 
trick is to edit the global configuration file (ie. /etc/pine.conf) to 
set your IMAP (or POP3) inbox-path to "{mainbox.jackmoves.com}inbox" 
and you should be all set.  I'm assuming, of course, that mainbox runs 
imapd and/or popd.
> 
> -John
> 
> Justin wrote:
> > 
> > I kind of have a wierd situation here. I'll start by explaining my
> > current server setup. I have a single server that does all the work
> > for my domain (besides DNS). It performs the following funtions:
> > webserving, email service, database, ftp service, and also shell
> > services for IRC related things. What I want to do is split off the
> > shell services part of the machine to a different box. So
> > mainbox.jackmoves.com will support all the important stuff like 
web,
> > email, db, and ftp. The other shellbox.jackmoves.com will be there 
for
> > all IRC and shell related services. I plan on splitting up my user
> > base since most ppl that use the web/email services don't use (or 
know
> > how to) use a linux shell. The shell users will have user accounts 
on
> > the mainbox.jackmoves.com server as well as 
shellbox.jackmoves.com. My
> > main concern is, since my mail server runs on 
mainbox.jackmoves.com,
> > will users on shellbox.jackmoves.com be able to send/retrieve
> > @jackmoves email from the shellbox with say Pine, mutt, or elm? My
> > main reasoning for this setup is so all the data on the mainbox
> > (web/email/db) is safe from a potential hack of the shellbox since 
it
> > is exposed to IRC and the like. I'm still confusing myself trying 
to
> > figure this all out so sorry if I am making no sense. Those of you
> > that do understand what I'm trying to do, I'd appreciate any
> > suggestions or input. Thanks in advance...
> > 
> > Justin
> > 
> > -----
> > glow at jackmoves.com
> > www.jackmoves.com
> > 
> >                                                   
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> > 
> >    Name:
> >    Type: unspecified type (application/octet-stream)
> 
> -- 
> 
>   - John Hernandez - Network Engineer - 303-497-6392 -
>  |  National Oceanic and Atmospheric Administration   |
>  |  Mailstop R/OM12. 325 Broadway, Boulder, CO 80305  |
>   ----------------------------------------------------
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> 
> 

-----
glow at jackmoves.com
www.jackmoves.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: "
Type: application/octet-stream
Size: 37 bytes
Desc: not available
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20010626/bdccccaf/attachment.obj>