Template: exim/configconvert/question
Type: select
Choices: convert, createnew, none
Description: Exim 3 configuration not compatible with Exim 4
 Your existing Exim 3 configuration in /etc/exim/exim.conf cannot be
 used by Exim 4. It is possible to try to convert your configuration file
 using a script, or you can build a new configuration file by answering
 a series of questions about your system.
 .
 As a third choice, you can leave Exim 4 unconfigured in case you want to
 write a configuration file yourself.

Template: exim/configconvert/convertnotice
Type: note
Description: Exim 3 configuration will be converted and put in exim4.conf
 Exim 4 cannot read an Exim 3 configuration file. An attempt has been made
 to convert your Exim 3 configuration file into an Exim 4 file, but this is
 not guaranteed to work in all cases.
 .
 Exim 4's configuration file is in /etc/exim4/exim4.conf; your original
 Exim 3 configuration file can still be found at /etc/exim/exim.conf, which
 will be ignored from now on.
 .
 If the configuration file is badly broken, Exim will now refuse to start.
 You should check your Exim configuration anyway to make sure that messages
 are still being delivered correctly.

Template: exim/configconvert/breakagenotice
Type: note
Description: Exim 4 is not configured
 Exim 4 has not been configured. You must write an Exim 4 configuration file
 as /etc/exim4/exim4.conf before Exim is usable. This host cannot
 send or receive email until this is done.

Template: exim/eximconfig/configtype
Type: select
Choices: internet, smarthost, satellite, local, none
Description: Which major configuration?
 You must choose one of the options below:
 .
 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. root and postmaster mail is delivered according 
 to /etc/aliases. No mail is received locally.
 .
 Local delivery only: You are not on a network.  Mail for local users 
 is delivered.
 .
 No configuration: No configuration will be done now; your mail system 
 will be broken and should not be used. You must then do the 
 configuration yourself later or run "dpkg-reconfigure exim"
 as root. Look in /usr/share/doc/exim/example.conf.gz

Template: exim/eximconfig/satellite_hostname
Type: string
Description: What is the hostname for this system?
 What is this system's name? It won't appear on From: lines of mail,
 as rewriting is used.

Template: exim/eximconfig/visible_hostname
Type: string
Description: What is the visible mail name of your system?
 This will appear on From: lines of outgoing messages.

Template: exim/eximconfig/syshostname
Type: string
Description: internal use only
 This value is only used internally-- this template is never displayed.

Template: exim/eximconfig/other_hostnames
Type: string
Description: What other domain names to recognise?
 Does this system have any other names which may appear on incoming
 mail messages, apart from the visible name (${visiblename}) and
 localhost?
 .
 By default all domains will be treated the same; if you want different 
 domain names to be treated differently, you will need to edit the config 
 file afterwards.
 .
 If there are any more, enter them here, separated with spaces or commas.  

Template: exim/eximconfig/relay_domains
Type: string
Description: Which domains to relay for?
 All mail from here or specified other local machines to anywhere on
 the internet will be accepted, as will mail from anywhere on the 
 internet to here. 
 .
 Are there any domains you want to relay mail for---that is, you are 
 prepared to accept mail for them from anywhere on the internet, but
 they are not local domains.
 .
 If there are any, enter them here, separated with spaces or commas. You
 can use wildcards. If you want to relay 
 mail for all domains that specify you as an MX, then say "mx".

Template: exim/eximconfig/relay_nets
Type: string
Description: Which machines to allow relaying for?
 Obviously, any machines that use us as a smarthost have to be excluded
 from the relaying controls, as using us to relay mail for them is the
 whole point.
 .
 Are there any networks of local machines you want to relay mail for?
 .
 If there are any, enter them here, separated with spaces or commas. You
 should use the standard address/length format (e.g. 194.222.242.0/24)
 .
 You need to double the colons in IPv6 addreses (e.g. 5f03::1200::836f::::/48)

Template: exim/eximconfig/readhost
Type: string
Description: Domain name for local users
 Since this is going to be a satellite system, I need to know what domain
 name to use for mail from local users; typically this is the machine on
 which you normally receive your mail.
 .
 Where will your users read their mail?

Template: exim/eximconfig/smarthost
Type: string
Description: Which machine will act as the smarthost and handle outgoing mail?
 Enter the hostname of the machine to send outgoing mail to.

Template: exim/eximconfig/postmaster
Type: string
Description: Who is to receive postmaster mail?
 Mail for the "postmaster" and "root" accounts is usually redirected
 to one or more user accounts, of the actual system administrators.
 By default, I'll set things up so that mail for "postmaster" and for
 various system accounts is redirected to "root", and mail for "root"
 is redirected to a real user.  This can be changed by editing /etc/aliases.
 .
 Note that postmaster-mail should usually be read on the system it is
 directed to, rather than being forwarded elsewhere, so (at least one of)
 the users you choose should not redirect their mail off this machine.
 .
 Which user account(s) should system administrator mail go to ?
 Enter one or more usernames separated by spaces or commas .  Enter
 "none" if you want to leave this mail in "root"'s mailbox - NB this
 is strongly discouraged.  Also, note that usernames should be lowercase!

Template: exim/eximconfig/overwrite_aliases
Type: boolean
Default: false
Description: Overwrite existing /etc/aliases?
 You already have an /etc/aliases file. Do you want to replace this with
 a new one (the old one will be kept and renamed to aliases.O)?

Template: exim/eximconfig/mailbox_format
Type: select
Choices: spool, maildir
Default: spool
Description: Where to store user mailboxes?
 The Debian default place to store user mail is in
 /var/spool/mail/$USER. However, you may wish to store it
 elsewhere. One popular choice (particularly with those migrating from
 qmail) is to store user mail in a "Maildir" in their home directory.
 .
 You can choose to store mail in the normal mail spool, or a
 home-directory Maildir.

Template: exim/eximconfig/auto_procmail
Type: boolean
Default: true
Description: Automatically use procmail to deliver mail?
 Do you want Exim to automagically deliver mail with procmail if:
 .
 a) it is installed, and
 .
 b) the target user has a ".procmailrc" file in their home directory.

Template: exim/eximconfig/auto_maildrop
Type: boolean
Default: true
Description: Automatically use maildrop to deliver mail?
 Do you want Exim to automagically deliver mail with maildrop if:
 .
 a) it is installed, and
 .
 b) the target user has a ".mailfilter" file in their home directory.

Template: exim/daemon/permissions
Type: select
Choices: setuid root, setuid mail, none
Default: setuid root
Description: Install Exim daemon with SUID bit set?
 Exim can be installed without extra privileges, setuid to mail (the
 Exim user), or setuid to root. The safe default is to install it
 setuid to root. Changing this can cause problems with usage of
 .forward files and mail delivery, depending on your setup.
 .
 Be sure to read Chapter 55 "Security considerations" of the Exim
 manual before you change this.