When you send mail to an address that no longer exists, the remote server
typically sends back some kind of "bounce" message saying the mail is
undeliverable. The software that manages a mailing list typically attempts to
filter these bounce messages so that (a) they aren't sent to all members
Hello,
is it just for me, or are members of this list getting lots of automated
mailings, too?
I just subscribed today and already got "Undeliverable Notices" from
biovigilant.com for each post I did and one "autoreply" from
cicpa.org.cn, sent to me personally.
--
Goody Bye, Minden jót, Mit
Hello Michael,
thank you for your clarification. I would prefer the catalog way, but
according to the Saxon documentation on XML catalogs it states
The catalog is NOT currently used for non-XML resources, *including
query modules*, unparsed text files, collations, and collections.
It seems,
Saxon allows you to set the static base URI when you compile a query using the
API
XQueryCompiler.setBaseURI()
The base URI doesn't have to have any particular relationship with the location
of the query source code. However, the same base URI is used for compile time
actions such as
Hello,
Since the application I am writing can be installed on other hosts, the
`base-uri` must be configurable to that foreign host. I want to solve
this with a library module, that keeps domain specific configuration
separate to the user and which gets imported where needed.
Test case:
