Dave Steinberg <[EMAIL PROTECTED]> writes: > >> error: uncaptured python exception, closing channel > >> <__main__.VDomainProxy listening mail.geekisp.com:7025 at 0x10390c> > >> (socket.error:(22, 'Invalid argument') > >> [/usr/ports/lang/python/2.2/w-python-2.2.1p1/fake-i386/usr/local/lib/ > >> python2.2/asyncore.py|poll|95] > >> [/usr/ports/lang/python/2.2/w-python-2.2.1p1/fake-i386/usr/local/lib/ > >> python2.2/asyncore.py|handle_read_event|386] > >> [/usr/local/bin/tmda-ofmipd|handle_accept|1026] > >> [/usr/local/bin/tmda-ofmipd|__init__|633]) > >> > >> > >> And was hoping someone might know if I goofed something along the way. > >> I'm also not sure what I did to invoke it. Generally tmda-ofmipd has > >> been stable for me. > > > > Is the SSL port-forwarding a new thing? Are you using stunnel? One > > Not particularly new, I've been running this setup since (at least) > version 0.79.
Well, I'm still fishing. A nutshell description of the problem: Once a TCP connection is made, tmda-ofmipd creates an object to handle that particular connection (more than one client can be connected to tmda-ofmipd at a time). This failure is occuring during the initialization of that object, before tmda-ofmipd has even sent the EHLO to the client. It appears to be happening in code that asks for the IP address of the socket. Milliseconds before, the same query was made in a different place in the code (line 1023) and no error occurs. Yet when it's made on line 633, it fails. Is it possible that the client is dropping the connection? > One small comment: > > Why would tmda-ofmipd lookup localhost or 127.0.0.1 if I've bound it > to mail.geekisp.com (which it succeeds in looking up and binding to)? I was looking at the previous line (line 632) and wondering if the real problem was there. That code asks for the fully qualified domain name of the client. Because stunnel makes every connection look as if it's coming from localhost, I wondered if that could be a problem. I don't think that line 632 is the real problem, though. I believe that the system call 'getsockname' is failing. The only "invalid argument" I can possibly see would be the socket, if it had closed. I'm afraid I can't narrow it down any more than that. If you can start tmda-ofmipd with the -d switch, perhaps we can determine from the log if it's always the same client, or at least spot something suspicious. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
