#3601 fedorahosted email list temporary LDAP failure turns into permanent delivery failure
Closed: Fixed None Opened 11 years ago by mjw.

= bug description =

Just got this bounce from elfutils-devel@lists.fedorahosted.org:

[-- Attachment #1 --]
[-- Type: text/plain, Encoding: 7bit, Size: 0.5K --]

The original message was received at Wed, 19 Dec 2012 02:49:58 -0500
from int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]

----- The following addresses had permanent fatal errors -----
elfutils-devel@lists.fedorahosted.org

----- Transcript of session follows -----
451 4.3.5 Error getting LDAP results in map access: Connection timed out with
+hosted-lists01.fedoraproject.org.
451 4.3.0 Temporary system failure. Please try again later.
501 5.6.0 Data format error

Note that at first this is a temporary failure, but then it turns into a (permanent) delivery error, which makes the message to the list bounce.


Note that later messages did go to the list, so the original LDAP timeout issue seems resolved. But it is somewhat annoying that if there is such a temporary timeout that message bounce because it looks like a permanent error.

Whats even more odd is that we don't use LDAP anywhere. ;)

Can you put the entire message with headers up somewhere or attach it here?

That would let us trace where it was going...

I attached the whole bounce message as I received it (the message was intended to be public anyway).
My apologies if this wasn't because of fedoraproject.org. If it wasn't and the message gives more hints where things went wrong please let me know which system admin I should poke. Thanks.

Huh. This seems that:

int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]

returned:

451 4.3.5 Error getting LDAP results in map access: Connection timed out with hosted-lists01.fedoraproject.org.

I don't know of any outages talking to hosted-lists01, although there could well have been a network issue of some kind. It sounds like the issue was on that redhat.com host to me... it failed to get a LDAP access map and timed out.

I'd suggest punting this to redhat.com mail admins. Happy to look at anything they like from our side...

If you could file a ticket with internal folks that would be great.

Please re-open this if there is anything more we can do from our side.

Login to comment on this ticket.

Metadata