[exim] Fixing IPV6 network is unreachable error messages

Page principale
Supprimer ce message
Répondre à ce message
Auteur: Thomas Leavitt
Date:  
À: exim-users
Sujet: [exim] Fixing IPV6 network is unreachable error messages
Server host OS: Ubuntu 12.04.02 LTS

exim4 --version
Exim version 4.76 #1 built 25-Oct-2012 14:24:33
Copyright (c) University of Cambridge, 1995 - 2007
Berkeley DB: Berkeley DB 5.1.25: (January 28, 2011)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated

ii  exim4
4.76-3ubuntu3.1                metapackage to ease Exim MTA (v4)
installation
ii  exim4-base
4.76-3ubuntu3.1                support files for all Exim MTA (v4) packages
ii  exim4-config
4.76-3ubuntu3.1                configuration for the Exim MTA (v4)
ii  exim4-daemon-light
4.76-3ubuntu3.1                lightweight Exim MTA (v4) daemon


split_config='false'

My server logs are flooded with messages like this:

2013-03-29 08:03:34 1ULaq6-0002Zl-9J
gmail-smtp-in.l.google.com[2607:f8b0:400e:c01::1b] Network is
unreachable

When I add either this: disable_ipv6, or dns_ipv4_lookup, I get "not found".
usr/sbin/update-exim4.conf: 33: /etc/exim4/update-exim4.conf.conf:
disable_ipv6: not found

I've dug through Google thoroughly, and don't see any reference to this,
nor do I see any instructions in the Exim4 documentation or on the wiki.
I'm not an expert at Exim4 by any means... I'm guessing that there's some
stanzas in a template somewhere that are missing that refer to this? Do
they need to be added to the exim4.conf.template file?

... as I wrote this, I did one final Google search and located a forum
thread from 2005 that says simply delete any IPv6 addresses from the
"dc_local_interfaces" line... and discussed this whole not very obvious
issue in detail.

Thomas