Re: Please review Mailman templates
On Fri, Feb 17, 2006 at 04:43:08PM +0100, Lionel Elie Mamane wrote:
> I've tweaked the debconf template for mailman recently. As I'm not a
> native English speaker, I'd appreciate if you went over it and gave me
> an OK or comments. The current version is attached.
Here are a few suggestions:
> Template: mailman/site_languages
> Type: multiselect
> __Choices: big5, ca, cs, da, de, en, es, et, eu, fi, fr, hr, hu, it, ja, ko, lt, nl, no, pl, pt, pt_BR, ro, ru, sl, sr, sv, uk
> Default: en
> _Description: Which languages to support?
> For each supported language Debian Mailman stores default language
For each supported language, Debian Mailman stores default language
> specific texts in /etc/mailman/LANG/ giving them conffile like
specific texts in /etc/mailman/LANG/ giving them conffile-like
> treatment with the help of ucf. This means approximately 150kB for
> each supported language on the root FS.
treatment with the help of ucf. Approximately 150kB is required
on the root filesystem for each supported language.
[...]
> Template: mailman/gate_news
> Type: boolean
> Default: false
> _Description: Gate news to mail?
> Do you want to gate news to mail, that is, send all the messages which
Do you want to gate news to mail, that is, send all messages which
> appear in a newsgroup to a mailing list.
appear in a newsgroup to a mailing list?
[..]
> Template: mailman/create_site_list
> Type: note
> _Description: Missing site list
> Mailman needs a so-called "site list", which is the list from which
> password reminders and such are sent out from. This list needs to be
> created before mailman will start.
> .
> To create the list, run "newlist mailman" and follow the instructions
> on-screen. Note that you also need to start mailman after that,
on-screen. Note that you also need to start mailman afterwards
> using /etc/init.d/mailman start.
[...]
> Template: mailman/queue_files_present
> Type: note
> _Description: Old queue files present
> The directory /var/lib/mailman/qfiles contains files. It needs to be
The directory /var/lib/mailman/qfiles contains existing files. It needs to be
> empty for the upgrade to work properly. If these files contain
> unprocessed messages that are otherwise fine, then you can try to
> handle them by:
> - Stopping new messages from coming in the queue (at the MTA level:
- Stopping new messages from entering the queue (at the MTA level:
> queue them in the MTA's queue or refuse them with a 4xx code). If
> your site has a relatively low mailman traffic, you can skip this
> step.
> - Start a mailman queue runner: /etc/init.d/mailman start
> - Let it run until all messages are handled.
> If they don't all get handled in a timely manner, look at the logs
> to try to understand why and solve the cause.
> - Stop it: /etc/init.d/mailman stop
> - Retry the upgrade.
> - Let messages come in again.
> You can also decide to simply remove the files, which will make
> Mailman forget about (and lose) the corresponding emails; expect
Mailman forget about (and lose) the corresponding messages; expect
> angry users.
[...]
> Template: mailman/update_aliases
> Type: note
> _Description: Administrator must update aliases
> The aliases you need for mailman in your MTA's configuration have
> changed. Please run /var/lib/mailman/bin/genaliases to see the new
> aliases you need.
> .
> Until you do that, some features will stop working and mails will go
Until you do that, some features will stop working and messages will go
> out with an invalid Return-Path.
[...]
Regards
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
Reply to: