[Date Prev][Date Next]
Slow Email Devliery, Was: ldaprc with ldaps:// and ldap:// fallback
Apologies for the list clutter, but I couldn't find a more appropriate
place to send this.
I originally sent this question to firstname.lastname@example.org, which is
as the contact for list problems, but that address was rejected with:
<email@example.com>: host www.openldap.org[188.8.131.52] said: 550
5.1.2 <firstname.lastname@example.org>... Rejected; bad system address (in reply
to RCPT TO command)
My original question was:
I've noticed that my emails to the openldap-technical list are delayed.
Typically the email is delayed from 30 minutes to an hour or two.
However, this email I sent yesterday was delayed for 16 hours. In all
cases, the delay appears to happen internally within boole.openldap.org.
Could this be due to a reputation issue with my relay server
(pinky.olp.net)? Or is this just moderation delay?
Here's a header snippet from the email in question:
Received: from psmtp.com (exprod5mx267.postini.com [184.108.40.206]) by
neo.olp.net (Postfix) with ESMTP id 8E23420EDC1 for <email@example.com>; Fri,
25 Jun 2010 08:56:28 -0500 (CDT)
Received: from source ([220.127.116.11]) (using TLSv1) by
exprod5mx267.postini.com ([18.104.22.168]) with SMTP; Fri, 25 Jun 2010
Received: from boole.openldap.org (mailman@localhost [IPv6:::1]) by
boole.openldap.org (8.14.3/8.14.3) with ESMTP id o5PDj7QP064017 for
<firstname.lastname@example.org>; Fri, 25 Jun 2010 13:56:20 GMT (envelope-from
Received: from pinky.olp.net (email@example.com [22.214.171.124]) by
boole.openldap.org (8.14.3/8.14.3) with ESMTP id o5OLriEj067106 for
<firstname.lastname@example.org>; Thu, 24 Jun 2010 21:54:08 GMT
Received: from quark.olp.net (vpn.olp.net [126.96.36.199]) by
pinky.olp.net (Postfix) with ESMTP id 378C0292E8E; Thu, 24 Jun 2010
16:53:42 -0500 (CDT)
Received: by quark.olp.net (Postfix, from userid 1000) id 1EFE6E7E002; Thu,
24 Jun 2010 16:53:40 -0500 (CDT)
On 24/06/10 16:53 -0500, Dan White wrote:
On 24/06/10 22:13 +0200, Emmanuel Dreyfus wrote:
Dan White <email@example.com> wrote:
You could do SASL EXTERNAL over both, with ldapi:/// using Unix peercred,
That sounds nice, but will it works with the "TLS_REQCERT demand" I have
for ldaps:// ?
In this case, EXTERNAL should only be offered after successful TLS
negotiation, or over a unix domain socket.
If TLS negotiation fails, then a SASL bind won't work without selecting