Re: Can't connect from non-localhost under Mac OS X 10.5.3?

Shay Telfer <[email protected]> Tue, 17 Jun 2008 23:33:31 +0800
Newsgroups gmane.mail.qpopper
Message-ID <[email protected]>
Randall Gellens wrote:
>  At 5:02 PM +0800 6/12/08, Shay Telfer wrote:
>
>>   Hi...
>>
>>   I've compiled qpopper 4.1b9 under Mac OS X 10.5.3 (Leopard).
>>
>>   I can connect to the server fine from localhost:
>>
>>>>     telnet localhost 110
>>>    Trying ::1...
>>>    telnet: connect to address ::1: Connection refused
>>>    Trying fe80::1...
>>>    telnet: connect to address fe80::1: Connection refused
>>>    Trying 127.0.0.1...
>>>    Connected to localhost.
>>>    Escape character is '^]'.
>>>    +OK Qpopper (version 4.1b9) at botrytis-local.local starting.
>>>    QUIT
>>>    +OK Pop server at botrytis-local.local signing off.
>>>    Connection closed by foreign host.
>>
>>   However, attempting the same from a different machine on the 
>>local network gives:
>>
>>>>     telnet 192.168.0.12 110
>>>    Trying 192.168.0.12...
>>>    telnet: connect to address 192.168.0.12: Connection refused
>>>    telnet: Unable to connect to remote host
>>
>>   I'm thinking the problem might be IPv6 related?
>>
>>   qpopper is being launched by launchd
>>
>>   Previously appfirewall.log was recording
>>
>>>    Jun  9 00:59:04 botrytis-local popper[5131]: (v4.0.8) Unable to 
>>>get canonical name of client 0.0.0.0: Unknown host (1)
>>>    Jun  9 00:59:04 botrytis-local popper[5131]: (v4.0.8) Servicing 
>>>request from "0.0.0.0" at 0.0.0.0
>>>    Jun  9 00:59:14 botrytis-local popper[5131]: (v4.0.8) Timing 
>>>for @0.0.0.0 (normal) auth=0 init=0 clean=0
>>
>>   however I'm now running qpopper with '-R' to not require reverse 
>>lookup, but the problem still persists
>>
>>   The firewall configuration seems to be ok:
>>>>   ipfw list
>>>   65535 allow ip from any to any
>>
>>   Any suggestions appreciated. There doesn't seem to be anything 
>>useful in the logfiles that I can see.
>>
>>   Same problem occurs with version 4.0.8
>
>  What if you disable the firewall, just to see if that fixes it?

The same thing happens when the firewall is disabled (ipfw disable firewall)

Even with an explicitly granted rule (00100 allow ip from any to any 
dst-port 110) only localhost can connect.

Thanks,
Shay
-- 
=========================== Shay  Telfer ================================
  Perth, Western Australia   Technomancer  The love of liberty is the love
  Opinions for hire              [POQ]     of others; the love of power is
  http://newtonslore.com/        fnord     the love of ourselves - Hazlitt