[ITT] po-debconf://teapop/fr.po
Bonjour,
C'est avec ce paquet que tous les paquets depuis la lettre "z" jusqu'à la
lettre "t" auront eu un rapport de bogue pour les faires passer à gettext.
Je soumets les debian/*templates* à la relecture également. Ils me paraissent
ok.
--
Michel Grentzinger
OpenPGP key ID : B2BAFAFA
Available on http://www.keyserver.net
Template: teapop/runmode
Type: select
_Choices: inetd, standalone, disabled
Default: inetd
_Description: How do you want teapop to be run?
Teapop can be run either using one of the common inetd "super-servers", in
"standalone" (otherwise known as "daemon") mode, or "disabled" (i.e. it
will not be run at all at the moment).
.
If run in standalone mode, teapop runs all the time, and does not have to
be started up each time a user connects to it. This makes it more
efficient for large/busy systems.
.
If run in inetd mode, teapop is only run when needed. This means that it
only uses memory when it's being used, and can give you more control over
the number of concurrent connections, where it will accept connections
from, and so on (especially with xinetd).
.
If disabled, everything will be set up, but nothing will actually be run.
.
The default is to use inetd mode.
.
If you change your mind later, see ${CONFFILE_DEB} for instructions on how
to change it.
Template: teapop/localmail
Type: boolean
Default: false
_Description: Do you want teapop to serve mail for this system's local users?
You will now be asked if you want teapop to allow local users to collect
their mail by POP3.
.
THIS MAY BE A BAD IDEA.
.
Unless you change the configuration, this uses the users' system passwords
to authenticate them. POP3 is usually used "in the clear", which makes it
*easy* for people to "sniff" your passwords from the network.
.
Possible solutions include preventing the users from logging in locally
(by setting their shells to /bin/false, for example -- obviously not
useful if they need login access), or manually configuring teapop to only
allow encrypted POP3 (using the stunnel package, perhaps).
.
If you are sure that users will never connect to this machine over an
insecure network, or if you don't care about the security of your machine,
it is OK to say "yes" here.
Template: teapop/already-passwd
Type: text
_Description: Existing configuration:
You appear to have an existing teapop configuration in ${CONFFILE_TEA} --
I won't touch it, but if you need to change teapop's configuration, that's
the place to start.
Template: teapop/runmode
Type: select
_Choices: inetd, standalone, disabled
Default: inetd
_Description: How do you want teapop to be run?
Teapop can be run either using one of the common inetd "super-servers", in
"standalone" (otherwise known as "daemon") mode, or "disabled" (i.e. it
will not be run at all at the moment).
.
If run in standalone mode, teapop runs all the time, and does not have to
be started up each time a user connects to it. This makes it more
efficient for large/busy systems.
.
If run in inetd mode, teapop is only run when needed. This means that it
only uses memory when it's being used, and can give you more control over
the number of concurrent connections, where it will accept connections
from, and so on (especially with xinetd).
.
If disabled, everything will be set up, but nothing will actually be run.
.
The default is to use inetd mode.
.
If you change your mind later, see ${CONFFILE_DEB} for instructions on how
to change it.
Template: teapop/localmail
Type: boolean
Default: false
_Description: Do you want teapop to serve mail for this system's local users?
You will now be asked if you want teapop to allow local users to collect
their mail by POP3.
.
THIS MAY BE A BAD IDEA.
.
Unless you change the configuration, this uses the users' system passwords
to authenticate them. POP3 is usually used "in the clear", which makes it
*easy* for people to "sniff" your passwords from the network.
.
Possible solutions include preventing the users from logging in locally
(by setting their shells to /bin/false, for example -- obviously not
useful if they need login access), or manually configuring teapop to only
allow encrypted POP3 (using the stunnel package, perhaps).
.
If you are sure that users will never connect to this machine over an
insecure network, or if you don't care about the security of your machine,
it is OK to say "yes" here.
Template: teapop/already-passwd
Type: text
_Description: Existing configuration:
You appear to have an existing teapop configuration in ${CONFFILE_TEA} --
I won't touch it, but if you need to change teapop's configuration, that's
the place to start.
Template: teapop/runmode
Type: select
_Choices: inetd, standalone, disabled
Default: inetd
_Description: How do you want teapop to be run?
Teapop can be run either using one of the common inetd "super-servers", in
"standalone" (otherwise known as "daemon") mode, or "disabled" (i.e. it
will not be run at all at the moment).
.
If run in standalone mode, teapop runs all the time, and does not have to
be started up each time a user connects to it. This makes it more
efficient for large/busy systems.
.
If run in inetd mode, teapop is only run when needed. This means that it
only uses memory when it's being used, and can give you more control over
the number of concurrent connections, where it will accept connections
from, and so on (especially with xinetd).
.
If disabled, everything will be set up, but nothing will actually be run.
.
The default is to use inetd mode.
.
If you change your mind later, see ${CONFFILE_DEB} for instructions on how
to change it.
Template: teapop/localmail
Type: boolean
Default: false
_Description: Do you want teapop to serve mail for this system's local users?
You will now be asked if you want teapop to allow local users to collect
their mail by POP3.
.
THIS MAY BE A BAD IDEA.
.
Unless you change the configuration, this uses the users' system passwords
to authenticate them. POP3 is usually used "in the clear", which makes it
*easy* for people to "sniff" your passwords from the network.
.
Possible solutions include preventing the users from logging in locally
(by setting their shells to /bin/false, for example -- obviously not
useful if they need login access), or manually configuring teapop to only
allow encrypted POP3 (using the stunnel package, perhaps).
.
If you are sure that users will never connect to this machine over an
insecure network, or if you don't care about the security of your machine,
it is OK to accept here.
Template: teapop/already-passwd
Type: text
_Description: Existing configuration:
You appear to have an existing teapop configuration in ${CONFFILE_TEA} --
I won't touch it, but if you need to change teapop's configuration, that's
the place to start.
Reply to: