Re: Reply to: not working

Ed Kasky <[email protected]>
Newsgroups gmane.mail.majordomo.general
Message-ID <[email protected]>
At 08:38 AM Thursday, 9/1/2005, Robert Isaac wrote -=>

>The dropped (s) was a typo, thanks for pointing it out. The alias's seem 
>to be working correctly:
>lists-owner: volvo lists: "|/usr/local/majordomo/wrapper majordomo" 
>majordomo: "|/usr/local/majordomo/wrapper majordomo" owner-majordomo: 
>lists-owner majordomo-owner: lists-owner directors: 
>"|/usr/local/majordomo/wrapper resend -l directors directors-list" 
>directors-list: :include:/usr/local/majordomo/lists/directors 
>owner-directors: [email protected] directors-owner: 
>[email protected] directors-approval: 
>[email protected] directors-request: 
>"|/usr/local/majordomo/wrapper majordomo -l directors"
These look okay to me with one exception.  I would add "nobody" at the end 
of the wrapper alias:
directors: "|/usr/local/majordomo/wrapper resend -l directors 
directors-list,nobody"

 From the faq:

    Sendmail 8.x will unfortunately log your -outgoing alias in the
    "Received:" lines. To prevent this you need to specify more than one
    address for the list name argument to resend. (for example
    "mylist:|"/usr/local/lib/majordomo/wrapper resend -h foo.org -l mylist
    mylist-seekrit,nobody"" where nobody is an alias for /dev/null)

You would add the following to your aliases:
nobody: /dev/null

>'volvo' in line 1 is my mailbox, should this be an actual address or does 
>it not matter?

Not sure what you mean by this.

>Now I have sorted out the smrsh issue as well new users can subscribe and 
>the messages all come through. I will see how the 'directors-list' runs as 
>it is only a small one, before setting up our main list.
>
>Is an incorrect GID and UID likely to be a problem. I used a current 
>user/group - daemon - in Makefile, as it would not install if I created a 
>new user and group 'majordomo'.

If it were I don't think anything would work for the list.  Am I correct in 
assuming that the list is sending to the recipients but not  reading 
updates to the config file?

Check that the config file is


>Thanks for your help, greatly appreciated.
>
>Bob
>
>___________________________________________________
>Robert Isaac
>Director and Web Administrator
>Volvo Owners Club
>
><file://www.volvoclub.org.uk>www.volvoclub.org.uk
>
>Please include all previous text with reply
>All messages are scanned with an antivirus scanner.
>
>-----Original Message-----
>From: [email protected] 
>[<mailto:[email protected]>mailto:[email protected]] 
>On Behalf Of Ed Kasky
>Sent: 01 September 2005 06:30
>To: [email protected]
>Cc: [email protected]
>Subject: Re: Reply to: not working
>
>Is the list "director-list" or "directors-list" - you have it as the 
>former in your footer and the latter in the reply_to
>
>Also, personally I find it much easier to keep all the file names the same 
>as the list.  In your config file you are mixing "directors" and 
>"director(s)-list"
>
>On another note, I had a problem very similar to this recently setting up 
>a new list.  None of the changes I was making in the config file were 
>taking effect when posting.  I figured out the my aliases for the list 
>were not correct.
>
>Double check the aliases if you can against a known working example.
>
>This is what I use as a template for lists with an archive and digest:
>test: "|/usr/local/majordomo/wrapper resend -l test test-outgoing,nobody'"
>test-outgoing: :include:/usr/local/majordomo/lists/test, test-archive, 
>test-digestify
>test-digestify: "|/usr/local/majordomo/digest -r -C -l test-digest 
>test-digest-outgoing"
>test-digest: test
>test-digest-outgoing: :include:/usr/local/majordomo/lists/test-digest
>test-archive:  "|/usr/local/majordomo/wrapper archive -f 
>/usr/local/majordomo/archives/test/test -a -M"
>
>At 02:23 PM Wednesday, 8/31/2005, Robert Isaac wrote -=>
>
> >  Thank you. I use Webmin which has a Majordomo module. To answer your
> > questions:
> >Where exactly are you making these changes?
> >In the config file for the list - directors-list, the file is
> >/lists/directors.config:
> >
> >This is for the footer:
> >         # message_footer       [string_array] (undef) <resend,digest>
> >         # Text to be appended at the end of all messages posted to the
> >         # list. The text is expanded before being used. The following
> >         # expansion tokens are defined: $LIST - the name of the current
> >         # list, $SENDER - the sender as taken from the from line, 
> $VERSION,
> >         # the version of majordomo. If used in a digest, no expansion
> >         # tokens are provided
> >message_footer        <<   END
> >NOTE: When sending a reply send it to: [email protected]
> >END
> >
> >This is for the Reply to:
> >
> >         # reply_to             [word] () <resend,digest>
> >         # Put a reply-to header with value <value> into the outgoing
> >         # message. If the token $SENDER is used, then the address of the
> >         # sender is used as the value of the reply-to header. This is the
> >         # value of the reply-to header for digest lists.
> >reply_to = [email protected]
> >
> >         # resend_host          [word] (undef) <resend>
> >         # The host name that is appended to all address strings specified
> >         # for resend.
> >resend_host = volvoclub.org.uk
> >
> >         # restrict_post        [restrict_post] (undef) <resend>
> >         # If defined, only addresses listed in these files (colon or space
> >         # separated) can post to the mailing list. By default, these files
> >         # are relative to the lists directory. These files are also 
> checked
> >         # when get_access, index_access, info_access, intro_access,
> >         # which_access, or who_access is set to 'list'. This is less 
> useful
> >         # than it seems it should be since there is no way to create these
> >         # files if you do not have access to the machine running resend.
> >         # This mechanism will be replaced in a future version of
> >         # majordomo/resend.
> >restrict_post = directors
> >
> >         # sender               [word] (owner-directors)
> > <majordomo,resend,dig
> >         # The envelope and sender address for the resent mail. This string
> >         # has "@" and the value of resend_host appended to it to make a
> >         # complete address. For majordomo, it provides the sender address
> >         # for the welcome mail message generated as part of the subscribe
> >         # command.
> >sender              =   owner-directors
> >
> >My understanding of the Reply to: is that when someone uses 'reply' to
> >an email from the list (directors-list) the list address automatically
> >goes into the TO field in the reply email so that it goes to the list
> >and not the originator. Have I misunderstood this?
> >-----Original Message-----
> >From: Ed Kasky [<mailto:[email protected]>mailto:[email protected]]
> >Sent: 31 August 2005 21:45
> >To: [email protected]
> >Cc: [email protected]
> >Subject: Re: Reply to: not working
> >
> >At 01:33 PM Wednesday, 8/31/2005, you wrote -=>
> > >ProLiant DL360 running RHESL4 with Apache 2 and Sendmail 8.13.1, with
> > >Majordomo 1.94.5
> > >
> > >I cannot get the Reply to: to work for discussions. If I put "Reply to:
> > >[email protected]" and send an email to the list from
> > >me, it arrives OK, but if I use the 'reply' function the email
> > >address in
> > the From:
> > >field is mine, not [email protected]. What have I missed 
> out?
> > >
> > >Also, the footer does not appear on the email.
> >
> >Where exactly are you making these changes?
> >
> >Are you making the changes to the config file directly or via email??
> >
> >Post what you have in your config file for these two things - it will
> >help us help you.
>
>. . . . . . . . . . . . . . . . . .
>Randomly Generated Quote (610 of 1003):
>It is a profitable thing, if one is wise, to seem foolish.
>                  -- Aeschylus

. . . . . . . . . . . . . . . . . .
Randomly Generated Quote (537 of 1003):
I find that principles have no real force except when one is well fed.
-Mark Twain (1835-1910)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.