------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://www.exim.org/bugzilla/show_bug.cgi?id=451
------- Comment #1 from holmgren@lysator.liu.se 2007-01-23 02:16 -------
I've figured it out. In this case where a bounce message is frozen (I
don't know if it has to be because the dnslookup router found that the
primary MX was the local host) and ignore_bounce_errors_after = 0s, Exim
still thinks that the message is frozen near the end of deliver.c and tries
to move it even though the routing error has been ignored, no deferred
address exists any longer, and the message therefore has been removed from
the spool.
I've attached my suggested patch, which I will commit if nobody objects. The
bug is completely harmless, so there's no need to panic.
--
Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email
--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
You are the QA contact for the bug, or are watching the QA contact.
http://www.exim.org/bugzilla/show_bug.cgi?id=451
------- Comment #1 from holmgren@lysator.liu.se 2007-01-23 02:16 -------
I've figured it out. In this case where a bounce message is frozen (I
don't know if it has to be because the dnslookup router found that the
primary MX was the local host) and ignore_bounce_errors_after = 0s, Exim
still thinks that the message is frozen near the end of deliver.c and tries
to move it even though the routing error has been ignored, no deferred
address exists any longer, and the message therefore has been removed from
the spool.
I've attached my suggested patch, which I will commit if nobody objects. The
bug is completely harmless, so there's no need to panic.
--
Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email
--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##