Oh, forgot to mention, line 58 which is "majordom" in BSD. Since your
script indicates one needs to define this, I didn't think it was important.
On the other hand, a comment might be nice in interest of completeness.
At 02:23 AM 3.31.2002 -0600, Daniel Liston wrote:
>Please do not uncomment any lines between 32 - 45. These commands are
>"one time" commands that should NOT be executed every time the script is
>run. The sample commands are provided as information only.
>Your mods to lines 74, 75, and 76 have been added as comments to
>my script. Searching on "BSD" should help find all lines where changes
>are necessary throughout the entire script. Variables that are set using
>these line are only set IF data is not found from the /etc/passwd file. In
>that case, the majordomo user has a different login ID, or is not installed.
>Line 78 however, I chose not to implement, as the same information is
>discovered from line 76. The reason for leaving /etc/majordomo.cf in
>line 78 is because all the majordomo bundled perl scripts will also check
>for a config file in this location.
>The "die" comment in line 120 is related to the test performed in line 119.
>Since suid bit checking is not done on line 119, I am not sure the comment
>you are suggesting as a replacement on line 120 is adequate. In actuality,
>this file should be owner:group root:majordomo and 4550 or 4755 depending
>on your local security policies. I do not think we should allow "world"
>to execute wrapper, but I have been lucky enough so far, to use 4755. Then
>again, I only have admin user accounts on my majordomo machine.
>I agree with line 143, and will set the default location for sendmail.cf
>to be in the /etc/mail directory, with a comment of possible location in
>/etc/sendmail. These lines are currently just comments, but if this is
>working reliably for you, and I get feedback from people having success
>in other operating systems, I will uncomment it permanently. If this is
>uncommented, lines 157 - 161 become unnecessary. Conversely, if lines
>143 - 156 are left commented, line 157 should contain a comment that lets
>users know it expects the majordomo.aliases location to be a root owned
>link to the $mjhome/majordomo.aliases file. I will add this comment, but
>will also have to adjust other lines with references to line numbers that
>change below this line. Again, lines 143 - 156 are experimental code to
>replace lines 157 - 161.
>Lines 376 - 443 may be changed to modify the default behavior of your
>$listname-post.config settings. I would recommend leaving them like they
>are, for consistancy purposes with a default install of majordomo itself.
>The config can be modified with standard majordomo commands at any point
>after list creation by the list-owner.
>Sendmail will not read or write files outside the directory structure it is
>already aware of, unless certain security considerations are met. Consider
>linking /usr/local/majordomo/majordomo.aliases to
>and linking /usr/local/majordomo/majordomo.cf to /etc/majordomo.cf. Both of
>these links should be owned by root. The /etc/mail/aliases.majordomo link
>what should be referenced in the sendmail.cf file. You have to read the
>sendmail FAQ to understand why things don't work in "other" directories.
>Also note: My script assumes /etc/mail/majordomo.aliases rather than the BSD
>expected name of /etc/mail/aliases.majordomo. This is immaterial, as long
>as sendmail.cf and the actual link or file name are consistant. Besides, if
>the filename can be found in sendmail.cf, my script will use it.
>PS. Attached is the latest and greatest newlist3.pl.gz
>Server Admin wrote:
>> Dan: Yes, just before the posting to you below, I attached your script that
>> I had reviewed & modified for different file/directory names and paths for
>> FBSD 4.5 and mj 194.5_1. I have not tried the script yet because some other
>> deadlines got in the way, but want to get back on the mj setup after
>> Here again is the attached script newlist2.pl packed (to_dan.gz) with a
>> test file about changes. You could run "diff" on your original script vs.
>> my modified one to readily see the changes because I did not alter the line
>> Check the mj aliases name & path which are very different.
>> Any further comments appreciated.
>> At 10:04 PM 3.29.2002 -0600, Daniel Liston wrote:
>> >Jack, I do not recall previous discussions of script modifications,
>> >but the newlist2.pl does not search for a Password. It DOES search
>> >the password file for a majordomo uid:gid and a $HOME directory, so
>> >it can set file and directory ownership and permissions properly.
>> >The "pw" you are referring to is just a file handle to reference the
>> >password file, not the actual password.
>> >Server Admin wrote:
>> >> Dan: On my earlier post to you about the script modifications, I
>> >> or two other things. I noice your script interrogates the /etc/passwd
>> >> in seach of a pw, however, the install sets up Majordomo as a Pseudo
>> >> "user majordom" as follows:
>> >> majordom:*:54:54:Majordomo Pseudo User:/usr/local/majordomo:/nonexistent
>> >> Wonder what your script will return from that setting? All dir/files are
>> >> installed as user/owner majordom:majordom and of course access is
>> >> work on things.
>> >Depending on if you changed anything wrong in the script I provided, the
>> >output from the above information would return;
>> >Majordomo: UID=54, GID=54, HOME=/usr/local/majordomo
>> >Could not find majordomo or majordom in password file.
>> >Default majordomo: UID=91, GID=91, HOME=/usr/lib/majordomo
>> >Please edit line 58 of this script, or create majordomo user.
>> >Continuing to use this script will assume defaults above.
>> >Press Ctrl-C to abort now, or <enter> to continue.
>> >> Also, I've listed several path changes in my earlier notes and of course
>> >> there is a different treatment for the "aliases.majordomo" whci install
>> >> places in: /usr/local/majordomo instead of the /etc/mail path. It
>> >> build an "aliases.majordomo.db" in /usr/local/majordomo as well. I
>> >> the "permissions" to map properly there once and gave up and moved mjd
>> >> aliases into the main aliases in /etc/mail. It complained about "group
>> >> writable" or "unsafe".
>> >If you are running sendmail, do NOT change any paths in that regard.
>> >are for sendmail, and majordomo could care less where they are. The file
>> >should be owned by root, 644, or it should be a link to your
>> >that was created by root.
>> >> Also, I uncommented your "parsing" lines (starting at #143) to allow the
>> >> script's interrogation of the sendmail.cf file looking for the
>> >> that is appropriate???
>> >Anything commented is currently still under development, but if you have
>> >uncommented it, please let me know your results. It "should" work, but
>> >not necessarily under "all" conditions.
>> >> The changes I sent should be the "new standard" for FreeBSD ver 4.5+.
>> >I did not receive any changes. Please provide them. I have had interest
>> >in creating a pkg_add version of majordomo for BSD, but current projects
>> >have pushed this to a far back burner.
>> >> Hope the info is of use and shall look forward to your review of the
>> >> in light of the above and previous submission of modifications.
>> >> At 03:51 PM 3.24.2002 -0600, Daniel Liston wrote:
>> >> >Try modifying the attached perl script to fit your file locations, and
>> >> >execute it.
>> >> >
>> >> >Dan
>> >> >
>> >> >Server Admin wrote:
>> >> >>
>> >> >> Hello, Dan:
>> >> >> Sorry to bother you offlist from the Majordomo users list, but
>> >> >> signed up from this email and nothing is coming thru yet. We
>> >> >> over a year ago and you were a big help on another server I was and
>> >> >> am using. I sincerely hope you don't mind my intrusion on your time.
>> >> >>
>> >> >> However, the old server is a virtual server and is remote. I am
>> setting up
>> >> >> a brand new server running FBSD 4.5-Stable and am migrating all
>> >> >> over to it from the old one. 90% of the domains could be moved no.
>> But, I
>> >> >> am now trying to install and configure majordomo 1.95_1 from scratch.
>> >> >>
>> >> >> Majordomo is installed, including the usual "test-l" list.
>> >> >> hooked together, aliases and have run config-test and all is well
>> >> >> BUT, in lists, all of the test files are there except no test.config
>> >> >> which I have tried to create using the email command:
>> >> >> newconfig test-1 test
>> >> >>
>> >> >> also, tried the other commands, but all that happens is that my exact
>> >> >> sent arrives back, not as a bounce, but just an email with my same
>> >> >> I cannot create the config file. Any ideas appreciated, I've spen
>> hours on
>> >> >> this and looked at the archives, FAQ to no avail.... nothing found on
>> >> >> creating the config.
>Attachment Converted: "c:\eudora\attach\newlist3.pl.gz"
.... our website: http://www.sage-one.net/
Jack L. Stone