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?
 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).
 .
 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/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/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.
 .
 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?

Template: postfix/main_mailer_type
Type: select
_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.
 .
 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.

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
 a later date, or configure it yourself by:
 .
 1) Editing /etc/postfix/main.cf to your liking
 .
 2) 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).
 .
 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.

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.

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.
 .
 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?
 Do 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?
 What character defines a local address extension?
 .
 To not use address extensions, leave the string blank.

Template: postfix/bad_recipient_delimiter
Type: note
_Description: Bad recipient delimiter
 The recipient delimiter is a single character, you entered too many
 characters.  Please try again.
 .
 "${enteredstring}"

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
 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.
 .
 If this 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
 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.)

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.
 .
 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.)
 .
 What address should be added to /etc/aliases, if the file is created?
 (Leave this blank to not add one.)