We chose to do the same thing except one of the criteria was to manage a
spool like approach, rather than deliver into users home space. We chose
to create 30 AFS mail spools and use a modulus function on the users UID
to determine which spool they should fall into.
BTW, 30 is quite an arbitary number.. It can be increased, decreased at
any time by changing our shared library, and moving some mail spools
around.
Our primary mail client is Pine which required some modifications along
with elm, imap, a popper etc.
We have been in production for two months now and are very happy with the
performance. We are currently using only one mail hub but we are
naturally looking forward to scaling upward.
My advice to you is that a single spool is a bad idea. You need to split
the spools according to some criteria so that you can take advantage of
some AFS volume/quota management.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[EMAIL PROTECTED]
Systems and Networks Department
211 Forney Building, UNC-Greensboro
Phone: (910) 334-3338
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Tue, 22 Oct 1996, Jae-young Kim wrote:
> Date: Tue, 22 Oct 1996 09:57:43 +0900 (KST)
> From: Jae-young Kim <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: AFS-based mail spool
>
>
>
> We're considering creating a AFS-based mail spool so that every
> AFS users can have a common mail address and read mails from anywhere.
> There are two different solutions we're comparing and we'd like to hear
> any comments, suggestions and experiences on these solutions.
>
> The first solution is to deliver mails to each user's home
> directory. A central mail server receives mails, it obtains a special
> token which enables to deliver mails to user's home, and deliver the mail
> to $HOME/Mail by 'procmail' process.
>
> The second solution is to delver mails to a central AFS-based mail
> spool directory. For example, there's /afs/p/mail/spool/$USER directory
> for each user's mails.
>
> Both solutions are required to satisfy the seamless transitions
> for current users which are accustomed to the local mail delivery and
> minimize the change of the current MUA binaries (mail, elm, pine, ...).
>
> We encounters some problems such as file locking, ACL setting,
> MUA recompiling, user tranining, etc... Any idea is highly appreciated.
>
> Sincerely,
> Jay Kim
> --
> ___________________________________________________________________________
> _____ ___ __ __
> __/\__ |_ _| / _ \ \ \_/ / Remember Yesterday, Dream about Tomorrow
> \ / | | | /_\ | \ / but ... LIVE TODAY !!!
> /_ _\ | | | _ | | |
> \/ __| | | | | | | | [EMAIL PROTECTED] (Jae-young Kim)
> |___/ |_| |_| |_| Researcher, Computer Center/POSTECH, KOREA
> ___________________________________________________________________________
>
