I'm using currently KDE 3.2 with KMail 1.6 After an emerge -u world (with ACCEPT_KEYWORDS="~x86" in make.conf) these packeges upgraded in the night (i deleted those which "not intresting", for example xfce packages): emerge (1 of 41) net-mail/mailbase-0.00-r6 to / emerge (3 of 41) net-mail/fetchmail-6.2.5 to / After I came back to my machine I just reailised, that KMail could not fetch messgaes from my local account because of "Transmission failed: Could not lock /var/spool/mail/bzs". I think the reason is that I'm not a member of the "mail" group, but I'm only a lamer... Reproducible: Always Steps to Reproduce: 1. fetching mail via fetchmail (as normal user) from my pop3 server through procmail (in my .procmailrc: SHELL=/bin/bash MAILDIR=/var/spool/mail LOGFILE=$HOME/.procmail/procmail.log and I'm using the defult locking when it's needed.) 2. try recevieng with kmail 3. recognise the error Actual Results: all the same Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20040207-r0, 2.4.22-gentoo-r5) ================================================================= System uname: 2.4.22-gentoo-r5 i686 Intel(R) Celeron(R) CPU 2.40GHz Gentoo Base System version 1.4.3.13 Autoconf: sys-devel/autoconf-2.59-r1 Automake: sys-devel/automake-1.8.2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -mcpu=pentium4 -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -mcpu=pentium4 -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb crypt cups encode foomaticdb gdbm gif gphoto2 gpm gtk gtk2 imagemagick imlib java jikes jpeg kde libg++ libwww mad maildir mbox mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline ruby samba sdl slang spell ssl svga tcltk tcpd tiff truetype unicode usb x86 xml xml2 xmms xv zlib"
I don't see how this is a kmail bug - if you want to use local mail like that it's your responsibility to set it up correctly, right?
Aditionally there is an option in the kmail receiving option for a local mailbox to specify whether a lockfile is used and if so, where it resides. Another option (use with care on an NFS mailbox) is to use fcntl locking which basically asks the OS to do locking. This does not need access for a lockfile. Basically read the kmail manual.
I think the reason is shown below (by the changed permissions), but maybe I'm wrong...: diff net-mail/mailbase/mailbase-0.00-r5.ebuild net-mail/mailbase/mailbase-0.00-r6.ebuild /usr/portage $: diff net-mail/mailbase/mailbase-0.00-r5.ebuild \ > net-mail/mailbase/mailbase-0.00-r6.ebuild ... < fperms 1777 /var/spool/mail --- > fperms 0775 /var/spool/mail 37c37 < chmod 1777 ${ROOT}/var/spool/mail --- > chmod 0775 ${ROOT}/var/spool/mail
