[Zope-PTK] Broken feed from the zope-ptk list
Ken Manheimer
klm@digicool.com
Wed, 28 Feb 2001 16:48:12 -0500 (EST)
We're getting bounces for postings to the zope-ptk@zope.org list from
majordomo@wwc.edu. Unfortunately, it looks like the deliveries to
majordomo@wwc.edu are indirect - there's no immediate zope-ptk subscribers
from wwc.edu - and we have no clues about how to track down how it's being
forwarded there. This message has two purposes - to see if anyone has any
clues about the subscription that's feeing to the wwc.edu address (so we
can disable it), and to ask the maintainer of the majordomo install at
wwc.edu to check whether their majordomo install is broken. It's treating
many if not all messages from our list as admin messages - or perhaps
someone is directing the traffic straight at "majordomo@wwc.edu", which i
guess lead to these error notices, sigh.
Any clues out there?
Ken
klm@digicool.com
---------- Forwarded message ----------
Return-Path: <Majordomo-Owner@wwc.edu>
Received: from ns2.digicool.com ([216.164.72.2] verified)
by digicool.com (CommuniGate Pro SMTP 3.4)
with ESMTP id 1627338 for klm@mail.digicool.com; Tue,
27 Feb 2001 19:03:59 -0500
Received: from saturn.wwc.edu (IDENT:postfix@saturn.wwc.edu [199.236.178.1])
by ns2.digicool.com (8.9.3/8.9.3) with ESMTP id TAA19985
for <klm@digicool.com>; Tue, 27 Feb 2001 19:01:36 -0500
Received: by saturn.wwc.edu (Postfix, from userid 91)
id 2628C70095; Tue, 27 Feb 2001 16:01:36 -0800 (PST)
To: klm@digicool.com
From: Majordomo@wwc.edu
Subject: Majordomo results: Re: [Zope-PTK] Workflow architecture pro
Reply-To: Majordomo@wwc.edu
Message-Id: <20010228000136.2628C70095@saturn.wwc.edu>
Date: Tue, 27 Feb 2001 16:01:36 -0800 (PST)
Sender: Majordomo-Owner@wwc.edu
--
>>>> On Tue, 27 Feb 2001, Shane Hathaway wrote:
**** Command 'on' not recognized.
>>>>
>>>> > I have finished updating the proposal for the new workflow
**** Command '>' not recognized.
>>>> > architecture. You can find it here:
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > http://cmf.zope.org/Members/hathawsh/workflow_proposal
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > Please ask questions. I may not have articulated some of the rationale
**** Command '>' not recognized.
>>>> > and details behind certain decisions and I want to make sure we're
**** Command '>' not recognized.
>>>> > really addressing workflow properly.
**** Command '>' not recognized.
>>>> >
**** Command '>' not recognized.
>>>> > I have also integrated an implementation of these interfaces into the
**** Command '>' not recognized.
>>>> > CMF which I'm about to check in, though I'm not sure the current sources
**** Command '>' not recognized.
>>>> > are being echoed to the public CVS server.
**** Command '>' not recognized.
>>>>
>>>> They are supposed to be - let me know if you're seeing gaps.
**** Command 'they' not recognized.
>>>>
>>>> Ken
**** Command 'ken' not recognized.
>>>> klm@digicool.com
**** Command 'klm@digicool.com' not recognized.
>>>>
>>>>
>>>> _______________________________________________
**** Command '_______________________________________________' not recognized.
>>>> Zope-PTK maillist - Zope-PTK@zope.org
**** Command 'zope-ptk' not recognized.
>>>> http://lists.zope.org/mailman/listinfo/zope-ptk
**** Command 'http://lists.zope.org/mailman/listinfo/zope-ptk' not recognized.
>>>>
>>>> See http://www.zope.org/Products/PTK/Tracker for bug reports and feature requests
**** Command 'see' not recognized.
>>>>
**** No valid commands found.
**** Commands must be in message BODY, not in HEADER.
**** Help for Majordomo@wwc.edu:
This help message is being sent to you from the Majordomo mailing list
management system at Majordomo@wwc.edu.
This is version 1.94.4 of Majordomo.
If you're familiar with mail servers, an advanced user's summary of
Majordomo's commands appears at the end of this message.
Majordomo is an automated system which allows users to subscribe
and unsubscribe to mailing lists, and to retrieve files from list
archives.
You can interact with the Majordomo software by sending it commands
in the body of mail messages addressed to "Majordomo@wwc.edu".
Please do not put your commands on the subject line; Majordomo does
not process commands in the subject line.
You may put multiple Majordomo commands in the same mail message.
Put each command on a line by itself.
If you use a "signature block" at the end of your mail, Majordomo may
mistakenly believe each line of your message is a command; you will
then receive spurious error messages. To keep this from happening,
either put a line starting with a hyphen ("-") before your signature,
or put a line with just the word
end
on it in the same place. This will stop the Majordomo software from
processing your signature as bad commands.
Here are some of the things you can do using Majordomo:
I. FINDING OUT WHICH LISTS ARE ON THIS SYSTEM
To get a list of publicly-available mailing lists on this system, put the
following line in the body of your mail message to Majordomo@wwc.edu:
lists
Each line will contain the name of a mailing list and a brief description
of the list.
To get more information about a particular list, use the "info" command,
supplying the name of the list. For example, if the name of the list
about which you wish information is "demo-list", you would put the line
info demo-list
in the body of the mail message.
II. SUBSCRIBING TO A LIST
Once you've determined that you wish to subscribe to one or more lists on
this system, you can send commands to Majordomo to have it add you to the
list, so you can begin receiving mailings.
To receive list mail at the address from which you're sending your mail,
simply say "subscribe" followed by the list's name:
subscribe demo-list
If for some reason you wish to have the mailings go to a different address
(a friend's address, a specific other system on which you have an account,
or an address which is more correct than the one that automatically appears
in the "From:" header on the mail you send), you would add that address to
the command. For instance, if you're sending a request from your work
account, but wish to receive "demo-list" mail at your personal account
(for which we will use "jqpublic@my-isp.com" as an example), you'd put
the line
subscribe demo-list jqpublic@my-isp.com
in the mail message body.
Based on configuration decisions made by the list owners, you may be added
to the mailing list automatically. You may also receive notification
that an authorization key is required for subscription. Another message
will be sent to the address to be subscribed (which may or may not be the
same as yours) containing the key, and directing the user to send a
command found in that message back to Majordomo@wwc.edu. (This can be
a bit of extra hassle, but it helps keep you from being swamped in extra
email by someone who forged requests from your address.) You may also
get a message that your subscription is being forwarded to the list owner
for approval; some lists have waiting lists, or policies about who may
subscribe. If your request is forwarded for approval, the list owner
should contact you soon after your request.
Upon subscribing, you should receive an introductory message, containing
list policies and features. Save this message for future reference; it
will also contain exact directions for unsubscribing. If you lose the
intro mail and would like another copy of the policies, send this message
to Majordomo@wwc.edu:
intro demo-list
(substituting, of course, the real name of your list for "demo-list").
III. UNSUBSCRIBING FROM MAILING LISTS
Your original intro message contains the exact command which should be
used to remove your address from the list. However, in most cases, you
may simply send the command "unsubscribe" followed by the list name:
unsubscribe demo-list
(This command may fail if your provider has changed the way your
address is shown in your mail.)
To remove an address other than the one from which you're sending
the request, give that address in the command:
unsubscribe demo-list jqpublic@my-isp.com
In either of these cases, you can tell Majordomo@wwc.edu to remove
the address in question from all lists on this server by using "*"
in place of the list name:
unsubscribe *
unsubscribe * jqpublic@my-isp.com
IV. FINDING THE LISTS TO WHICH AN ADDRESS IS SUBSCRIBED
To find the lists to which your address is subscribed, send this command
in the body of a mail message to Majordomo@wwc.edu:
which
You can look for other addresses, or parts of an address, by specifying
the text for which Majordomo should search. For instance, to find which
users at my-isp.com are subscribed to which lists, you might send the
command
which my-isp.com
Note that many list owners completely or fully disable the "which"
command, considering it a privacy violation.
V. FINDING OUT WHO'S SUBSCRIBED TO A LIST
To get a list of the addresses on a particular list, you may use the
"who" command, followed by the name of the list:
who demo-list
Note that many list owners allow only a list's subscribers to use the
"who" command, or disable it completely, believing it to be a privacy
violation.
VI. RETRIEVING FILES FROM A LIST'S ARCHIVES
Many list owners keep archives of files associated with a list. These
may include:
- back issues of the list
- help files, user profiles, and other documents associated with the list
- daily, monthly, or yearly archives for the list
To find out if a list has any files associated with it, use the "index"
command:
index demo-list
If you see files in which you're interested, you may retrieve them by
using the "get" command and specifying the list name and archive filename.
For instance, to retrieve the files called "profile.form" (presumably a
form to fill out with your profile) and "demo-list.9611" (presumably the
messages posted to the list in November 1996), you would put the lines
get demo-list profile.form
get demo-list demo-list.9611
in your mail to Majordomo@wwc.edu.
VII. GETTING MORE HELP
To contact a human site manager, send mail to Majordomo-Owner@wwc.edu.
To contact the owner of a specific list, send mail to that list's
approval address, which is formed by adding "-approval" to the user-name
portion of the list's address. For instance, to contact the list owner
for demo-list@wwc.edu, you would send mail to demo-list-approval@wwc.edu.
To get another copy of this help message, send mail to Majordomo@wwc.edu
with a line saying
help
in the message body.
VIII. COMMAND SUMMARY FOR ADVANCED USERS
In the description below items contained in []'s are optional. When
providing the item, do not include the []'s around it. Items in angle
brackets, such as <address>, are meta-symbols that should be replaced
by appropriate text without the angle brackets.
It understands the following commands:
subscribe <list> [<address>]
Subscribe yourself (or <address> if specified) to the named <list>.
unsubscribe <list> [<address>]
Unsubscribe yourself (or <address> if specified) from the named <list>.
"unsubscribe *" will remove you (or <address>) from all lists. This
_may not_ work if you have subscribed using multiple addresses.
get <list> <filename>
Get a file related to <list>.
index <list>
Return an index of files you can "get" for <list>.
which [<address>]
Find out which lists you (or <address> if specified) are on.
who <list>
Find out who is on the named <list>.
info <list>
Retrieve the general introductory information for the named <list>.
intro <list>
Retrieve the introductory message sent to new users. Non-subscribers
may not be able to retrieve this.
lists
Show the lists served by this Majordomo server.
help
Retrieve this message.
end
Stop processing commands (useful if your mailer adds a signature).
Commands should be sent in the body of an email message to
"Majordomo@wwc.edu". Multiple commands can be processed provided
each occurs on a separate line.
Commands in the "Subject:" line are NOT processed.
If you have any questions or problems, please contact
"Majordomo-Owner@wwc.edu".