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. The vast majority of my mail passes through as expected. Yes, Stunnel is the ssl agent here, listening on port 8025 and forwarding to 7025. Firewall rules prevent direct access to port 7025. Both services bind exclusively to the IP of mail.geekisp.com.
possible problem (I'm stretching here, trying to understand the problem without full information about changes to your setup) is that when tmda-ofmipd makes a name query (it uses gethostbyaddr()) for the address 127.0.0.1, it gets an error.
Is there additional information I might provide? I wish I knew what message was passing through tmda-ofmipd when it crashed, but I will simply have to pay attention later on.
As for my dns setup, I run a stock local dns cache (dnscache) as per DJB's instructions at
http://cr.yp.to/djbdns/run-cache.html. My resolv.conf searches the hosts file first, then consults dns.
My /etc/hosts is pretty stock, the relevent line being: 127.0.0.1 localhost.geekisp.com localhost
A quick nslookup for '127.0.0.1' returns 'localhost'.
sudo -u vpopmail sh -c 'PATH=$PATH:/usr/local/bin /usr/local/bin/tmda-ofmipd -u vpopmail -p mail.geekisp.com:7025 -R imap://mail.geekisp.com -S /usr/local/tmda/contrib/vpopmail-vdir.sh >> /var/log/tmda-ofmipd.log 2>&1 '
You don't need (and shouldn't use) the -u flag when running tmda-ofmipd from sudo as the user 'vpopmail'. I don't think that's the cause of the above problem, though.
Ah, thanks, quite right. No sense in making it redundant!
I've got SSL managing the connection on port 8025, hooking it into port 7025. Everything else is pretty much stock. TMDA version 0.83.
This is what makes me curious about your name resolver setup.
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)?
Thanks for the reply!
Regards, -- Dave Steinberg http://www.geekisp.com _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
