LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 06-17-2005, 01:23 AM   #1
paul_mat
Member
 
Registered: Nov 2004
Location: Townsville, Australia
Distribution: Fedora Core 5, CentOS 4, RHEL 4
Posts: 855

Rep: Reputation: 30
majordomo subscribe e-mail


hi there i'm trying to get majordomo working properly and clean but wheni get my return e-mail to say i've been accepted i get all this jibberish, can someone tell me whot ot stop it from sending all that rubbish?


--

>>>> This is a multi-part message in MIME format.
**** Command 'this' not recognized.
>>>>
>>>> ------=_NextPart_000_0085_01C57350.08249400
**** Command '------=_nextpart_000_0085_01c57350.08249400' not recognized.
>>>> Content-Type: text/plain; charset="us-ascii"
**** Command 'content-type:' not recognized.
>>>> Content-Transfer-Encoding: 7bit
**** Command 'content-transfer-encoding:' not recognized.
>>>>
>>>> Subscribe smart-board
Succeeded.
>>>>
>>>>
>>>> ------=_NextPart_000_0085_01C57350.08249400
**** Command '------=_nextpart_000_0085_01c57350.08249400' not recognized.
>>>> Content-Type: text/html; charset="us-ascii"
**** Command 'content-type:' not recognized.
>>>> Content-Transfer-Encoding: quoted-printable
**** Command 'content-transfer-encoding:' not recognized.
>>>>
>>>> <html xmlns=3D"urn:schemas-microsoft-comfficeffice" =
**** Command '<html' not recognized.
>>>> xmlns:w=3D"urn:schemas-microsoft-comffice:word" =
**** Command 'xmlns:w=3d"urn:schemas-microsoft-comffice:word"' not recognized.
>>>> xmlns=3D"http://www.w3.org/TR/REC-html40">
**** Command 'xmlns=3d"http://www.w3.org/tr/rec-html40">' not recognized.
>>>>
>>>> <head>
**** Command '<head>' not recognized.
>>>> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
**** Command '<meta' not recognized.
>>>> charset=3Dus-ascii">
**** Command 'charset=3dus-ascii">' not recognized.
>>>> <meta name=3DGenerator content=3D"Microsoft Word 11 (filtered
>>>> medium)">
**** Command '<meta' not recognized.
>>>> <style>
**** Command '<style>' not recognized.
>>>> <!--
**** Command '<!--' not recognized.
>>>> /* Style Definitions */
**** Command '/*' not recognized.
>>>> p.MsoNormal, li.MsoNormal, div.MsoNormal
**** Command 'p.msonormal,' not recognized.
>>>> {margin:0cm;
**** Command '{margin:0cm;' not recognized.
>>>> margin-bottom:.0001pt;
**** Command 'margin-bottom:.0001pt;' not recognized.
>>>> font-size:12.0pt;
**** Command 'font-size:12.0pt;' not recognized.
>>>> font-family:"Times New Roman";}
**** Command 'font-family:"times' not recognized.
>>>> a:link, span.MsoHyperlink
**** Command 'a:link,' not recognized.
>>>> {color:blue;
**** Command '{color:blue;' not recognized.
>>>> text-decoration:underline;}
**** Command 'text-decoration:underline;}' not recognized.
>>>> a:visited, span.MsoHyperlinkFollowed
**** Command 'a:visited,' not recognized.
>>>> {color:#606420;
**** Command '{color:#606420;' not recognized.
>>>> text-decoration:underline;}
**** Command 'text-decoration:underline;}' not recognized.
>>>> span.EmailStyle17
**** Command 'span.emailstyle17' not recognized.
>>>> {mso-style-typeersonal-compose;
**** Command '{mso-style-typeersonal-compose;' not recognized.
>>>> font-family:Arial;
**** Command 'font-family:arial;' not recognized.
>>>> color:windowtext;}
**** Command 'color:windowtext;}' not recognized.
>>>> @page Section1
**** Command '@page' not recognized.
>>>> {size:612.0pt 792.0pt;
**** Command '{size:612.0pt' not recognized.
>>>> margin:72.0pt 90.0pt 72.0pt 90.0pt;}
**** Command 'margin:72.0pt' not recognized.
>>>> div.Section1
**** Command 'div.section1' not recognized.
>>>> {page:Section1;}
**** Command '{page:section1;}' not recognized.
>>>> -->
**** Command '-->' not recognized.
>>>> </style>
**** Command '</style>' not recognized.
>>>>
>>>> </head>
**** Command '</head>' not recognized.
>>>>
>>>> <body lang=3DEN-US link=3Dblue vlink=3D"#606420">
**** Command '<body' not recognized.
>>>>
>>>> <div class=3DSection1>
**** Command '<div' not recognized.
>>>>
>>>> <p class=3DMsoNormal><font size=3D2 face=3DArial><span =
**** Command '<p' not recognized.
>>>> style=3D'font-size:10.0pt;
**** Command 'style=3d'font-size:10.0pt;' not recognized.
>>>> font-family:Arial'>Subscribe
>>>> smart-board<o></o></span></font></p>
**** Command 'font-family:arial'>subscribe' not recognized.
>>>>
>>>> </div>
**** Command '</div>' not recognized.
>>>>
>>>> </body>
**** Command '</body>' not recognized.
>>>>
>>>> </html>
**** Command '</html>' not recognized.
>>>>
>>>> ------=_NextPart_000_0085_01C57350.08249400--
**** Command '------=_nextpart_000_0085_01c57350.08249400--' not recognized.
>>>>
>>>>
**** Help for Majordomo@:


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

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@".
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@:

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@. (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@:

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@ 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@:

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@.

VII. GETTING MORE HELP

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

To get another copy of this help message, send mail to Majordomo@ 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@". 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@".
 
Old 06-19-2005, 03:30 PM   #2
david_ross
Moderator
 
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047

Rep: Reputation: 66
Make sure you are sending it as plain text and not as html.
 
Old 06-19-2005, 06:08 PM   #3
paul_mat
Member
 
Registered: Nov 2004
Location: Townsville, Australia
Distribution: Fedora Core 5, CentOS 4, RHEL 4
Posts: 855

Original Poster
Rep: Reputation: 30
when i send in plain text all that happens is the top part just before the 'Subscribe smart-board
Succeeded' is cut off. so i guess thats one of the problems gone, is there a way i can make majordomo accept rich text/html text? and does anyone know about the last part of the message?


--

>>>> This is a multi-part message in MIME format.
**** Command 'this' not recognized.
>>>>
>>>> ------=_NextPart_000_0085_01C57350.08249400
**** Command '------=_nextpart_000_0085_01c57350.08249400' not recognized.
>>>> Content-Type: text/plain; charset="us-ascii"
**** Command 'content-type:' not recognized.
>>>> Content-Transfer-Encoding: 7bit
**** Command 'content-transfer-encoding:' not recognized.
 
Old 06-19-2005, 06:36 PM   #4
jrdioko
Member
 
Registered: Oct 2002
Distribution: Debian 6.0.2 (squeeze)
Posts: 944

Rep: Reputation: 30
All the subscribe email has to contain is the "subscribe" line. If I understand your situation correctly, majordomo is trying to process all the other lines in the email you sent it (such as ">>>> This is a multi-part message in MIME format."), and failing because those are not valid commands. The help message at the bottom of your post explains it in a way:

Quote:
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.
 
Old 06-19-2005, 07:08 PM   #5
paul_mat
Member
 
Registered: Nov 2004
Location: Townsville, Australia
Distribution: Fedora Core 5, CentOS 4, RHEL 4
Posts: 855

Original Poster
Rep: Reputation: 30
hi there, does anyone have a good how to guide for removing the mime format for majorodmo e-mails?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
majordomo paul_mat Linux - Newbie 0 06-06-2005 07:59 PM
"subscribe to thread"? "subscribe to forum"? johnMG LQ Suggestions & Feedback 4 04-12-2005 09:50 PM
majordomo ????? pudhiyavan Linux - General 0 02-19-2004 07:52 AM
majordomo!! katana Linux - General 8 09-23-2001 07:44 AM
Majordomo Help! markma Linux - General 2 12-18-2000 09:07 AM


All times are GMT -5. The time now is 12:14 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration