Gordon Rowell wrote:
> This is quite bizarre. I have raised an internal bug report on this, as it
> does appear that the most recent fetchmail update has this problem, though
> I am not sure under which circumstances.
Well, my clue came from the fetchmail manpage and what it had to say
about exit code 2--in particular, about "a protocol fetchmail wants to
use is not listed in /etc/services". Apparently this was added some
time after 5.5.0 and before 5.7.4, but I have no idea why--perhaps to
more easily allow for installations which place these services on
non-standard ports?
Since the only legal descriptor for pop3 in fetchmail is "pop3" (and
not pop or pop-3), I'd expect this problem will occur any time a user
tries to use fetchmail to check a POP account. Fortunately, it should
be a simple fix--a one-line custom template for /etc/services, or adding
the line to template-begin should do the job.
--
Dan Brown, KE6MKS, [EMAIL PROTECTED]
"Meddle not in the affairs of dragons, for you are crunchy
and taste good with ketchup."
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
