Hello again, and thanks for all your help so far.
Hopefully I've got this a little better nailed down.
My .fetchmailrc looks like this (I'll try to remember to blank out the
passwords this time):
defaults
protocol POP3
is benfell here
fetchall
forcecr
mda "/usr/bin/procmail -f - "
poll mail.yyyyyyyy user dbenfell password xxxxxxx
poll antares.xxxxxxxxxxxxx port 11110 user benfell pass xxxxxxxxxxxx
preconnect "ssh -C -f [EMAIL PROTECTED] -L
11110:antares.xxxxxxxxxxxxx:110 sleep 5"
poll area66-1.dsl.speakeasy.net port 11110 user benfell pass
xxxxxxxxxxxx
preconnect "ssh -C -f [EMAIL PROTECTED] -L
11110:area66-1.dsl.speakeasy.net:110 sleep 2"
poll pop3.zzzzzzzzzzzzz user dbenfell password xxxxxxx # keep no
fetchall
This formula worked very, very briefly, once, in fact, on antares, a
machine where I have an account but not administrative access and
which runs sendmail. Mostly it isn't working there either. The other
flavors people have sent me haven't made any difference, so I'm
assuming my problem isn't in .fetchmailrc. area66-1 is running qmail.
As you can see, I'm trying this on two machines, antares and area66-1.
area66-1 is my server.
Since I omitted the --syslog and --invisible options, I get a little
more information on the terminal where I'm running this:
1 message for dbenfell at mail.yyyyyyyy (2133 octets).
reading message 1 of 1 (2133 octets) .. flushed
Warning: Remote host denied X11 forwarding, perhaps xauth program
could not be run on the server side.
fetchmail: POP3 connection to antares.xxxxxxxxxxxxx failed: Connection
refused
fetchmail: Query status=SOCKET
Warning: Remote host denied X11 forwarding, perhaps xauth program
could not be run on the server side.
Local: bind: Address already in use
fetchmail: pre-connection command failed with status 65280
fetchmail: Query status=SYNTAX
fetchmail: No mail for dbenfell at pop3.zzzzzzzzzzzzz
Going to my own server, area66-1, I see in /var/log/messages:
Jun 22 08:50:25 area66-1 sshd[2011]: log: Connection from
216.254.42.100 port 1022
Jun 22 08:50:25 area66-1 sshd[2011]: log: RSA authentication for
benfell accepted.
Jun 22 08:50:25 area66-1 sshd[2013]: log: executing remote command as
user benfell
Jun 22 08:50:27 area66-1 sshd[2011]: log: Closing connection to
216.254.42.100
Jun 22 08:55:39 area66-1 sshd[2014]: log: Connection from
216.254.42.100 port 1022
Jun 22 08:55:40 area66-1 sshd[2014]: log: RSA authentication for
benfell accepted.
Jun 22 08:55:40 area66-1 sshd[2016]: log: executing remote command as
user benfell
Jun 22 08:55:42 area66-1 sshd[2014]: log: Closing connection to
216.254.42.100
Jun 22 08:59:19 area66-1 sshd[2018]: log: Connection from
216.254.42.100 port 1023
Jun 22 08:59:31 area66-1 sshd[2018]: log: RSA authentication for
benfell accepted.
Jun 22 08:59:40 area66-1 su: (to root) benfell on /dev/pts/0
Jun 22 08:59:40 area66-1 PAM-unix2[2031]: session started for user
root, service su
Jun 22 09:00:00 area66-1 /USR/SBIN/CRON[2048]: (benfell) CMD (cd
/home/benfell/setiathome; ./setiathome -nice 19 -email)
Jun 22 09:00:54 area66-1 sshd[2071]: log: Connection from
216.254.42.100 port 1021
Jun 22 09:00:55 area66-1 sshd[2071]: log: RSA authentication for
benfell accepted.
Jun 22 09:00:55 area66-1 sshd[2073]: log: executing remote command as
user benfell
Jun 22 09:00:57 area66-1 sshd[2071]: log: Closing connection to
216.254.42.100
Jun 22 09:06:14 area66-1 sshd[2074]: log: Connection from
216.254.42.100 port 1021
Jun 22 09:06:14 area66-1 sshd[2074]: log: RSA authentication for
benfell accepted.
Jun 22 09:06:14 area66-1 sshd[2074]: fatal: bind: Address already in
use
Jun 22 09:11:28 area66-1 sshd[2076]: log: Connection from
216.254.42.100 port 1021
Jun 22 09:11:29 area66-1 sshd[2076]: log: RSA authentication for
benfell accepted.
Jun 22 09:11:29 area66-1 sshd[2076]: fatal: bind: Address already in
use
Jun 22 09:16:43 area66-1 sshd[2097]: log: Connection from
216.254.42.100 port 1021
Jun 22 09:16:43 area66-1 sshd[2097]: log: RSA authentication for
benfell accepted.
Jun 22 09:16:43 area66-1 sshd[2097]: fatal: bind: Address already in
use
Jun 22 09:20:00 area66-1 /USR/SBIN/CRON[2102]: (benfell) CMD (cd
/home/benfell/setiathome; ./setiathome -nice 19 -email)
Jun 22 09:21:59 area66-1 sshd[2110]: log: Connection from
216.254.42.100 port 1021
Jun 22 09:21:59 area66-1 sshd[2110]: log: RSA authentication for
benfell accepted.
Jun 22 09:21:59 area66-1 sshd[2110]: fatal: bind: Address already in
use
Jun 22 09:27:13 area66-1 sshd[2119]: log: Connection from
216.254.42.100 port 1021
Am I interpreting this right when I think I'm succeeding in my ssh
access, but not in getting at port 110?
I've installed tcpserver, partly because of its stated benefits,
partly because the expertise on this list seems to be oriented in that
direction. Am I correct in understanding that tcpserver bypasses
hosts.allow and hosts.deny? I added the startup to my inetd startup
script. In part, it looks like:
case "$1" in
start)
echo "Starting tcpserver (smtp)"
tcpserver -u 502 -g 101 0 smtp /var/qmail/bin/qmail-smtpd &
echo "Starting tcpserver (monitoring for smtp)"
tcpserver -v -u 502 -g 101 0 smtp /var/qmail/bin/qmail-smtpd \
2>&1 | /var/qmail/bin/splogger smtpd 3 &
echo "Starting tcpserver (qmtp)"
tcpserver -u 502 -g 101 0 qmtp /var/qmail/bin/qmail-qmtpd &
echo "Starting tcpserver (pop3)"
tcpserver 0 pop3 /var/qmail/bin/qmail-popup area66-1.dsl.speakeasy.net \
/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir &
echo -n "Starting INET services (inetd)"
startproc /usr/sbin/inetd || return=$rc_failed
echo -e "$return"
;;
stop)
echo "Stopping all tcpserver processes"
killall tcpserver
echo -n "Shutting down INET services (inetd)"
killproc -TERM /usr/sbin/inetd || return=$rc_failed
echo -e "$return"
;;
I notice the second tcpserver task, the one that's supposed to monitor
smtp, isn't running. From /var/log/messages at startup:
Jun 21 23:30:16 area66-1 smtpd: 961655416.698982 tcpserver: fatal:
unable to bind: address already used
I keep running up against this "address already in use" nonsense and I
can't find a proper explanation of it anywhere. But the smtp side of
things seems to be working well -- it's just pop that isn't.
--
David Benfell
[EMAIL PROTECTED]
ICQ 59438240 [e-mail first for access]
---
There are no physicists in the hottest parts of hell, because the
existence of a "hottest part" implies a temperature difference, and
any marginally competent physicist would immediately use this to
run a heat engine and make some other part of hell comfortably cool.
This is obviously impossible.
-- Richard Davisson
[from fortune]
