[Project_owners] Mozdev mailing list out of order: "Recipient address rejected"
godmar at gmail.com
Wed Feb 27 12:54:34 PST 2013
Hi, our mailing list (libx at mozdev.org) is out of order - it says "Recipient
Could someone check what's going on?
---------- Forwarded message ----------
From: Mail Delivery Subsystem <mailer-daemon at googlemail.com>
Date: Wed, Feb 27, 2013 at 3:39 PM
Subject: Delivery Status Notification (Failure)
To: godmar at gmail.com
Delivery to the following recipient failed permanently:
libx at mozdev.org
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for
the recipient domain mozdev.org by mozdev.mozdev.org. [126.96.36.199].
The error that the other server returned was:
550 5.1.1 <libx at mozdev.org>: Recipient address rejected: User unknown in
local recipient table
----- Original message -----
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
X-Received: by 10.50.88.129 with SMTP id bg1mr1862059igb.33.1361997586948;
Wed, 27 Feb 2013 12:39:46 -0800 (PST)
Received: by 10.64.147.37 with HTTP; Wed, 27 Feb 2013 12:39:46 -0800 (PST)
Date: Wed, 27 Feb 2013 15:39:46 -0500
CAB4+JY+k14QxDC5Tntux_x+9ywupTCHrSEq7rRsH0CmMxTpvsg at mail.gmail.com>
Subject: LibX and Summon
From: Godmar Back <godmar at gmail.com>
To: "libx at mozdev.org" <libx at mozdev.org>
Content-Type: multipart/alternative; boundary=e89a8f234e7b5b38c204d6bac69d
Anand Swaminathan implemented two very nice facilities for LibX editions
that include Summon in their configuration.
They are described on our blog: http://libx.org/libx-blog/ specifically:
We would like your feedback and suggestions for these services. We think
they're really cool.
We checked the existing LibX edition configurations, and found a fair
number of them that include Summon. However, unfortunately, few of them
include Summon as their primary catalog, which is a prerequisite to
benefiting from these services.
We are putting all this effort into supporting Summon for a couple of
reasons. First, we have Summon at Virginia Tech. Second, to our knowledge,
Summon is the only major vendor that openly documents their APIs and access
points and does not require any NDA to create implementations that interact
However, even Summon has different service points with different levels of
services. The highest level of service can be obtained from the Summon API,
which we know some of you are using for other applications. We created a
PhP proxy for LibX that you must install if you wish to use the Summon API,
Fortunately, Summon also provides a slightly lesser service, which does not
require any API access, via its 'Summon Search Widget' facility. LibX
supports this service as well, and does so without requiring you to obtain
an API key or running your own proxy.
Please share your feedback as well as ideas on how to extend these services!
- Godmar & Anand
ps: also, if you feel that we are overly restrictive in requiring Summon to
be the primary catalog, let us know. Our rationale is that the link should
go to the same place as the tooltip. Generally, most libraries import their
entire print catalog into Summon, so there's really little need to directly
search the print catalog - but local considerations
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Project_owners