Matt Sergeant wrote:
mark warren bracher wrote:
any thoughts? since it's the same config and the same process
listening on multiple network interfaces, I'm a bit stumped about why
it behaves differently on one than it does on the others......
The core check_early_talker will make it hang forever probably. Make
sure you use the async one.
yep, using async/check_early_talker.
and it doesn't so much _hang_. the server is responsive. I can type in
'mail from:' and 'rcpt to:' lines and send a mail. and connections on
other interfaces get the 220 line, even as a connection on the external
interface is sitting and waiting for it.
it just never prints the 220 greeting line to connections on eth1, but
it will for connections on other network interfaces.
running with that theme though, I started commenting out non-essential
plugins, one at a time and testing the connection. the problem
continued until I commented out
async/dnsbl disconnect
which makes sense, now that I think about it, since the ip/mask for each
of the other interfaces is in config/dnsbl_allow. the external
interface is the only one that dnsbl is going to run for.
I then added everything else back in one by one, to make sure it wasn't
a weird interaction between plugins. at this point I'm back to my
original config, minus async/dnsbl. and I get 220 greeting lines on all
interfaces. now I need to dig and and figure out where in that plugin
things are getting hung up...
looking at the log (with async/dnsbl enabled), async::dnsbl is running,
and all the dns queries are returning
15705 running plugin (connect): async::dnsbl
15705 trying to get config for dnsbl_allow
15705 trying to get config for dnsbl_zones
15705 async::dnsbl plugin: Checking 5.55.104.209.zen.spamhaus.org for
TXT record in the background
15705 async::dnsbl plugin: Checking 5.55.104.209.spamsources.fabel.dk
for TXT record in the background
15705 Result for TXT 5.55.104.209.zen.spamhaus.org: NXDOMAIN
15705 Finished (1)
15705 Result for TXT 5.55.104.209.spamsources.fabel.dk: NXDOMAIN
15705 Finished (0)
but it never moves past this point...
- mark
