Your message dated Wed, 22 Feb 2006 03:47:07 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#342619: fixed in exim4 4.60-4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: exim4-daemon-heavy
Version: 4.50-8
Severity: serious
On Thu, Dec 08, 2005 at 10:33:54PM +0100, Florian Weimer wrote:
> * Lionel Elie Mamane:
>
> > On Thu, Dec 08, 2005 at 09:30:52PM +0100, Wouter Verhelst wrote:
> >
> >> The fact that my primary MX is only available through IPv6, and that
> >> this is the case for other people who're having problems too might
> >> then be a better chance at being the problem.
> >
> > My primary MX is IPv6-only, too. I don't have detected a problem yet :)
>
> Do you receive lots of mail from master.debian.org, and would you
> notice the bounces? Mail from Debian mailing lists come directly from
> murphy.debian.org, which does not seem to have the problem.
>
> You also have one IPv4-only MX, which might be enough to prevent the
> Exim bug[1] from occurring.
>
> [1] I'm not sure if it's a Exim's fault, it's only a hunch.
I'm quite sure it's an exim bug, but haven't quite nailed it yet. The
bug has been witnessed positively both on master.d.o and on
one mailserver I maintain. Interestingly, it doesn't seem to be IPv6
related (or maybe there are two bugs).
The situation on my mailserver was that the primary MX had a long term
unavailability and was way past cutoff time, but the secondary MX worked
fine. However, for some reason, what suddenly happened was that all the
mail queued for the domain in question got bounced for reason of having
a extended time of being unreacheable, past the retry time. Obviously,
that's bogus, as the secundary MX wasn't past cutoff yet.
I've meant to look into the code for this, but didn't yet get around to
it. If someone wants to do so, please -- I seriously suspect that Exim
in Sarge has a serious bug in there somewhere, it's showing up with this
IPv6 and IPv4 multihomed MX's too, after all.
I think this is a serious bug, as it can cause mail to get lost
(bouncing a mail for no good reason at all in some very common
situations like the IPv6 vs IPv4 multimhomed MX's)
Log snippets:
# Primary (long time unreacheable) MX is shrek.vanschaik.tk, secundary
# reacheable MX is mailrelay.direct-adsl.nl
Last succesful delivery:
2005-11-30 17:49:53 1EhV6R-0000uq-Qg shrek.vanschaik.tk [81.207.193.3]:
Connection timed out
2005-11-30 17:50:02 1EhV6R-0000uq-Qg => [EMAIL PROTECTED]
<[EMAIL PROTECTED]> R=dnslookup_relay_to_domains T=remote_smtp
H=mailrelay.direct-adsl.nl [195.121.6.56] C="250 2.0.0 jAUGo2wm025502
Message accepted for delivery" QT=3m19s
First failure:
2005-11-30 18:35:41 1EhVnA-0002GK-L1 shrek.vanschaik.tk [81.207.193.3]:
No route to host
2005-11-30 18:35:41 1EhVnA-0002GK-L1 == [EMAIL PROTECTED]
<[EMAIL PROTECTED]> R=dnslookup_relay_to_domains T=remote_smtp defer
(113): No route to host
2005-11-30 18:35:41 1EhVnA-0002GK-L1 ** [EMAIL PROTECTED]
<[EMAIL PROTECTED]>: retry timeout exceeded
Second failure:
2005-11-30 18:36:43 1EhVrp-0001pB-Jw ** [EMAIL PROTECTED]
<[EMAIL PROTECTED]> R=dnslookup_relay_to_domains T=remote_smtp:
retry time not reached for any host after a long failure period
Obviously, the secundary MX was okay, so retry timeout exceeded and
especially the second failure should not have happened.
--Jeroen
--
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl
--- End Message ---
--- Begin Message ---
Source: exim4
Source-Version: 4.60-4
We believe that the bug you reported is fixed in the latest version of
exim4, which is due to be installed in the Debian FTP archive:
exim4-base_4.60-4_i386.deb
to pool/main/e/exim4/exim4-base_4.60-4_i386.deb
exim4-config_4.60-4_all.deb
to pool/main/e/exim4/exim4-config_4.60-4_all.deb
exim4-daemon-heavy_4.60-4_i386.deb
to pool/main/e/exim4/exim4-daemon-heavy_4.60-4_i386.deb
exim4-daemon-light_4.60-4_i386.deb
to pool/main/e/exim4/exim4-daemon-light_4.60-4_i386.deb
exim4_4.60-4.diff.gz
to pool/main/e/exim4/exim4_4.60-4.diff.gz
exim4_4.60-4.dsc
to pool/main/e/exim4/exim4_4.60-4.dsc
exim4_4.60-4_all.deb
to pool/main/e/exim4/exim4_4.60-4_all.deb
eximon4_4.60-4_i386.deb
to pool/main/e/exim4/eximon4_4.60-4_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marc Haber <[EMAIL PROTECTED]> (supplier of updated exim4 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 22 Feb 2006 10:30:16 +0000
Source: exim4
Binary: eximon4 exim4-daemon-custom exim4-daemon-heavy exim4-base exim4
exim4-daemon-light exim4-config
Architecture: source i386 all
Version: 4.60-4
Distribution: unstable
Urgency: low
Maintainer: Exim4 Maintainers <[EMAIL PROTECTED]>
Changed-By: Marc Haber <[EMAIL PROTECTED]>
Description:
exim4 - metapackage to ease exim MTA (v4) installation
exim4-base - support files for all exim MTA (v4) packages
exim4-config - configuration for the exim MTA (v4)
exim4-daemon-heavy - exim MTA (v4) daemon with extended features, including
exiscan-ac
exim4-daemon-light - lightweight exim MTA (v4) daemon
eximon4 - monitor application for the exim MTA (v4) (X11 interface)
Closes: 342619
Changes:
exim4 (4.60-4) unstable; urgency=low
.
* add rationale to README.Debian explaining why using system
passwords for SMTP AUTH is a bad idea.
* streamline configuration to decrease differences to upstream default
example, and to adopt new things that were added since we last
looked there.
* Do not set inst_aliases for installation, this only affects
example.conf anyway.
* fail build if upstream's example configuration has changed.
* fix NEWS confusion. Thanks to Andreas for spotting this.
* exim4-base.exim4.init: invoke exim4 daemon with the environment
cleaned to avoid language confusion.
* document tls on connect in README.Debian.
* use adduser --quiet instead of > /dev/null in *.postinst.
* Add require_files directive to userforward router to avoid errors
when mailing [EMAIL PROTECTED]
* Add comment about setting up TLS in conf.d/auth/30_exim4-config_examples
to keep people from blindly allowing cleartext auth.
* Replace 37_dns_disable_additional_section patch with
37_upstream_patch_342619, which is the nearly identical patch from
upstream CVS, approved by Philip. (mh) Closes: #342619
Files:
15e67edef7599d51bb485ea3b89df810 1044 mail standard exim4_4.60-4.dsc
e21f380b10ab85ad2ca83c94eb597022 328742 mail standard exim4_4.60-4.diff.gz
c6aa04b110079c6d3b51df6933f26464 874938 mail standard
exim4-base_4.60-4_i386.deb
fa702543806f4dc83209ba3e701ed89c 392892 mail standard
exim4-daemon-light_4.60-4_i386.deb
467016a016bed4d3a637230e276fa957 83138 mail optional eximon4_4.60-4_i386.deb
5284b89edd4fca92c4cb4ec0ee8f855b 445188 mail optional
exim4-daemon-heavy_4.60-4_i386.deb
e50a410d4165c4f4a24fe31001ab4c1e 263966 mail standard
exim4-config_4.60-4_all.deb
ba5d649c6825b0e6d55d7166c89804e7 1572 mail standard exim4_4.60-4_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD/Eu4gZalRGu6PIQRAo2AAJ9mkteCvEwDqmYkVkrvcPtpUMSR5gCeJ/zw
6UwjhuijeY+Pj/Fu7nc+Zuk=
=lgtx
-----END PGP SIGNATURE-----
--- End Message ---
