>
>why does the user not get mail access?
>
Very good question,
I asked this one to myself as well.
The users are students at a high school, and one parent didn't want their
children using email.
The principal asked me if I could block it.
(Potato running IMP)
I then realized that the student has
* Mike Egglestone <[EMAIL PROTECTED]> [2001.11.27 08:45:21-0800]:
> I think I'll have to leave it the way it was.
yup. aside, maybe the principal should tell that parent (stupid
parent!) that email is not a bad thing and that what they are asking
you to do is censorship. either you provide intern
As others have said, there's no complete way to keep someone from sending
mail without losing other things. Here are some ideas though:
1.) In addition to the previously-mentioned mode of blocking mail receipt,
I can think of two other options:
a.) ln -s /var/spool/mail/user /dev/null
* Christopher S. Swingley <[EMAIL PROTECTED]> [2001.11.26 20:59:18-0900]:
> Dunno how to stop someone from sending mail. Maybe an iptables rule
> that uses the --m owner --uid-owner switches to block port 25 to
> that user? Course, if you're running potato, you've probably got a
> 2.2 kernel, so
* Mike Egglestone <[EMAIL PROTECTED]> [2001.11.26 21:51:42-0800]:
> Is there a simple way to stop a user from being able
> to send and receive email?
>
> Potato r3 running exim.
not really, since that user could always telnet to a relay through
port 25 and send with SMTP.
if you were using iptab
> Is there a simple way to stop a user from being able
> to send and receive email?
Stopping the receiving is easy -- just create an empty file in
/var/mail/$username and change it's permissions to 444.
Dunno how to stop someone from sending mail. Maybe an iptables rule
that uses the --m owner -
Hi,
Is there a simple way to stop a user from being able
to send and receive email?
Potato r3 running exim.
Thanks in Advance!!
Mike
7 matches
Mail list logo
