Re: [RFR2] templates://postfix/{templates}
A second round of niggles; only the last one is essential.
> Template: postfix/mydomain_warning
...
> Postfix version 2.3.3-2 and later require changes in main.cf.
> Specifically, mydomain must be specified, since hostname(2) is not
> a fully-qualified domain name (FQDN).
Specifically specified is repetitive. Make it "must be set"?
> Template: postfix/kernel_version_warning
> Type: boolean
> _Description: Install postfix despite a too old kernel?
You still can't quite say this... make it "an unsupported kernel".
> Template: postfix/rfc1035_violation
..
> The "${enteredstring}" string does not follow RFC 1035 and does not
> appear to be a valid IP address.
Make that 'The string "${enteredstring}"'.
> Template: postfix/mailname
...
> For example, if a mail address on the local host is foo@domain.example,
> then the correct value for this option would be example.com.
Search-and-replace error; foo@example.com (and we can do without the
first use of the word "example").
--
JBR
Ankh kak! (Ancient Egyptian blessing)
Template: postfix/mydomain_warning
Type: boolean
_Description: Add a 'mydomain' entry in main.cf for upgrade?
Postfix version 2.3.3-2 and later require changes in main.cf.
Specifically, mydomain must be set, since hostname(2) is not a
fully-qualified domain name (FQDN).
.
Failure to fix this will result in a broken mailer. Decline this option
to abort the upgrade, giving you the opportunity to add this configuration
yourself. Accept this option to automatically set mydomain based on the
FQDN of the machine.
Template: postfix/kernel_version_warning
Type: boolean
_Description: Install postfix despite an unsupported kernel?
Postfix uses features that are not found in kernels prior to 2.6. If you
proceeed with the installation, Postfix will not run.
Template: postfix/tlsmgr_upgrade_warning
Type: boolean
_Description: Correct tlsmgr entry in master.cf for upgrade?
Postfix version 2.2 has changed the invocation of tlsmgr.
.
Failure to fix this will result in a broken mailer. Decline this option
to abort the upgrade, giving you the opportunity to add this configuration
yourself. Accept this option to automatically make master.cf compatible
with Postfix 2.2 in this respect.
Template: postfix/rfc1035_violation
Type: boolean
Default: false
_Description: Ignore bad hostname entry?
The string "${enteredstring}" does not follow RFC 1035 and does not
appear to be a valid IP address.
.
RFC 1035 states that "each component must start with an alphanum, end with
an alphanum and contain only alphanums and hyphens. Components must be
separated by full stops."
.
Please choose whether you want to keep that choice anyway.
Template: postfix/main_mailer_type
Type: select
# Translators beware! the following six strings form a single
# Choices menu. - Every one of these strings has to fit in a standard
# 80 characters console, as the fancy screen setup takes up some space
# try to keep below ~71 characters.
# DO NOT USE commas (,) in Choices translations otherwise
# this will break the choices shown to users
__Choices: No configuration, Internet Site, Internet with smarthost, Satellite system, Local only
Default: Internet Site
_Description: General type of mail configuration:
Please select the mail server configuration type that best meets your needs.
.
No configuration:
Should be chosen to leave the current configuration unchanged.
Internet site:
Mail is sent and received directly using SMTP.
Internet site using smarthost:
Mail is received directly using SMTP or by running a utility such
as fetchmail. Outgoing mail is sent using a smarthost.
Satellite system:
All mail is sent to another machine, called a "smarthost", for delivery.
Local delivery only:
The only delivered mail is the mail for local users. There is no network.
Template: postfix/not_configured
Type: error
_Description: Postfix not configured
You have chosen 'No Configuration'. Postfix will not be configured and
will not be started by default. Please run 'dpkg-reconfigure postfix' at
a later date, or configure it yourself by:
- Editing /etc/postfix/main.cf to your liking;
- Running /etc/init.d/postfix start.
Template: postfix/mailname
Type: string
Default: /etc/mailname
_Description: System mail name:
The "mail name" is the domain name used to "qualify" mail addresses
without a domain name.
.
This name will also be used by other programs. It should be the
single, full domain name (FQDN).
.
Thus if a mail address on the local host is foo@example.com, the
correct value for this option would be example.com.
Template: postfix/destinations
Type: string
_Description: Other destinations to accept mail for (blank for none):
Please give a comma-separated list of domains for which this machine
should consider itself the final destination. If this is a mail
domain gateway, you probably want to include the top-level domain.
Template: postfix/relayhost
Type: string
_Description: SMTP relay host (blank for none):
Please specify a domain, host, host:port, [address] or
[address]:port. Use the form [destination] to turn off MX lookups.
Leave this blank for no relay host.
.
The relayhost parameter specifies the default host to send mail to when no
entry is matched in the optional transport(5) table. When no relayhost is
given, mail is routed directly to the destination.
Template: postfix/procmail
Type: boolean
_Description: Use procmail for local delivery?
Please choose whether you want to use procmail to deliver local mail.
.
Note that if you use procmail to deliver mail system-wide, you should set
up an alias that forwards mail for root to a real user.
Template: postfix/protocols
Type: select
__Choices: all, ipv6, ipv4
_Description: Internet protocols to use:
By default, whichever Internet protocols are enabled on the system at
installation time will be used. You may override this default with any
of the following:
.
all : use both IPv4 and IPv6 addresses;
ipv6: listen only on IPv6 addresses;
ipv4: listen only on IPv4 addresses.
Template: postfix/recipient_delim
Type: string
Default: +
_Description: Local address extension character:
Please choose the character that will be used to define a local address
extension.
.
To not use address extensions, leave the string blank.
Template: postfix/bad_recipient_delimiter
Type: error
_Description: Bad recipient delimiter
The recipient delimiter must be a single character. "${enteredstring}"
is what you entered.
Template: postfix/chattr
Type: boolean
Default: false
_Description: Force synchronous updates on mail queue?
If synchronous updates are forced, then mail is processed more slowly.
If not forced, then there is a remote chance of losing some mail if
the system crashes at an inopportune time, and you are not using a
journaled filesystem (such as ext3).
Template: postfix/mynetworks
Type: string
Default: 127.0.0.0/8
_Description: Local networks:
Please specify the network blocks for which this host should relay mail.
The default is just the local host, which is needed by some mail user agents.
.
If this host is a smarthost for a block of machines, you need to specify the
netblocks here, or mail will be rejected rather than relayed.
.
To use the postfix default (which is based on the connected subnets), enter
an empty string.
Template: postfix/mailbox_limit
Type: string
Default: 0
_Description: Mailbox size limit:
Please specify the limit that Postfix should place on mailbox files
to prevent runaway software errors. A value of zero (0) means no
limit. The upstream default is 51200000.
Template: postfix/root_address
Type: string
Default:
_Description: Root and postmaster mail recipient:
Mail for the "postmaster", "root", and other system accounts needs to
be redirected to the user account of the actual system administrator.
.
If this value is left empty, such mail will be saved in /var/mail/nobody,
which is not recommended.
.
Mail is not delivered to external delivery agents as root.
.
If you already have a /etc/aliases file, then you may need to add this
entry. Leave this blank to not add one.
--- templates.orig 2007-04-29 23:52:52.000000000 +0100
+++ templates.jbr 2007-04-29 23:56:46.000000000 +0100
@@ -1,173 +1,104 @@
-
-Template: postfix/dynamicmaps_upgrade_warning
-Type: boolean
-_Description: Correct dynamicmaps.cf for upgrade?
- Postfix version 2.0.2 and later require changes in dynamicmaps.cf.
- Specifically, wildcard support is gone, and with it, %s expansion. Any
- changes that you made to dynamicmaps.cf that relied on these features will
- need to be fixed by you. Failure to correct these will result in a broken
- mailer.
- .
- Should dynamicmaps.cf be automatically changed? Decline this option to
- abort the upgrade, giving you the opportunity to eliminate wildcard and
- %s-expansion-dependent configuration. Accept this option if you have no
- such configuration, and automatically make dynamicmaps.cf compatible with
- Postfix 2.0.2 in this respect.
-
-Template: postfix/master_upgrade_warning
-Type: boolean
-_Description: Correct master.cf for upgrade?
- Postfix version 2.1 and later require new services in master.cf.
- .
- Should this configuration be automatically added to master.cf? Decline
- this option to abort the upgrade, giving you the opportunity to add this
- configuration yourself. Accept this option to automatically make
- master.cf compatible with Postfix 2.1 in this respect.
-
Template: postfix/mydomain_warning
Type: boolean
-_Description: Add mydomain entry in main.cf for upgrade?
+_Description: Add a 'mydomain' entry in main.cf for upgrade?
Postfix version 2.3.3-2 and later require changes in main.cf.
- Specifically, mydomain must be specified, since hostname(2) is not
- a fully-qualified domain name (FQDN).
+ Specifically, mydomain must be set, since hostname(2) is not a
+ fully-qualified domain name (FQDN).
.
- Failure to fix this will result in a broken mailer. Decline this option
+ Failure to fix this will result in a broken mailer. Decline this option
to abort the upgrade, giving you the opportunity to add this configuration
- yourself. Accept this option to automatically set mydomain based on the
+ yourself. Accept this option to automatically set mydomain based on the
FQDN of the machine.
Template: postfix/kernel_version_warning
Type: boolean
-_Description: Kernel is too old to support postfix
- Postfix uses features that are not found in kernels prior to 2.6. If you
+_Description: Install postfix despite an unsupported kernel?
+ Postfix uses features that are not found in kernels prior to 2.6. If you
proceeed with the installation, Postfix will not run.
- .
- Install postfix anyway?
Template: postfix/tlsmgr_upgrade_warning
Type: boolean
_Description: Correct tlsmgr entry in master.cf for upgrade?
Postfix version 2.2 has changed the invocation of tlsmgr.
.
- Failure to fix this will result in a broken mailer. Decline this option
+ Failure to fix this will result in a broken mailer. Decline this option
to abort the upgrade, giving you the opportunity to add this configuration
- yourself. Accept this option to automatically make master.cf compatible
+ yourself. Accept this option to automatically make master.cf compatible
with Postfix 2.2 in this respect.
-Template: postfix/nqmgr_upgrade_warning
-Type: boolean
-_Description: Correct master.cf for upgrade?
- Postfix version 2.1 renamed "nqmgr" to "qmgr", and you are using "nqmgr".
- .
- Failure to fix this will result in a broken mailer. Decline this option
- to abort the upgrade, giving you the opportunity to add this configuration
- yourself. Accept this option to automatically make master.cf compatible
- with Postfix 2.1 in this respect.
-
-Template: postfix/db_upgrade_warning
-Type: boolean
-Default: true
-_Description: Should Postfix upgrade hash and btree maps?
- Postfix has switched to db4, and this may require maps to be upgraded.
- .
- Do you want to automatically attempt the conversion?
-
-Template: postfix/transport_map_warning
-Type: note
-_Description: Transport map incompatibility
- You have a transport map defined, and there is an incompatible change in
- how transport maps are used. Postfix will not be restarted automatically.
- .
- Transport map entries override $mydestination. If you use transport maps,
- it is better to always have explicit entries for all domain names you have
- in $mydestination. See the html/faq.html sections for firewalls and
- intranets. If you have transport entries for parent domains of anything
- delivered locally, you will probably need to add specific entries for the
- destination domains before you restart Postfix.
-
Template: postfix/rfc1035_violation
Type: boolean
Default: false
_Description: Ignore bad hostname entry?
- The string you have entered
- .
- "${enteredstring}"
- .
- does not follow RFC 1035 and does not appear to be a valid IP address.
+ The string "${enteredstring}" does not follow RFC 1035 and does not
+ appear to be a valid IP address.
.
RFC 1035 states that "each component must start with an alphanum, end with
an alphanum and contain only alphanums and hyphens. Components must be
separated by full stops."
.
- Do you want to keep it anyway?
+ Please choose whether you want to keep that choice anyway.
Template: postfix/main_mailer_type
Type: select
-_Choices: No configuration, Internet Site, Internet with smarthost, Satellite system, Local only
+# Translators beware! the following six strings form a single
+# Choices menu. - Every one of these strings has to fit in a standard
+# 80 characters console, as the fancy screen setup takes up some space
+# try to keep below ~71 characters.
+# DO NOT USE commas (,) in Choices translations otherwise
+# this will break the choices shown to users
+__Choices: No configuration, Internet Site, Internet with smarthost, Satellite system, Local only
Default: Internet Site
-_Description: General type of configuration?
- You have several choices for general configuration at this point. If you
- have your debconf priority set to 'low' or 'medium', you will be asked
- more questions later. You can always run "dpkg-reconfigure --priority=low
- postfix" at a later point if you want to see these questions again.
- .
- No configuration - IF YOU WANT THE INSTALL TO LEAVE YOUR CONFIG ALONE,
- CHOOSE THIS OPTION. No configuration changes will be done now: If you
- have not already configured Postfix, your mail system will be broken and
- should not be used. You must then do the configuration yourself by editing
- /usr/share/postfix/main.cf.dist and saving your changes as
- /etc/postfix/main.cf, or by running dpkg-reconfigure Postfix. main.cf
- will not be modified by the Postfix install process.
- .
- Internet site - mail is sent and received directly using SMTP. If your
- needs don't fit neatly into any category, you probably want to start with
- this one and then edit the config file by hand.
- .
- Internet site using smarthost - You receive Internet mail on this machine,
- either directly by SMTP or by running a utility such as fetchmail.
- Outgoing mail is sent using a smarthost. optionally with addresses
- rewritten. This is probably what you want for a dialup system.
+_Description: General type of mail configuration:
+ Please select the mail server configuration type that best meets your needs.
.
- Satellite system - All mail is sent to another machine, called a "smart
- host" for delivery. No mail is received locally.
- .
- Local delivery only - You are not on a network. Mail for local users is
- delivered.
+ No configuration:
+ Should be chosen to leave the current configuration unchanged.
+ Internet site:
+ Mail is sent and received directly using SMTP.
+ Internet site using smarthost:
+ Mail is received directly using SMTP or by running a utility such
+ as fetchmail. Outgoing mail is sent using a smarthost.
+ Satellite system:
+ All mail is sent to another machine, called a "smarthost", for delivery.
+ Local delivery only:
+ The only delivered mail is the mail for local users. There is no network.
Template: postfix/not_configured
-Type: note
-_Description: WARNING: Postfix not configured
- You have chosen "No Configuration" - Postfix will not be configured and
- will not be started by default. Please run 'dpkg-reconfigure postfix' at
+Type: error
+_Description: Postfix not configured
+ You have chosen 'No Configuration'. Postfix will not be configured and
+ will not be started by default. Please run 'dpkg-reconfigure postfix' at
a later date, or configure it yourself by:
- .
- 1) Editing /etc/postfix/main.cf to your liking
- .
- 2) Running /etc/init.d/postfix start
+ - Editing /etc/postfix/main.cf to your liking;
+ - Running /etc/init.d/postfix start.
Template: postfix/mailname
Type: string
Default: /etc/mailname
-_Description: Mail name?
- Your `mail name' is the hostname portion of the address to be shown on
- outgoing news and mail messages (following the username and @ sign).
+_Description: System mail name:
+ The "mail name" is the domain name used to "qualify" mail addresses
+ without a domain name.
+ .
+ This name will also be used by other programs. It should be the
+ single, full domain name (FQDN).
.
- This name will be used by other programs besides Postfix; it should be the
- single, full domain name (FQDN) from which mail will appear to originate.
+ Thus if a mail address on the local host is foo@example.com, the
+ correct value for this option would be example.com.
Template: postfix/destinations
Type: string
-_Description: Other destinations to accept mail for? (blank for none)
- Give a comma-separated list of domains that this machine should consider
- itself the final destination for. If this is a mail domain gateway, you
- probably want to include the top-level domain.
+_Description: Other destinations to accept mail for (blank for none):
+ Please give a comma-separated list of domains for which this machine
+ should consider itself the final destination. If this is a mail
+ domain gateway, you probably want to include the top-level domain.
Template: postfix/relayhost
Type: string
-_Description: SMTP relay host? (blank for none)
- Specify a domain, host, host:port, [address] or [address]:port. Use the
- form [destination] to turn off MX lookups. Leave this blank for no relay
- host.
+_Description: SMTP relay host (blank for none):
+ Please specify a domain, host, host:port, [address] or
+ [address]:port. Use the form [destination] to turn off MX lookups.
+ Leave this blank for no relay host.
.
The relayhost parameter specifies the default host to send mail to when no
entry is matched in the optional transport(5) table. When no relayhost is
@@ -176,84 +107,79 @@
Template: postfix/procmail
Type: boolean
_Description: Use procmail for local delivery?
- Do you want to use procmail to deliver local mail?
+ Please choose whether you want to use procmail to deliver local mail.
.
Note that if you use procmail to deliver mail system-wide, you should set
up an alias that forwards mail for root to a real user.
Template: postfix/protocols
Type: select
-_Choices: all, ipv6, ipv4
-_Description: Internet protocols to use?
- By default, whichever internet protocols are enabled on the system at
- installation time will be used. You may override this default with any
+__Choices: all, ipv6, ipv4
+_Description: Internet protocols to use:
+ By default, whichever Internet protocols are enabled on the system at
+ installation time will be used. You may override this default with any
of the following:
.
- all - use both ipv4 and ipv6 addresses
- .
- ipv6 - listen only on ipv6 addresses
- .
- ipv4 - listen only on ipv4 addresses
+ all : use both IPv4 and IPv6 addresses;
+ ipv6: listen only on IPv6 addresses;
+ ipv4: listen only on IPv4 addresses.
Template: postfix/recipient_delim
Type: string
Default: +
-_Description: Local address extension character?
- What character defines a local address extension?
+_Description: Local address extension character:
+ Please choose the character that will be used to define a local address
+ extension.
.
To not use address extensions, leave the string blank.
Template: postfix/bad_recipient_delimiter
-Type: note
+Type: error
_Description: Bad recipient delimiter
- The recipient delimiter is a single character, you entered too many
- characters. Please try again.
- .
- "${enteredstring}"
+ The recipient delimiter must be a single character. "${enteredstring}"
+ is what you entered.
Template: postfix/chattr
Type: boolean
Default: false
_Description: Force synchronous updates on mail queue?
- If synchronous updates are forced (yes), then mail is processed more slowly.
- If not forced (no), then there is a remote chance of losing some mail if
+ If synchronous updates are forced, then mail is processed more slowly.
+ If not forced, then there is a remote chance of losing some mail if
the system crashes at an inopportune time, and you are not using a
journaled filesystem (such as ext3).
- .
- The default is "no".
Template: postfix/mynetworks
Type: string
Default: 127.0.0.0/8
-_Description: Local networks?
- For what network blocks should this machine relay mail? The default is
- just the local host, which is needed by some mail user agents.
+_Description: Local networks:
+ Please specify the network blocks for which this host should relay mail.
+ The default is just the local host, which is needed by some mail user agents.
.
- If this is a smarthost for a block of machines, you need to specify the
+ If this host is a smarthost for a block of machines, you need to specify the
netblocks here, or mail will be rejected rather than relayed.
.
- To use the postfix default (which is based on connected networks), enter
+ To use the postfix default (which is based on the connected subnets), enter
an empty string.
Template: postfix/mailbox_limit
Type: string
Default: 0
-_Description: Mailbox size limit
- What limit should Postfix place on mailbox files to prevent runaway
- software errors. A value of zero (0) means no limit. (The upstream
- default is 51200000.)
+_Description: Mailbox size limit:
+ Please specify the limit that Postfix should place on mailbox files
+ to prevent runaway software errors. A value of zero (0) means no
+ limit. The upstream default is 51200000.
Template: postfix/root_address
Type: string
Default:
-_Description: Where should mail for root go
- The user root (and any other users with a uid of 0) must have mail
- redirected via an alias, or their mail may be delivered to
- /var/mail/nobody. This is by design: mail is not delivered to external
- delivery agents as root.
+_Description: Root and postmaster mail recipient:
+ Mail for the "postmaster", "root", and other system accounts needs to
+ be redirected to the user account of the actual system administrator.
.
- If you already have a /etc/aliases file, then you may need to add this
- entry. (The entry will only be added if the file /etc/aliases is created.)
+ If this value is left empty, such mail will be saved in /var/mail/nobody,
+ which is not recommended.
+ .
+ Mail is not delivered to external delivery agents as root.
.
- What address should be added to /etc/aliases, if the file is created?
- (Leave this blank to not add one.)
+ If you already have a /etc/aliases file, then you may need to add this
+ entry. Leave this blank to not add one.
Reply to: