Index: ossp-pkg/petidomo/README RCS File: /v/ossp/cvs/ossp-pkg/petidomo/README,v co -q -kk -p'1.1.1.1' '/v/ossp/cvs/ossp-pkg/petidomo/README,v' | diff -u /dev/null - -L'ossp-pkg/petidomo/README' 2>/dev/null --- ossp-pkg/petidomo/README +++ - 2025-04-11 22:34:38.015491061 +0200 @@ -0,0 +1,90 @@ + + Petidomo Mailing List Manager + Version 2.2 beta 2 + + +Greetings citizen, + +I know how tedious reading "manuals" is when you're eager to install +the new software, so I'll keep it as short as possible. Before +Petidomo can be installed, either from a binary or a source +distribution, you -must- do the following: + + 1) Create a user of the name "petidomo". + + The petidomo-user is needed by the software, but will usually not + be used to log into the system, so you should set the password + entry to "*" and the login shell to "/usr/bin/true" or + "/sbin/nologin" -- depending on what your system uses. + + + 2) Create a group of the name "petidomo". + + This group should contain all users of your system who are allowed + to administrate Petidomo or for other reasons need access to the + installation. The "petidomo" user should be a member of this + group, too, even though this is not strictly necessary. + + + 3) Create the home directory of the "petidomo" user. + + The home directory is the place where the package will live. A + good place is "/usr/local/petidomo", but you can place it + wherever it suits your installation. + + +Once the user, the group and the directory exist, you can use the +following mechanisms to do the actual installation. + +If you're upgrading from Petidomo 2.0 and have some mailing lists +installed already, you can safely use these mechanisms, too. In no +event will the installation procedure overwrite your config files or +change anything except for the actual binaries. + +The installation itself works as follows: + + Binary distribution: + + Become 'root' and start the "install.sh" script, which can be + found in the same directory as this file. install.sh will populate + the home directory of the petidomo user and insert the required + mail aliases into /etc/aliases. Then it will install the CGI + config manager and that's it: Petidomo is ready to run. + + + Source distribution: + + Obviously you need to compile the sources first of all. In order + to compile Petidomo, you will need the following tools: + + - a C compiler, preferably gcc or egcs + + - a version of make(1) that understands the "include" and + ".PHONY" statement (use GNU make if your native make doesn't) + + - flex, the GNU version of lex + + - bison, the GNU version of yacc, at least version 1.25. Older + version -might- work, but I had problems with them, because + they're lacking the YYERROR_VERBOSE mechanism. + + If you have all these tools, you can compile Petidomo with the + following commands: + + $ make + $ make install (must be done as root) + + +In case you experience any problems you're not able to fix, you're +welcome to file a problem report with the "send-pr" utility, included +in the distribution. You might also want to check out the +petidomo-users mailing list, to which you can subscribe by sending a +SUBSCRIBE command to the following address: + + petidomo-users-request@petidomo.com + +Okay, I hope you'll find the Petidomo Mailing List Manager useful, and +may the force be with you! + + + Peter Simons Index: ossp-pkg/petidomo/config/list-config RCS File: /v/ossp/cvs/ossp-pkg/petidomo/config/list-config,v co -q -kk -p'1.1.1.1' '/v/ossp/cvs/ossp-pkg/petidomo/config/list-config,v' | diff -u /dev/null - -L'ossp-pkg/petidomo/config/list-config' 2>/dev/null --- ossp-pkg/petidomo/config/list-config +++ - 2025-04-11 22:34:38.018312213 +0200 @@ -0,0 +1,135 @@ +# +# ~petidomo/lists//config +# +# $Header$ +# + +# TAG: ListType +# The following types of mailing lists exists and one of them +# should be specified here: +# +# open -- The list is open for all postings which are not rejected +# due to the access control mechanism. +# closed -- Only subscribers are allowed to post. +# moderated -- Only postings which contain the correct posting +# password are allowed. +# +# This option is REQUIRED. Petidomo will abort with an error, if it is +# unset. +ListType open + +# TAG: AllowPublicSubscription +# yes -- Everybody can subscribe and unsubscribe. +# no -- Un-/subscription can only be done by the admin. +# Authenticiation is done via password mechanism. +# +# The default, if this option is unset, is to allow public +# subscription and unsubscription. +AllowPublicSubscription yes + +# TAG: AllowAlienSubscription +# yes -- Users are allowed to subscribe and unsubscribe addresses +# not equal to the address they're sending the mail from. +# no -- Users can only add (or remove) the address they're sending +# the mail from to the list (from the list). +# This option has no effect if public subscription has been +# disallowed. +# +# The default, if this option is unset, is to allow alien +# subscription and unsubscription. +AllowAlienSubscription yes + +# TAG: AllowMembersCommand +# Does the 'members' or 'who' command work for this mailing list, or +# do you want to keep the addresses of the subscribers confidential? +# Set this option to 'yes' to allow the 'members'-command, or set it +# to 'no' to disallow it. +# +# The default, if the option is unset, is NOT to allow the 'members'- +# command. +AllowMembersCommand no + +# TAG: ShowOnIndex +# Specify either "yes" or "no", depending on whether you want +# this mailing list to be shown on the index of available lists. +# +# The default, if the option is unset, is to show the mailing +# list on the index. +ShowOnIndex yes + +# TAG: Hostname +# This entry specifies the fully qualified domain name, Petidomo +# should use. This will usually be the 'real' name of the machine the +# software is running on, for example: +# +# HostName listserver.foo.bar +# +# The name of the machine and the used name need not necessarily be +# the same, though. Please consult the manual for further details +# about using this feature, looking at the chapter ``Virtual +# Hosting''. +# +# If this option is unset, Petidomo will use the name that has +# been specified in the master config file, ~petidomo/etc/petidomo.conf. +#Hostname host.domain.net + +# TAG: AdminPassword +# This tag sets the master password, which authenticiates the +# administrator of this mailing list. The administrator has +# special priviledes, such as deleting other users, overriding +# access control restrictions or un-/subscribing users to closed +# mailing lists. Passwords are always case-insensitive. +# +# Leave this entry blank, if you don't want to enable remote +# administration of the mailing list. This is not recommended, +# though, because you will have to edit all files manually, +# then. +#AdminPassword "open sesame" + +# TAG: PostingPassword +# The posting password must be specified when posting to closed +# or moderated mailing lists, or the server will reject the +# article and forward it to the list owner. Passwords are always +# case-insensitive. +#PostingPassword "yeahyeah" + +# TAG: ReplyTo +# This tag controls the 'Reply-To:' field, which Petidomo adds +# to posted articles before they are delivered. Using this +# option, you can force Petidomo to insert a 'Reply-To:' which +# points to a certain address, or you can tell Petidomo to leave +# 'Reply-To:' alone, by setting the parameter to "none". +# +# If this option is unset, Petidomo will default to insert a +# 'Reply-To:' point back to the mailing list, so that +# subscribers can conveniently post simply by hitting the +# 'reply' function in their mail reader. +#ReplyTo none + +# TAG: PostingFilter +# If you specify a posting filter, this program or script will +# be started by Petidomo right before it sends a posting out to +# the subscribers. The programm will receive the article, as it +# has been prepared by Petidomo on standard input and is expect +# to write the final version to standard output. The posting +# filter can be used to manipulate the headers for special +# purposes, for example. +# +# If the filter program exits with a returncode not equal to 0 +# (zero), Petidomo will not post the article and terminate. +#PostingFilter "/bin/cat" + +# TAG: Archive +# Petidomo has the ability to archive all articles that have been +# posted to a mailing list. With this tag you can chose the path to +# this archive. You have two options: You can specify a directory +# name here, or a file name. If Petidomo finds a file name, it will +# simply append the posted article to the file, one by one. If you +# provide the path of a directory, Petidomo will save each article in +# a seperate file into this directory. Paths without a leading slash +# ("/") are treated relative to the list's home directory, otherwise +# the path is absolute. +# +# If this option is unset, no archives of the posted articles will be +# kept. +#Archive "log"