dovecot - Jan 2012 - v2.1.rc5 (85a9b5236b6c) Error: lmtp client: DNS lookup of $FQDN failed: connect(dns-client) failed: No such file or directory

When the Sieve plugin tries to send a vacation message or redirect
a message to another address it fails.

dovecot: lmtp(6412, user at example.com): Error: lmtp client: DNS lookup of
orange.example.com failed: connect(dns-client) failed: No such file or directory
dovecot: lmtp(6412, user at example.com): Error: dAIOClYSJE8MGQAAhQ0vrQ: sieve:
msgid=<4F241255.2060900 at example.com>: failed to redirect message to
<admin+user at example.com> (refer to server log for more information)

But the dns-client sockets are created when Dovecot starts up:

# find /usr/local/var/run/dovecot -name dns-client -exec ls -l {} +
srw-rw-rw- 1 root staff 0 Jan 28 16:15 /usr/local/var/run/dovecot/dns-client
srw-rw-rw- 1 root root  0 Jan 28 16:15
/usr/local/var/run/dovecot/login/dns-client

Hum, is it Dovecot or Pigeonhole (dovecot-2.1-pigeonhole 1600:b2a456e15ed5)?


Regards,
Pascal
-- 
The trapper recommends today: c01dcofe.1202816 at localdomain.org

On 28.1.2012, at 17.34, Pascal Volk wrote:
> When the Sieve plugin tries to send a vacation message or redirect
> a message to another address it fails.
> 
> dovecot: lmtp(6412, user at example.com): Error: lmtp client: DNS lookup of
orange.example.com failed: connect(dns-client) failed: No such file or directory
Fixed: http://hg.dovecot.org/dovecot-2.1/rev/bc2eea348f55
http://hg.dovecot.org/dovecot-2.1/rev/32318f1588d4

The same problem exists in v2.0 also, but I didn't bother to fix it there. A
workaround is to use IP instead of host in submission_host.