Some more data on my "timing" problem...
It turns out I had one other variable between the "it works" and "it doesn't
work" situations: start-stop-daemon (which I use in my boot script to start
and stop server processes, like fetchmail; this is under linux 2.2.19).
For some reason, using the fetchmailrc file to start fetchmail via
start-stop-daemon causes a problem, while starting it from the commandline
doesn't.
I realize this means the problem is likely in start-stop-daemon, and probably
has nothing to do with fetchmail, but... anybody have any thoughts on why
start-stop-daemon is having a problem with the fetchmail invocation?
- Mark
-----Original Message-----
From: Mark Olbert [mailto:mark(_at_)arcabama(_dot_)com]
Sent: Wednesday, November 14, 2001 1:22 PM
To: 'fetchmail-friends(_at_)lists(_dot_)ccil(_dot_)org'
Subject: Bizarre Timing Problem: Fetchmail, Pop3 and SSH
I am having a devil of a time getting fetchmail and ssh to play nicely with
each other in retrieving mail from a pop3 server.
I've gotten the complex to work, using the following fetchmailrc file, >>but<<
only when I invoke fetchmail in >>verbose<< mode:
========================
# fetchmail control file (/etc/fetchmail.rc)
# updated 11/14/01
#
set postmaster "mark"
set no bouncemail
set syslog
set daemon 3600
poll localhost
via localhost
port 1234
timeout 30
protocol pop3
username [remote user] password [remote password] is
[local user] here no keep fetchall
limit 0 mda /usr/local/bin/procmail -d %T"
preconnect "(ssh -C -f [remote user](_at_)[remote pop3 server]
-L 1234:[remote pop3 server]:110 sleep 5); sleep 5"
==================
In other words:
fetchmail -v -f /etc/fetchmailrc
works, while
fetchmail -f /etc/fetchmailrc
doesn't work. The latter fails with error 32512, localhost refused connection
(the daemon does start, however... and it gives the same error every time you
wake it up).
Any suggestions on how I can configure this stuff to work without having to
bloat up my log files??? <grin>
- Mark
mark(_at_)arcabama(_dot_)com