Majordomo results: [UBCCS:VIRUS] Was: Returned mail: Data f

Majordomo at Majordomo at
Mon Aug 1 15:04:28 CEST 2005


>>>> This is a multi-part message in MIME format...
**** Command 'this' not recognized.
>>>> ------=_NextPart_000_0009_87A2270A.AF343686
**** Command '------=_nextpart_000_0009_87a2270a.af343686' not recognized.
>>>> Content-Type: text/plain;
**** Command 'content-type:' not recognized.
>>>> 	charset=us-ascii
**** Command 'charset=us-ascii' not recognized.
>>>> Content-Transfer-Encoding: 7bit
**** Command 'content-transfer-encoding:' not recognized.
>>>> Content-Disposition: inline
**** Command 'content-disposition:' not recognized.
>>>> The message was undeliverable due to the following reason(s):
**** Command 'the' not recognized.
>>>> Your message could not be delivered because the destination server was
**** Command 'your' not recognized.
>>>> unreachable within the allowed queue period. The amount of time
**** Command 'unreachable' not recognized.
>>>> a message is queued before it is returned depends on local configura-
**** Command 'a' not recognized.
>>>> tion parameters.
**** Command 'tion' not recognized.
>>>> Most likely there is a network problem that prevented delivery, but
**** Command 'most' not recognized.
>>>> it is also possible that the computer is turned off, or does not
**** Command 'it' not recognized.
>>>> have a mail system running right now.
**** Command 'have' not recognized.
>>>> Your message was not delivered within 4 days:
**** Command 'your' not recognized.
>>>> Mail server is not responding.
**** Command 'mail' not recognized.
>>>> The following recipients did not receive this message:
**** Command 'the' not recognized.
>>>> <majordomo at>
**** Command '<majordomo at>' not recognized.
>>>> Please reply to postmaster at
**** Command 'please' not recognized.
>>>> if you feel this message to be in error.
**** Command 'if' not recognized.
>>>> ------=_NextPart_000_0009_87A2270A.AF343686
**** Command '------=_nextpart_000_0009_87a2270a.af343686' not recognized.
>>>> Content-Type: text/plain; charset=UTF-8
**** Command 'content-type:' not recognized.
>>>> Content-Transfer-Encoding: 8bit
**** Command 'content-transfer-encoding:' not recognized.
>>>> The original content of this message part has been replaced
**** Command 'the' not recognized.
>>>> by this text because it tested positive for the following
**** Command 'by' not recognized.
>>>> virus(es):
**** Command 'virus(es):' not recognized.
>>>>     W32/MyDoom-O
**** Command 'w32/mydoom-o' not recognized.
>>>> The original message has been quarantined pending further
**** Command 'the' not recognized.
>>>> action by the mail administrator.  For further information
**** Command 'action' not recognized.
>>>> about the message and its delivery status, please contact
**** Command 'about' not recognized.
>>>> the undersigned, and include the full content of this
**** Command 'the' not recognized.
>>>> message.  The identifier for this message is
**** Command 'message.' not recognized.
>>>> 'j71D4OFr001489'.
**** Command ''j71d4ofr001489'.' not recognized.
>>>> This notification is being sent to you and any other
**** Command 'this' not recognized.
>>>> original envelope recipient(s).   To avoid creating a
**** Command 'original' not recognized.
>>>> nuisance and to keep mail traffic under control, the
**** Command 'nuisance' not recognized.
>>>> original sender  of the message has NOT been notified.
**** Command 'original' not recognized.
>>>> However, you may want to notify the sender at your
**** Command 'however,' not recognized.
>>>> discretion.
**** Command 'discretion.' not recognized.
>>>> The Management
**** Command 'the' not recognized.
>>>> PureMessage Admin <postmaster at>
**** Command 'puremessage' not recognized.
>>>> ------=_NextPart_000_0009_87A2270A.AF343686
**** Command '------=_nextpart_000_0009_87a2270a.af343686' not recognized.
>>>> Content-Type: text/plain; name="SpamAssassinReport.txt"
**** Command 'content-type:' not recognized.
>>>> Content-Disposition: inline; filename="SpamAssassinReport.txt"
**** Command 'content-disposition:' not recognized.
>>>> Content-Transfer-Encoding: 7bit
**** Command 'content-transfer-encoding:' not recognized.
>>>> MIME-Version: 1.0
**** Command 'mime-version:' not recognized.
>>>> X-Mailer: MIME-tools 5.411 (Entity 5.404)
**** Command 'x-mailer:' not recognized.
>>>> Spam detection software, running on the system "", has
**** Command 'spam' not recognized.
>>>> identified this incoming email as possible spam.  The original message
**** Command 'identified' not recognized.
>>>> has been attached to this so you can view it (if it isn't spam) or block
**** Command 'has' not recognized.
>>>> similar future email.  If you have any questions, see
**** Command 'similar' not recognized.
>>>> postmaster at for details.
**** Command 'postmaster at' not recognized.
>>>> Content preview:  The message was undeliverable due to the following
**** Command 'content' not recognized.
>>>>   reason(s): Your message could not be delivered because the destination
**** Command 'reason(s):' not recognized.
>>>>   server was unreachable within the allowed queue period. The amount of
**** Command 'server' not recognized.
>>>>   time a message is queued before it is returned depends on local
**** Command 'time' not recognized.
>>>>   configura- tion parameters. [...] 
**** Command 'configura-' not recognized.
>>>> Content analysis details:   (7.5 points, 5.0 required)
**** Command 'content' not recognized.
>>>>  pts rule name              description
**** Command 'pts' not recognized.
>>>> ---- ---------------------- --------------------------------------------------
**** Command '----' not recognized.
>>>>  0.3 NO_REAL_NAME           From: does not include a real name
**** Command '0.3' not recognized.
>>>>  3.3 MSGID_FROM_MTA_SHORT   Message-Id was added by a relay
**** Command '3.3' not recognized.
>>>>  2.3 RCVD_IN_XBL            RBL: Received via a relay in Spamhaus XBL
**** Command '2.3' not recognized.
>>>>                             [ listed in]
**** Command '[' not recognized.
>>>>  1.6 FORGED_MUA_OUTLOOK     Forged mail pretending to be from MS Outlook
**** Command '1.6' not recognized.
>>>> ------=_NextPart_000_0009_87A2270A.AF343686--
**** Command '------=_nextpart_000_0009_87a2270a.af343686--' not recognized.
**** No valid commands found.
**** Commands must be in message BODY, not in HEADER.

**** Help for Majordomo at

This help message is being sent to you from the Majordomo mailing list
management system at Majordomo at

This is version 1.94.5 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

You can interact with the Majordomo software by sending it commands
in the body of mail messages addressed to "Majordomo at".
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


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:


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 at


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.


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 at" as an example), you'd put
the line

	subscribe demo-list jqpublic at

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 at  (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 at

	intro demo-list

(substituting, of course, the real name of your list for "demo-list").


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 at

In either of these cases, you can tell Majordomo at to remove
the address in question from all lists on this server by using "*"
in place of the list name:

	unsubscribe *
	unsubscribe * jqpublic at


To find the lists to which your address is subscribed, send this command
in the body of a mail message to Majordomo at


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 are subscribed to which lists, you might send the


Note that many list owners completely or fully disable the "which"
command, considering it a privacy violation.


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


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"

	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 at


To contact a human site manager, send mail to Majordomo-Owner at
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 at, you would send mail to demo-list-approval at

To get another copy of this help message, send mail to Majordomo at
with a line saying


in the message body.


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.

	Show the lists served by this Majordomo server.

	Retrieve this message.

	Stop processing commands (useful if your mailer adds a signature).

Commands should be sent in the body of an email message to
"Majordomo at". 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 at".

More information about the Python-list mailing list