-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Using tmda-ofmipd seems to introduce an unusually large delay in sending (about 5 seconds).
Whilst just about tolerable I decided to see if something was wrong, bumped up logging & sent a test message. Logging showed some unexpected DNS queries (AAAA queries). But my curiousity was tweaked. I see "hostname.FQDN. AAAA" then "hostname AAAA" (or for other stuff 'localhost.fqdn AAAA' and then 'localhost AAAA') from DNS logging, these go if I switch to authenticating against "imap://127.0.0.1:143", so I know it is ofmipd issuing the queries. I don't understand why it is issues AAAA queries (although I know I ought to check the BIND users archive for some tips of that relating to Redhat 7.0, and I know my resolv.conf manual page is out of date but I couldn't dig out the corrected version), and why it is doing two queries, when I would expect an "A" query for both fully qualified requests to be answered. A quick glance at the code did nothing to enlighten me, tmda calls IMAP4, IMAP4 calls socket.socket, and socket.socket issues a AF_INET socket open. Is there some deep Python or Linux oddity going on here? I use hosts before DNS, and hosts should answer both A queries. I really ought to understand exactly what is happening here, sometime not knowing how something you thought you understood works is worse than not having the slightest clue. I guess some fumbling over names and ports could be to blaim for the delay, but mosly my curiosity is raised. What exactly is happening, or is some the the code doing some sort of check for existence that I missed in my reading of it. Simon -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+FMHaGFXfHI9FVgYRAkuzAJ4twUM7XPzJBqmLQQcbwYvTuVj9MACcDtgM h7/UZCPpgAZCLJz7d0EN9Yk= =0bKx -----END PGP SIGNATURE----- _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
