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

[LCFC2] templates://exim4/{exim4-base.templates,exim4-config.templates}



(2nd call after integrating Justin's comments which I missed)

This is the last call for comments for the review of debconf
templates for exim4.

The reviewed templates will be sent on Thursday, May 31, 2007 to the package
maintainer as a bug report and a mail will be sent to this list with
"[BTS]" as a subject tag.


-- 


Template: exim4/purge_spool
Type: boolean
Default: false
_Description: Remove undelivered mails in spool directory?
 There are mails in the Exim spool directory /var/spool/exim4/input which
 have not yet been delivered. Removing Exim will cause them to remain
 undelivered until Exim is re-installed.
 .
 If this option is not chosen, the spool directory is kept, allowing
 the messages in the queue to be delivered at a later date after
 Exim is re-installed.

Template: exim4/move_exim3_spool
Type: boolean
Default: false
_Description: Move undelivered mails from Exim v3 to v4 spool?
 There are some undelivered mails in the old spool
 directory /var/spool/exim/input/.
 .
 Choosing this option will move these messages to exim4's spool
 (/var/spool/exim4/input/) where they will be handled by exim4.
 .
 This works only one-way: Exim v4 can handle the v3 spool but not
 vice-versa. If you may need to revert to Exim v3, reject this option.
 Instead, move the messages yourself after your upgrade to v4 has
 become permanent.

Template: exim4-base/drec
Type: error
_Description: Reconfigure exim4-config instead of this package
 Exim has its configuration factored out into a dedicated package,
 exim4-config. To reconfigure Exim, use 'dpkg-reconfigure exim4-config'.
Template: exim4/dc_eximconfig_configtype
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: internet site; mail is sent and received directly using SMTP, mail sent by smarthost; received via SMTP or fetchmail, mail sent by smarthost; no local mail, local delivery only; not on a network, no configuration at this time
Default: local delivery only; not on a network
_Description: General type of mail configuration:
 Please select the mail server configuration type that best meets your needs.
 .
 Systems with dynamic IP addresses, including dialup systems, should generally
 be configured to send outgoing mail to another machine, called a 'smarthost'
 for delivery because many receiving systems on the Internet block
 incoming mail from dynamic IP addresses as spam protection.
 .
 A system with a dynamic IP address can receive its own mail, or local
 delivery can be disabled entirely (except mail for root and postmaster).

Template: exim4/no_config
Type: boolean
Default: true
_Description: Really leave the mail system unconfigured?
 Until the mail system is configured, it will be broken and cannot be
 used. Configuration at a later time can be done either by hand or by
 running 'dpkg-reconfigure exim4-config' as root.

Template: exim4/mailname
Type: string
_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, fully qualified domain name (FQDN).
 .
 Thus, if a mail address on the local host is foo@example.org,
 the correct value for this option would be example.org.

Template: exim4/dc_other_hostnames
Type: string
Default: 
_Description: Other destinations for which mail is accepted:
 Please enter a semicolon-separated list of recipient domains for
 which this machine should consider itself the final destination,
 apart from the local hostname (${fqdn}) and 'localhost'. These
 domains are commonly called 'local domains'.
 .
 Leaving this list blank will have Exim do no local deliveries.
 .
 By default all local domains will be treated identically. If both
 a.example and b.example are local domains, acc@a.example and
 acc@b.example will be delivered to the same final destination. If
 different domain names should be treated differently, it is
 necessary to edit the config files afterwards.

Template: exim4/dc_relay_domains
Type: string
Default: 
_Description: Domains to relay mail for:
 Please enter a semicolon-separated list of recipient domains for
 which this system will relay mail, for example as a fallback MX or
 mail gateway. This means that this system will accept mail for these
 domains from anywhere on the Internet and deliver them according to
 local delivery rules.
 .
 Do not mention local domains here. Wildcards may be used.

Template: exim4/dc_relay_nets
Type: string
Default: 
_Description: Machines to relay mail for:
 Please enter a semicolon-separated list of IP address ranges for
 which this system will unconditionally relay mail, functioning as a
 smarthost.
 .
 You should use the standard address/prefix format (e.g. 194.222.242.0/24
 or 5f03:1200:836f::/48).
 .
 If this system should not be a relay for any other host, leave
 this list blank.

Template: exim4/dc_readhost
Type: string
_Description: Visible domain name for local users:
 The option to hide the local mail name in outgoing mail was enabled.
 It is therefore necessary to specify the domain name this system
 should use for the domain part of local users' sender addresses.

Template: exim4/dc_smarthost
Type: string
_Description: IP address or host name of the outgoing smarthost:
 Please enter the IP address or the host name of a mail server that
 this system should use as outgoing smarthost. If the smarthost only
 accepts your mail on a port different from TCP/25, append two colons
 and the port number (for example smarthost.example::587 or
 192.168.254.254::2525). Colons in IPv6 addresses need to be doubled.
 .
 If the smarthost requires authentication, please refer to
 /usr/share/doc/exim4-base/README.Debian.gz for notes about
 setting up SMTP authentication.

Template: exim4/dc_postmaster
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/mail,
 which is not recommended.
 .
 Note that postmaster's mail should be read on the system to which it is
 directed, rather than being forwarded elsewhere, so (at least one of)
 the users listed here should not redirect their mail off this machine.
 A 'real-' prefix can be used to force local delivery.
 .
 Multiple user names need to be separated by spaces.

Template: exim4/dc_noalias_regenerate
Type: boolean
Default: false
_Description: Overwrite existing /etc/aliases?
 An /etc/aliases file was found on the system, but it does not redirect
 mail for root to a user account, which is strongly recommended.
 .
 Accepting this option will cause /etc/aliases to be overwritten, and
 the old file will be renamed to aliases.O.

Template: exim4/dc_local_interfaces
Type: string
Default: notset
_Description: IP-addresses to listen on for incoming SMTP connections:
 Please enter a semicolon-separated list of IP addresses. The Exim SMTP
 listener daemon will listen on all IP addresses listed here.
 .
 An empty value will cause Exim to listen for connections on all
 available network interfaces.
 .
 If this system only receives mail directly from local services like
 fetchmail or your mail program (MUA) talking to localhost (and not
 from other hosts), it is advisable to prohibit external connections to
 the local Exim. This can be accomplished by entering 127.0.0.1 here.
 This will disable listening on public network interfaces.

Template: exim4/dc_minimaldns
Type: boolean
Default: false
_Description: Keep number of DNS-queries minimal (Dial-on-Demand)?
 In normal mode of operation Exim does DNS lookups at startup, and when
 receiving or delivering messages. This is for logging purposes and
 allows keeping down the number of hard-coded values in the
 configuration.
 .
 If this system does not have a DNS full service resolver available at
 all times (for example if its Internet access is a dial-up line using
 dial-on-demand), this might have unwanted consequences. For example,
 starting up Exim or running the queue (even with no messages waiting)
 might trigger a costly dial-up-event.
 .
 This option should be selected if this system is using Dial-on-Demand.
 If it has always-on Internet access, this option should be disabled.

Template: exim4/exim4-config-title
Type: title
_Description: Mail Server configuration

Template: exim4/use_split_config
Type: boolean
_Description: Split configuration into small files?
 The Debian exim4 packages can either use 'unsplit configuration', a
 single monolithic file (/etc/exim4/exim4.conf.template) or 'split
 configuration', where the actual Exim configuration files are built
 from about 50 smaller files in /etc/exim4/conf.d/.
 .
 Unsplit configuration is better suited for large modifications and is
 generally more stable, whereas split configuration offers a comfortable
 way to make smaller modifications but is more fragile and might break
 if modified carelessly.
 .
 A more detailed discussion of split and unsplit configuration can be
 found in /usr/share/doc/exim4-base/README.Debian.gz.

Template: exim4/hide_mailname
Type: boolean
_Description: Hide local mail name in outgoing mail?
 The headers of outgoing mail can be rewritten to make it appear to have been
 generated on a different system. If this option is chosen,
 '${mailname}', 'localhost' and '${dc_other_hostnames}' in From, Reply-To,
 Sender and Return-Path are rewritten.

Template: exim4/dc_localdelivery
Type: select
__Choices: mbox format in /var/mail/, Maildir format in home directory
Default: mbox format in /var/mail/
_Description: Delivery method for local mail:
 Exim is able to store locally delivered email in different formats.
 The most commonly used ones are mbox and Maildir. mbox uses a single
 file for the complete mail folder stored in /var/mail/. With Maildir
 format every single message is stored in a separate file in ~/Maildir/.
 .
 Please note that most mail tools in Debian expect the local delivery
 method to be mbox in their default.
Source: exim4
Section: mail
Priority: standard
Maintainer: Exim4 Maintainers <pkg-exim4-maintainers@lists.alioth.debian.org>
Uploaders: Andreas Metzler <ametzler@debian.org>,Marc Haber <mh+debian-packages@zugschlus.de>
Standards-Version: 3.7.2
Build-Depends: dpatch (>=2.0.10), debhelper (>= 5), po-debconf, bzip2, docbook-xsl, xsltproc, lynx, docbook-xml, libpcre3-dev, libldap2-dev, libpam0g-dev, libident-dev, libdb4.3-dev, libxmu-dev, libxt-dev, libxext-dev, libx11-dev, libxaw7-dev, libpq-dev, libmysqlclient15-dev, libsqlite3-dev, libperl-dev, libgnutls-dev, libsasl2-dev

Package: exim4-base
Architecture: any
Priority: standard
Conflicts: exim, exim-tls, exim4-daemon-light (<<${Upstream-Version}), exim4-daemon-heavy (<<${Upstream-Version}), exim4-daemon-custom (<<${Upstream-Version})
Replaces: exim, exim-tls, exim4-daemon-light, exim4-daemon-heavy, exim4-daemon-custom
Depends: ${shlibs:Depends}, ${misc:Depends}, cron (>=3.0pl1-42), exim4-config (>=4.30) | exim4-config-2, adduser, netbase, lsb-base (>= 3.0-3)
Recommends: psmisc
Suggests: mail-reader, eximon4, exim4-doc-html|exim4-doc-info, gnutls-bin | openssl, file, libmail-spf-query-perl (>= 1.999-1)
Description: support files for all exim MTA (v4) packages
 Exim (v4) is a mail transport agent. exim4-base provides the support
 files needed by all exim4 daemon packages. You need an additional package
 containing the main executable. The available packages are:
 .
  exim4-daemon-light
  exim4-daemon-heavy
 .
 If you build exim4 from the source package locally, you can also
 build an exim4-daemon-custom package tailored to your own feature set.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Package: exim4-config
Architecture: all
Priority: standard
Provides: exim4-config-2
Conflicts: exim, exim-tls, exim4-config, exim4-config-2, bash (<< 2.05), exim4-daemon-light (<<4.63), exim4-daemon-heavy (<<4.63), ${MTA-Conflicts}
Depends: ${shlibs:Depends}, ${misc:Depends}, adduser
Description: configuration for the exim MTA (v4)
 Exim (v4) is a mail transport agent. exim4-config provides the configuration
 for the exim4 daemon packages. The configuration framework has been split
 off the main package to allow sites to replace the configuration scheme
 with their own without having to change the actual exim4 packages.
 .
 Sites with special configuration needs (having a lot of identically
 configured machines for example) can use this to distribute their own
 custom configuration via the packaging system, using the magic
 available with dpkg's conffile handling, without having to do local
 changes on all of these machines.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Package: exim4-daemon-light
Architecture: any
Priority: standard
Provides: mail-transport-agent
Conflicts: mail-transport-agent
Replaces: mail-transport-agent, exim4-base (<= 4.61-1)
Depends: exim4-base (>= ${Upstream-Version}), ${shlibs:Depends}, ${misc:Depends}
Description: lightweight exim MTA (v4) daemon
 Exim (v4) is a mail transport agent. This package contains the exim4
 daemon with only basic features enabled. It works well with the
 standard setups that are provided by Debian and includes support for
 TLS encryption and the dlopen patch to allow dynamic loading of a
 local_scan function.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Package: exim4
Architecture: all
Priority: standard
Depends: ${misc:Depends}, debconf (>= 1.4.69) | cdebconf (>= 0.39), exim4-base (>= ${Upstream-Version}), exim4-daemon-light | exim4-daemon-heavy | exim4-daemon-custom
Description: meta-package to ease exim MTA (v4) installation
 Exim (v4) is a mail transport agent. exim4 is the meta-package depending
 on the essential components for a basic exim4 installation.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Package: exim4-daemon-heavy
Architecture: any
Priority: optional
Provides: mail-transport-agent
Conflicts: mail-transport-agent
Replaces: mail-transport-agent, exim4-base (<= 4.61-1)
Depends: exim4-base (>= ${Upstream-Version}), ${shlibs:Depends}, ${misc:Depends}
Description: exim MTA (v4) daemon with extended features, including exiscan-acl
 Exim (v4) is a mail transport agent. This package contains the exim4
 daemon with extended features. In addition to the features already
 supported by exim4-daemon-light, exim4-daemon-heavy includes LDAP,
 sqlite, PostgreSQL and MySQL data lookups, SASL and SPA SMTP authentication,
 embedded Perl interpreter, and the content scanning extension
 (formerly known as "exiscan-acl") for integration of virus scanners
 and spamassassin.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Package: exim4-daemon-custom
Architecture: any
Priority: optional
Provides: mail-transport-agent
Conflicts: mail-transport-agent
Replaces: mail-transport-agent, exim4-base (<= 4.61-1)
Depends: exim4-base (>= ${Upstream-Version}), ${shlibs:Depends}, ${misc:Depends}
Description: custom exim MTA (v4) daemon with locally set features
 Exim (v4) is a mail transport agent. This package contains a
 custom-configured exim4 daemon compiled to local needs. This package
 is not part of official Debian, but can easily be built from the
 Debian source package. For information about the feature set compiled in,
 and for bug reports, please find out who built your package.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Package: eximon4
Architecture: any
Priority: optional
Conflicts: eximon
Replaces: eximon
Depends: ${shlibs:Depends}, exim4-base (>= 4.10)
Description: monitor application for the exim MTA (v4) (X11 interface)
 Eximon is a helper program for the exim MTA (v4). It allows
 administrators to view the mail queue and logs, and perform a variety
 of actions on queued messages, such as freezing, bouncing and thawing
 messages.
 .
  Homepage: http://www.exim.org/

Package: exim4-dbg
Architecture: any
Priority: extra
Depends: exim4-base, exim4-config, eximon4
Description: debugging symbols for the exim MTA (v4) packages
 Exim (v4) is a mail transport agent. This package contains
 debugging symbols for the binaries contained in the exim4
 packages. The daemon packages have their own debug package.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Package: exim4-daemon-light-dbg
Architecture: any
Priority: extra
Depends: exim4-daemon-light
Description: debugging symbols for the exim MTA (v4) packages
 Exim (v4) is a mail transport agent. This package contains dbg
 debugging symbols for the binaries contained in the
 exim4-daemon-light package.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Package: exim4-daemon-heavy-dbg
Architecture: any
Priority: extra
Depends: exim4-daemon-heavy
Description: debugging symbols for the exim MTA (v4) packages
 Exim (v4) is a mail transport agent. This package contains dbg
 debugging symbols for the binaries contained in the
 exim4-daemon-heavy package.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Package: exim4-daemon-custom-dbg
Architecture: any
Priority: extra
Depends: exim4-daemon-custom
Description: debugging symbols for the exim MTA (v4) packages
 Exim (v4) is a mail transport agent. This package contains dbg
 debugging symbols for the binaries contained in the
 exim4-daemon-custom package.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Package: exim4-dev
Architecture: any
Priority: extra
Description: header files for the exim MTA (v4) packages
 Exim (v4) is a mail transport agent. This package contains header
 files that can be used to compile code that is then dynamically linked
 to exim's local_scan interface.
 .
 The Debian exim4 packages have their own web page,
 http://pkg-exim4.alioth.debian.org/. There is also a Debian-specific
 FAQ list. Information about the way the Debian packages are
 configured can be found in
 /usr/share/doc/exim4-base/README.Debian.gz, which additionally contains
 information about the way the Debian binary packages are built. The
 very extensive upstream documentation is shipped in
 /usr/share/doc/exim4-base/spec.txt.gz. To repeat the debconf-driven
 configuration process in a standard setup, invoke dpkg-reconfigure
 exim4-config. There is a Debian-centered mailing list,
 pkg-exim4-users@lists.alioth.debian.org. Please ask Debian-specific
 questions there, and only write to the upstream exim-users mailing
 list if you are sure that your question is not Debian-specific. You
 can find the subscription web page on
 http://lists.alioth.debian.org/mailman/listinfo/pkg-exim4-users
 .
  Homepage: http://www.exim.org/

Attachment: signature.asc
Description: Digital signature


Reply to: