On Tue, Dec 06, 2016 at 07:33:06PM -0500, Gene Heskett wrote: > On Tuesday 06 December 2016 17:26:55 Jude DaShiell wrote: > > > It may be an ownership problem if you have the fetchmail package > > installed on your system. The .fetchmailrc file may be in your > > account but that doesn't necessarily mean you explicitly own it. > > > > On Tue, 6 Dec 2016, Bob Holtzman wrote: > > > Date: Tue, 6 Dec 2016 16:21:23 > > > From: Bob Holtzman <hol...@cox.net> > > > To: debian-user@lists.debian.org > > > Subject: "command not found" > > > Resent-Date: Tue, 6 Dec 2016 21:21:52 +0000 (UTC) > > > Resent-From: debian-user@lists.debian.org > > > > > > I've run across this a number of times in the past, but it's usually > > > a permissions problem, easily fixed. Not this time. > > > > > > holtzm@localhost:~$ ls -l .fetchmail > > > -rwx------ 1 holtzm holtzm 365 Nov 26 14:05 .fetchmail > > Who setup those perms? Of course it will fail. Heres mine.
Me, and they have been working flawlessly on another installation. > > -rwxr-xr-x 1 root staff 754964 Feb 11 2015 /usr/local/bin/fetchmail > > fetchmail starts as root, and immediately does a set uid to the user that > launched it, and its been working that way here for for nearly 2 > decades. Its running as a daemon, as the user me, pulling new mail > every 3 minutes since the last reboot 11 days back. > > > > > > Sure looks like it aught to work. It's probably something simple > > > that I'm missing and when someone points it ought I will ram my head > > > into a wall in self-disgust. > > Not recommended. But a repeated reading of the man page might be > illuminating. Either that or my learning to proof read would be equally illuminating. -- Bob Holtzman "Bother", said Pooh, as he chambered another round...