[stunnel-users] stunnel woes under HPUX 10.20

[foner-stunnel at media.mit.edu]

[Please keep me CC'ed on replies!  I'm not on any stunnel lists.]

Stunnel 4.07 and 4.08 don't build under HPUX 10.20.  4.06 appears
to build, but doesn't appear to work---with a config file like this,
running on the local host:

    pid = /usr/local/var/stunnel/stunnel.pid
    client = yes
    foreground = yes
    # debug = debug

    [pop3s]
    accept = 110
    connect = our-pop-host:995

...and an attempt like this, using (for instance) Emacs 21.4a's movemail:

    movemail po:foner:localhost NEWMAIL [the-password]

...I get an infinite hang.  Enabling debugging causes stunnel to spit
out an infinite stream of a single line at maximum rate, and seems
unaffected by whether I'm trying to connect to it or not:

    # stunnel test-stunnel.conf
    1900.01.00 00:00:00 LOG5[9738:0]: stunnel 4.06 on hppa1.1-hp-hpux10.20 FORK+POLL with OpenSSL 0.9.7e 25 Oct 2004
    1900.01.00 00:00:00 LOG7[9738:0]: Snagged 64 random bytes from /users/foner/.rnd
    1900.01.00 00:00:00 LOG7[9738:0]: Wrote 1024 new random bytes to /users/foner/.rnd
    1900.01.00 00:00:00 LOG7[9738:0]: RAND_status claims sufficient entropy for the PRNG
    1900.01.00 00:00:00 LOG6[9738:0]: PRNG seeded successfully
    1900.01.00 00:00:00 LOG6[9738:0]: file ulimit = 60 (can be changed with 'ulimit -n')
    1900.01.00 00:00:00 LOG6[9738:0]: poll() used - no FD_SETSIZE limit for file descriptors
    1900.01.00 00:00:00 LOG5[9738:0]: 27 clients allowed
    1900.01.00 00:00:00 LOG7[9738:0]: FD 3 in non-blocking mode
    1900.01.00 00:00:00 LOG7[9738:0]: FD 4 in non-blocking mode
    1900.01.00 00:00:00 LOG7[9738:0]: FD 5 in non-blocking mode
    1900.01.00 00:00:00 LOG7[9738:0]: SO_REUSEADDR option set on accept socket
    1900.01.00 00:00:00 LOG7[9738:0]: pop3s bound to 0.0.0.0:110
    1900.01.00 00:00:00 LOG7[9738:0]: Created pid file /usr/local/var/stunnel/stunnel.pid
    1900.01.00 00:00:00 LOG6[9738:0]: daemon_loop: s_poll_wait: Invalid argument (22)
    1900.01.00 00:00:00 LOG6[9738:0]: daemon_loop: s_poll_wait: Invalid argument (22)
    1900.01.00 00:00:00 LOG6[9738:0]: daemon_loop: s_poll_wait: Invalid argument (22)
    1900.01.00 00:00:00 LOG6[9738:0]: daemon_loop: s_poll_wait: Invalid argument (22)
    [ . . . and forever more . . . ]

I can't imagine that this is supposed to be how debug works, since
it's totally useless for debugging if it spits out the same line as
fast as it can.

I'm running the stunnel as root, and netstat seems to show that
it's bound to port 110, but doesn't seem to indicate any outbound
connection from stunnel to our pop host after I invoke movemail.

I have no idea if versions before 4.06 work; I haven't tried.  Sure,
this is an old OS, but zillions of other things, including the entire
GNU toolchain, seem to work on it, so stunnel should, too.

Builds for all three versions I've tried may be found in at the
following URLs.  Note that 4.07 and 4.08 fail on different files,
but in essentially the same way.

http://foner.www.media.mit.edu/people/foner/Sys/stunnel-4.06.build
http://foner.www.media.mit.edu/people/foner/Sys/stunnel-4.07.build
http://foner.www.media.mit.edu/people/foner/Sys/stunnel-4.08.build

I've done some websearching, and I've searched the stunnel archives at
mirt.net, but haven't found anything relevant.

Any clues?  Thanks...