From owner-freebsd-hackers Tue Feb 20 14:00:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA09348 for hackers-outgoing; Tue, 20 Feb 1996 14:00:24 -0800 (PST) Received: from terra.stack.urc.tue.nl (terra.stack.urc.tue.nl [131.155.140.128]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA09339 for ; Tue, 20 Feb 1996 14:00:18 -0800 (PST) Received: from xaa.stack.urc.tue.nl (uucp@localhost) by terra.stack.urc.tue.nl (8.6.11) with UUCP id XAA21966; Tue, 20 Feb 1996 23:00:08 +0100 Received: (from freebsd@localhost) by xaa.stack.urc.tue.nl (8.7.3/8.6.12) id WAA00598; Tue, 20 Feb 1996 22:59:05 +0100 (MET) Message-Id: <199602202159.WAA00598@xaa.stack.urc.tue.nl> Subject: Re: pop3 and blocked users To: guido@gvr.win.tue.nl (Guido van Rooij) Date: Tue, 20 Feb 1996 22:59:04 +0100 (MET) From: "Mark Huizer" Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199602201925.UAA07476@gvr.win.tue.nl> from "Guido van Rooij" at Feb 20, 96 08:25:43 pm Reply-To: xaa@stack.urc.tue.nl (Mark Huizer) X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org Precedence: bulk > Shouldn't pop implementation check if users are having a shell not > listed in /etc/shells? Otherwise, blocked users will stil be able to > recieve mail.. Well... it's quite simple to change that. I just did it for my computing society. Simply check it in pop_pass.c and give a POP_FAILURE. But I feel a bit funny about it. When I had a machine with pop-accounts, I could imagine WANTING to give ppl a non-existant shell, so they can only access mail. Another thing I am going to do tomorrow or something is changing it so it won't give an error when the blocked user is connecting. It would be even better if it would standard generate a mailbox containing of only 1 message telling that the *()^^&* user is blocked and should take some serious action in stead of trying to read mail > > -Guido > Mark