Your message dated Wed, 09 Aug 2006 17:21:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line mailman: Missing setup info
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mailman
Version: 2.0.11-1woody8
Severity: wishlist
I just installed mailman on Woody, and the install process didn't
configure it.
That's good, I prefer to install packages and read their documentation
before starting them, particularly when site-specific configuration is
required.
Unfortunately, no info on what to do next popped out. In contrast,
mailman (on RHL 7.3) has this information:
Description :
Mailman is software to help manage email discussion lists, much like
Majordomo and Smartmail. Unlike most similar products, Mailman gives
each mailing list a webpage, and allows users to subscribe,
unsubscribe, etc. over the Web. Even the list manager can administer
his or her list entirely from the Web. Mailman also integrates most
things people want to do with mailing lists, including archiving, mail
<-> news gateways, and so on.
When the package has finished installing, you will need to:
* Run /var/mailman/bin/mmsitepass
to set the mailman administrator password.
* Edit /var/mailman/Mailman/mm_cfg.py
to customize mailman's configuration for your site.
* Modify the sendmail configuration to ensure that it is running and
accepting connections from the outside world (to ensure that it runs,
set "DAEMON=yes" in /etc/sysconfig/sendmail, ensuring that it accepts
connections from the outside world may require modifying
/etc/mail/sendmail.mc and regenerating sendmail.cf), and
* Add these lines:
ScriptAlias /mailman/ /var/mailman/cgi-bin/
Alias /pipermail/ /var/mailman/archives/public/
<Directory /var/mailman/archives>
Options +FollowSymlinks
</Directory>
to /etc/httpd/conf/httpd.conf to configure your Web server.
I recommend this be adapted and included in future Debian packages. This
is in the package description: ideally I'd like it to be mailed to root
too so as to ensure it's not overlooked.
PS I prefer the virtual host configuration already in the wishlist list,
but if I changed what RH said I'd be fibbing.
Thanks for your time.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux mail 2.4.18-686 #1 Sun Apr 14 11:32:47 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages mailman depends on:
ii apache 1.3.26-0woody3 Versatile, high-performance HTTP s
ii apache [httpd] 1.3.26-0woody3 Versatile, high-performance HTTP s
ii apache-ssl [httpd] 1.3.26.1+1.48-0woody3 Versatile, high-performance HTTP s
ii cron 3.0pl1-72 management of regular background p
ii debconf 1.0.32 Debian configuration management sy
ii libc6 2.2.5-11.5 GNU C Library: Shared libraries an
ii logrotate 3.5.9-8 Log rotation utility
ii postfix [mail-tran 1.1.11-0.woody3 A high-performance mail transport
ii python 2.1.3-3.2 An interactive object-oriented scr
--- End Message ---
--- Begin Message ---
Hello John,
> package mailman
> tags 250804 + woody
> thanks
>
> Hi John,
>
> Thanks for your bugreport and sorry for the slow response. I can not
> fix the woody installation, as that closed for normal bugfixes; but I
> will check the READMEs for the upcoming stabe distribution, Sarge.
Since this only applies to woody and that can't be fixed, I'm closing
the report now. Thanks for reporting.
Thijs
signature.asc
Description: This is a digitally signed message part
--- End Message ---
