Marcus Watts wrote:
>
>I find myself curious as to how these sites that presumably keep pop
>mailboxes in AFS handle mail forwarding. Do you handle mail forwarding
>on the pop servers? Do you allow programs, such as procmail and
>vacation? How do you handle AFS tokens and pags for such programs? If
>you haven't thought about this, and are using sendmail or something
>similar, what happens if a user creates a .forward in their home
>directory? Is it honored?
We pretty much punt on this, because allowing users to run arbitrary commands
on the pop server would get us into an arbitrary load ("Let's see, if I change
my .forward to run this _really big_ compile and send myself an email..."
Don't laugh. Things like this happen).
We set up our pop server with /bin/nosh as the shell for all the pop users.
That way, they can still forward their mail to another email address, but if
they try to run any commands, they can't. It sucks to be them, but we don't
see another choice.
For people in our department who have a desktop workstation, we _do_ allow
local mail delivery. In that case, the users are only using their own cycles
to do procmail, vacation, etc., not everyone else's cycles.
The same .forward problems exists for IMAP (.forward uses server CPU cycles).
We are working on some specific solutions (allow vacation and procmail, but
nothing else). We don't have a comprehensive solution on that one.
Dave
