In what I am talking about, there's no need for a shell environment on
the IMAP servers, at least not for ordinary users. Nobody is going to
run Pine on the IMAP server. The whole point of a dedicated IMAP
server is for it to be IMAP-only. Dedicated servers are more reliable
(less likely to crash) than machines that have to run an unpredictable
mix of tasks.
I guess that's what confuses me... I'm not seeing how a server can simply
be an imap server. The email needs to get onto the server somehow (in
our case sendmail/mail.local). In the delivery process there might be
additional milters in use (in our case Spam Assassin and ClamAV). Then
at the user level there are email related dot files for those who choose to
play with their forwarding (.forward), vacation messaging (.vacation*), or
additional filtering (.procmailrc). We would prefer that all users have
open
shell access in order to personalize their email configuration/make changes
to their dot files if desired.
Part if the advantage to using UW imap over Cyrus for example is that it's
not a black box and plays well with the rest of the software that might or
might not be installed. We're still using pine in traditional unix mode, so
that's what I was thinking when I used pine as an example. Forgot that it
can also be used as an imap client.
-Brian
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
