From owner-freebsd-hackers Wed Aug 14 10:13:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA14787 for hackers-outgoing; Wed, 14 Aug 1996 10:13:04 -0700 (PDT) Received: from cronus.oanet.com (richmond@cronus.oanet.com [204.209.13.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14780 for ; Wed, 14 Aug 1996 10:12:59 -0700 (PDT) Received: from localhost (richmond@localhost) by cronus.oanet.com (8.7.3/8.6.12) with SMTP id LAA20179; Wed, 14 Aug 1996 11:12:34 -0600 (MDT) Date: Wed, 14 Aug 1996 11:12:33 -0600 (MDT) From: Raymond Richmond To: Joe Greco cc: bsdi-users@bsdi.com, hackers@FreeBSD.ORG Subject: Re: Popper errors. In-Reply-To: <199608141703.MAA12125@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It is symlinked actually, I was planning on changing the partition to /var/mail but at this time it is not an option for me. The only thing I noticed was that the group for the mail files in question were sometimes different than that of the pop file. This hsould not matter however as the file permissions are set on the user, not group. On Wed, 14 Aug 1996, Joe Greco wrote: > > Recently we moved our mail from the var partition to a new > > one to accomodate our space needs. After the move a great many of our > > users recieve the following error. > > > > Aug 10 06:30:59 cronus popper[12883]: -ERR Unable to copy mail spool file > > Wrong permissions on the new spool directory? You did symlink /var/mail to > the new location, yes? Your POP mail server looks like it's already > configured to use /var/mail for temp files, that's good. > > (typically it is easier to mount a new disk as /var/mail than it is to > play games and dink with symlinks). > > ... JG > -- __^__ __^__ ( ___ )------------------------------------------------------( ___ ) | / |---Raymond Richmond---Question Man-------(403)430-0811 -| \ | | / |---------OA Internet----------Technical Support---------| \ | |_*_| |_*_| (_____)----------------richmond@oanet.com--------------------(_____)