Journal Journal: Qmail apparently doesn't like Nolisting 1
My homebrew club's new vice-president needed to create an account on our TWiki to keep up with officer-type stuff. By default, if Net::SMTP is installed as part of your Perl configuration, it'll use that (TWiki is written mostly in Perl IIRC). If it can't find that, it'll call whatever sendmail-compatible program you specify. With TWiki using Net::SMTP and nolisting set up, TWiki was no longer able to send its new-user messages. It bitched about some sort of DNS error. Reconfiguring TWiki to use the sendmail wrapper instead got it working.
I also had some weirdness sending mail through alfter.us around the same time as I was testing these problems. Cox's SMTP server was acting up, so I opened an SSH tunnel from my Mac mini to alfter.us, with port 2525 on the Mac redirected to port 25 on alfter.us. When I tried sending mail from Thunderbird through the tunnel, I got DNS errors again (similar to what TWiki was generating). When I got rid of nolisting, those problems went away. With nolisting gone, I was also able to switch TWiki back to using Net::SMTP, and it works as it did before.
At first, I was going to attribute this problem to Net::SMTP as that's where I first noticed it. Now that I've thought about it a little more, it seems that maybe qmail is to blame. Net::SMTP wasn't in the loop when I was trying to send mail from home; that was Thunderbird (Mac) -> OpenSSH (Mac) -> OpenSSH (Linux) -> qmail (Linux). qmail has generally been well-behaved IME, but why would setting an intentionally-broken MX record cause it to spaz out like this? qmail-smtpd shouldn't care about its own MX records one way or the other; it should only be interested in other servers' records.