Kiran wrote:
>
> Hi Dan,
>
> Thanks for the help earlier. The list is now working. But there are a
> few problems associated with it
Your welcome.
>
> 1. When I send a subscription to majordomo@mydomain.com it sends me back two
> mails - one asking for confirmation for subscription the other giving
> Majordomo results with the following contents along with the help file. This
> seems as a problem with html...Any Ideas
Returning the two messages for an open+confirm subscribe_policy in your list
is correct. Answers to your other questions below...
>
> --
>
> >>>> This is a multi-part message in MIME format.
> **** Command 'this' not recognized.
> >>>>
> >>>> ------=_NextPart_000_0117_01BFCA59.FF9DE060
> **** Command '------=_nextpart_000_0117_01bfca59.ff9de060' not recognized.
> >>>> Content-Type: text/plain;
> **** Command 'content-type:' not recognized.
> >>>> charset="iso-8859-1"
> **** Command 'charset="iso-8859-1"' not recognized.
> >>>> Content-Transfer-Encoding: quoted-printable
> **** Command 'content-transfer-encoding:' not recognized.
> >>>>
> >>>> subscribe infra
> **** Your request to editor@indiainfoline.com:
> ****
> **** subscribe infra kiran@indiainfoline.com
> ****
> **** must be authenticated. To accomplish this, another request must be
> **** sent in with an authorization key, which has been sent to:
> **** kiran@indiainfoline.com
> ****
> **** If the message is not received, there is generally a problem with
> **** the address. Before reporting this as a problem, please note the
> **** following:
> ****
> **** You only need to give an address to the subscribe command if you want
> **** to receive list mail at a different address from where you sent the
> **** command. Otherwise you can simply omit it.
> ****
> **** If you do give an address to the subscribe command, it must be a legal
> **** address. It should not consist solely of your name. The address must
> **** point to a machine that is reachable from the list server.
> ****
> **** If you have any questions about the policy of the list owner, please
> **** contact "infra-approval@indiainfoline.com".
> ****
> **** Thanks!
> ****
> **** editor@indiainfoline.com
> >>>>
> >>>> ------=_NextPart_000_0117_01BFCA59.FF9DE060
> **** Command '------=_nextpart_000_0117_01bfca59.ff9de060' not recognized.
> >>>> Content-Type: text/html;
> **** Command 'content-type:' not recognized.
> >>>> charset="iso-8859-1"
> **** Command 'charset="iso-8859-1"' not recognized.
> >>>> Content-Transfer-Encoding: quoted-printable
> **** Command 'content-transfer-encoding:' not recognized.
> >>>>
> >>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> **** Command '<!doctype' not recognized.
> >>>> <HTML><HEAD>
> **** Command '<html><head>' not recognized.
> >>>> <META content=3D"text/html; charset=3Diso-8859-1" =
> **** Command '<meta' not recognized.
> >>>> http-equiv=3DContent-Type>
> **** Command 'http-equiv=3dcontent-type>' not recognized.
> >>>> <META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
> **** Command '<meta' not recognized.
> >>>> <STYLE></STYLE>
> **** Command '<style></style>' not recognized.
> >>>> </HEAD>
> **** Command '</head>' not recognized.
> >>>> <BODY bgColor=3D#ffffff>
> **** Command '<body' not recognized.
> >>>> <DIV><FONT face=3DArial size=3D2>subscribe =
> **** Command '<div><font' not recognized.
> >>>> infra</FONT></DIV></BODY></HTML>
> **** Command 'infra</font></div></body></html>' not recognized.
> >>>>
> >>>> ------=_NextPart_000_0117_01BFCA59.FF9DE060--
> **** Command '------=_nextpart_000_0117_01bfca59.ff9de060--' not recognized.
> >>>>
> **** Help for editor@indiainfoline.com:
>
> 2. When I send a mail to list-request@mydomain.com, the same procedure
> follows the 2nd mail gives the above junk?
Your list-request address basically forwards to majordomo. That is why
you get the same results as writing directly to majordomo. The problem
lies in your email client sending the request in html or as a mime
attachment instead of inline plain text.
Think of it this way. If you write a paper letter to someone, you write
it in the language they will understand, without backgrounds, colors, or
fancy fonts that can confuse the reader. Majordomo needs to be treated
the same way electronically. (plain text messages)
[Optionally, you could add a pre-processor to the list to de-mime the
messages. There are other experts here that can help you with that.]
> 3. How can I edit the help file? where is this situated?
The help file is built into majordomo itself, in a file called majordomo,
and starts near line # 1367. Be sure to use a non-Microsoft text editor
when making modifications to this file. (unless you like living on the
edge)
> 4. How can I change the headers to include customised msgs?
In your listname.config file there is a setting called message_headers.
You can do something like this;
message_headers << END
X-Mailing-List: $LIST
X-Loop: $LIST\@mydomain.com
X-Unsubscribe-Address: $LIST-unsubscribe\@mydomain.com
X-Unsubscribe-URL: http://www.mydomain.com/unsubscribe-$LIST
END
Note: The $LIST token is expanded to your actual listname for you.
These lines are not displayed in the message body. You must have
full header viewing enabled to see them.
If you want a message body header (fronter in majordomo terminology),
use the message_fronter setting the same as you would a message_footer.
message_fronter << END
-
---
This message is being sent to you as a subscriber of $LIST.
If you would like to be removed from future mailings, please
visit http://www.mydomain.com/unsubscribe-$LIST and
enter the email address you received this message at.
---
-
END
Note: The single dash preserves a blank line at the top and bottom
of the fronter. The multi-dash line tells majordomo not to process
any of the fronter as possible administrivia. Then your fronter
for whatever purposes you like, followed by dashes (for balance
in the eye of your readers), and the preserved blank line before
the text of the actual message begins.
Dan Liston
PS. Be willing to do LOTS of experimenting to get it right.
>
> Would apppreciate if u could reply at the earliest?
> And thanks in advance.
>
> Kiran
Follow-Ups:
References:
|
|
