[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [RFR] templates://postfix/{templates}

On Mon, Apr 23, 2007 at 06:22:57PM +0200, Christian Perrier wrote:
> I suggest waiting for others reviewers to complete the review. That
> should last for about 10 days to give everybody a chance to comment.
> Of course, I'll take your comments and modify our review according to them...

And I forgot to attach the file.  sigh.

I don't currently have an urgent need to upload postfix:  I'll hold off
unless such a need arises.  Attached is the file as it currently exists
in source control.

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 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/kernel_version_warning
Type: boolean
_Description: Unsupported kernel.  Install postfix anyway?
 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 "${enteredstring}" string 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).
 For example, if a mail address on the local host is foo@domain.example,
 then the correct value for this option would be domain.example.

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
 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
_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
_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.

Reply to: