kawfy wrote:lukewill wrote:kawfy wrote:cat /usr/share/doc/packages/mailman/README.SuSE
[...]
Wenn Du mich auf etwas besonderes hinweisen möchtest, müsstest du ein wenig konkreter werden.
Ich würde gerne die Datei selbst lesen, vielleicht finden ich und andere dort Hinweise und können dir Tipps geben.
Ehrllch gesagt, sprichst du etwas in rätseln. Oder möchtest du vielleicht das ich die README.SuSE hier poste, na ja kann nicht schaden:
---- README.SuSE -----------
Installation notes for package Mailman
--------------------------------------
Last change: 2003-08-11
Authors: VladimÃr Linek <
feedback@suse.de>
Heiko Rommel <
feedback@suse.de>
Basic configuration
===================
The package is prefconfigured for use with the Apache web server and the
Postfix MTA.
If this suites your installation, you should be done by working through the four
steps below:
1) in /etc/sysconfig/mailman tweak the parameters
MAILMAN_SMTPHOST
MAILMAN_DEFAULT_NNTP_HOST
MAILMAN_DEFAULT_EMAIL_HOST
MAILMAN_DEFAULT_URL_HOST
and run SuSEconfig.
2) Call "/usr/lib/mailman/bin/mmsitepass" as user root to set your site
master password.
3) Finally, call "/usr/lib/mailman/bin/newlist mailman" as user root to create
the master mailing list. This list is needed for the inner workings of
Mailman. For details see /usr/share/doc/packages/mailman/README.
4) Add /var/lib/mailman/data/aliases to the alias_maps statement in /etc/postfix/main.cf:
alias_maps = hash:/etc/aliases, ..., hash:/var/lib/mailman/data/aliases
and reload postfix.
You can either create mailing lists through the web interface or with the
"newlist" command as root (located in /usr/lib/mailman/bin).
In both cases, the lists' aliases are created automatically and propagated to
the Postfix MTA.
Other MTAs
==========
If you want to use Mailman with a different MTA, you should work through the
following steps:
- change MAILMAN_MTA in /etc/sysconfig/mailman
- have a look at /usr/share/doc/packages/mailman/README.<your MTA>
- set MAILMAN_MAIL_GID in /etc/sysconfig/mailman accordingly to what gid your
MTA uses when running script aliases - if you use Sendmail, this is probably 2
(group daemon)
- check that /var/lib/mailman/data/aliases is used as alias table by your MTA
- run SuSEconfig
Other web servers
=================
If you want to use Mailman with a different web server, you should work through
the following steps:
- create script aliases and path aliases as pointed out in
/usr/share/doc/packages/mailman/INSTALL, section "4. Final system set-up"
- set MAILMAN_CGI_GID in /etc/sysconfig/mailman accordingly to what gid your
web server uses when running cgi scripts
- run SuSEconfig
Cron entries
============
Cron entries for Mailman are located in /usr/lib/mailman/cron/crontab and are
copied into /etc/cron.d/ when Mailman is started (with /usr/sbin/rcmailman
for example). If you want to make some changes in the crontab, please modify
the source file and reload the service.
Starting/Stopping/Reloading
===========================
You should not use mailmanctl for these tasks. Use
rcmailman {start|stop|status|try-restart|restart|force-reload|reload}
Upgrading
=========
Your old site configuration (including archives) should have been updated
automatically during the installation of this package. However, you can invoke
Mailman's update script (/usr/lib/mailman/bin/update) without harm.
The lists' aliases can be regenerated by Mailman's genaliases script
(/usr/lib/mailman/bin/genaliases). Dependent on the settings in
/etc/sysconfig/mailman these aliases will be written to a built-in file, to the
screen or nowhere at all.
Editing List Archives
=====================
This package features a patch by Adriane Boyd that makes it possible for list
administrators to edit their list archives through a web interface linked into
the admin interface.
A new cgi script called editarch allows administrators to browse by month and
delete messages from the archives. The messages are immediately deleted from
the mbox file, but because of the overhead in reprocessing archives, the
archives aren't redone on-the-fly. Instead, a file is kept with a running list
of recently edited archives and a nightly cron job does the reprocessing. The
file location is configurable in mm_cfg. (Note: since it has to read through
the mbox file message by message, pages will load slowly for lists with large
archives.)
Remember to have a lot of fun!
Your SuSE Team
----------EOF------------