Please find, for review, the debconf templates of postfix (sorry I now discover that I skipped the ITR step). Lamont, please also review the proposed changes yourself if you have time for this. I have plenty of them...and you might not agree with some. Please keep debian-l10n-english@lists.debian.org in answers. See the end of this mail for a general and some detailed rationales. Other reviewers, please review this carefully. Postfix templates are complicated and often used. Please read Rationale before sending your reviews. This review will last from Sunday, April 22, 2007 to Wednesday, May 02, 2007. Please send reviews as unified diffs (diff -u) against the original files. Comments about your proposed changes will be appreciated. Your review should be sent as an answer to this mail. When appropriate, I will send intermediate requests for review, with "[RFRn]" (n>=2) as a subject tag. When we will reach a consensus, I send a "Last Chance For Comments" mail with "[LCFC]" as a subject tag. Finally, the reviewed templates will be sent to the package maintainer as a bug report, and a mail will be sent to this list with "[BTS]" as a subject tag. Rationale: - some templates have *not* been reviewed at all. See comments. I just sent a bug report suggesting these templates to be removed. Depending on Lamont Jones (package maintainer) answer to this suggestion, we'll review them or not - I reduced the size of the main template (mail system type) significantly. This is because this templates exceeds the size of a standard 80x25 screen which makes it difficult to use with debconf and the dialog default interface. The template is probably still too big, though. This is a very though case. - I picked some wording in exim4 to make the package slightly consistent with it. - Other changes are mostly motivated by compliance with recommendations of the Developer's Reference - I noticed that lamont often does not use articles. This hurts my French sensitivity but I left several of them unchanged. Please comment. --
# Should be removed as it handles a transition from old versions
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.
# Should be removed as it handles a transition from old versions
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.
# Probably to keep
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: Too old 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.
# Should be removed as it handles a transition from old versions
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.
# Should be removed as it handles a transition from old versions
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?
# Should be removed as it handles a transition from old versions
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 "${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:
The mail is sent and received directly using SMTP.
Internet site using smarthost:
The 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.
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.
.
This name won't appear on From: lines of outgoing mails if rewriting
is enabled.
Template: postfix/destinations
Type: string
_Description: Other destinations to accept mail for (blank for none):
Please 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):
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 sued 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 while "${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 which this host should relay mail for.
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 networks), 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.
--- ../postfix.old/debian/templates 2007-04-18 08:07:20.925503483 +0200
+++ debian/templates 2007-04-22 09:42:40.814447792 +0200
@@ -1,4 +1,5 @@
+# Should be removed as it handles a transition from old versions
Template: postfix/dynamicmaps_upgrade_warning
Type: boolean
_Description: Correct dynamicmaps.cf for upgrade?
@@ -14,6 +15,7 @@
such configuration, and automatically make dynamicmaps.cf compatible with
Postfix 2.0.2 in this respect.
+# Should be removed as it handles a transition from old versions
Template: postfix/master_upgrade_warning
Type: boolean
_Description: Correct master.cf for upgrade?
@@ -24,36 +26,36 @@
configuration yourself. Accept this option to automatically make
master.cf compatible with Postfix 2.1 in this respect.
+# Probably to keep
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).
.
- 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: Too old 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.
- .
- 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.
+# Should be removed as it handles a transition from old versions
Template: postfix/nqmgr_upgrade_warning
Type: boolean
_Description: Correct master.cf for upgrade?
@@ -64,6 +66,7 @@
yourself. Accept this option to automatically make master.cf compatible
with Postfix 2.1 in this respect.
+# Should be removed as it handles a transition from old versions
Template: postfix/db_upgrade_warning
Type: boolean
Default: true
@@ -72,6 +75,7 @@
.
Do you want to automatically attempt the conversion?
+# Should be removed as it handles a transition from old versions
Template: postfix/transport_map_warning
Type: note
_Description: Transport map incompatibility
@@ -89,85 +93,78 @@
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 "${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."
.
- 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.
- .
- Satellite system - All mail is sent to another machine, called a "smart
- host" for delivery. No mail is received locally.
+_Description: General type of mail configuration:
+ Please select the mail server configuration type that best meets your needs.
.
- 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:
+ The mail is sent and received directly using SMTP.
+ Internet site using smarthost:
+ The 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.
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 be used by other programs besides Postfix; it should be the
- single, full domain name (FQDN) from which mail will appear to originate.
+ 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.
+ .
+ This name won't appear on From: lines of outgoing mails if rewriting
+ is enabled.
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 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.
+_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 +173,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 sued 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 while "${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 which this host should relay mail for.
+ 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 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.)
+_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.
.
- What address should be added to /etc/aliases, if the file is created?
- (Leave this blank to not add one.)
+ 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.
--- ../postfix.old/debian/control 2007-04-18 08:07:19.781493117 +0200
+++ debian/control 2007-04-22 09:42:11.522207825 +0200
@@ -13,7 +13,7 @@
Suggests: procmail, postfix-mysql, postfix-pgsql, postfix-ldap, postfix-pcre, sasl2-bin, libsasl2-modules, resolvconf, postfix-cdb
Conflicts: mail-transport-agent, smail, libnss-db (<< 2.2-3), postfix-tls
Provides: mail-transport-agent, postfix-tls
-Description: A high-performance mail transport agent
+Description: high-performance mail transport agent
${Description}
Package: postfix-ldap
@@ -22,7 +22,7 @@
Description: LDAP map support for Postfix
${Description}
.
- This provides support for LDAP maps in Postfix. If you plan to use LDAP maps
+ This provides support for LDAP maps in Postfix. If you plan to use LDAP maps
with Postfix, you need this.
Package: postfix-cdb
@@ -31,7 +31,7 @@
Description: CDB map support for Postfix
${Description}
.
- This provides support for CDB (constant database) maps in Postfix. If you
+ This provides support for CDB (constant database) maps in Postfix. If you
plan to use CDB maps with Postfix, you need this.
Package: postfix-pcre
@@ -41,7 +41,7 @@
${Description}
.
This provides support for PCRE (perl compatible regular expression) maps in
- Postfix. If you plan to use PCRE maps with Postfix, you need this.
+ Postfix. If you plan to use PCRE maps with Postfix, you need this.
Package: postfix-mysql
Architecture: any
@@ -65,11 +65,11 @@
Architecture: all
Section: devel
Depends: postfix (>= ${Upstream}-0), postfix (<< ${Upstream}.0-0)
-Description: Postfix loadable modules development environment
+Description: loadable modules development environment for Postfix
${Description}
.
This provides the headers and library links to build additional map
- types for Postfix. If you're not developing postfix modules, then you
+ types for Postfix. If you're not developing postfix modules, then you
do not need this.
Package: postfix-doc
@@ -77,7 +77,7 @@
Section: doc
Suggests: postfix
Replaces: postfix (<<0.0.20020113), postfix-tls
-Description: Postfix documentation
+Description: documentation for Postfix
${Description}
.
- This package provides documentation for Postfix.
+ This package provides the documentation for Postfix.
Source: postfix
Section: mail
Priority: extra
Maintainer: LaMont Jones <lamont@debian.org>
Standards-Version: 3.7.2.0
Build-Depends: debhelper (>= 4.1.16), po-debconf (>= 0.5.0), groff-base, patch, dpatch, lsb-release, libdb4.3-dev, libldap2-dev (>=2.1), libpcre3-dev, libmysqlclient15-dev|libmysqlclient14-dev, libssl-dev (>=0.9.7-1), libsasl2-dev, libpq-dev, libcdb-dev | tinycdb
Package: postfix
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, netbase, adduser (>=3.48), dpkg (>= 1.8.3), lsb-base (>=3.0-6), ssl-cert
Recommends: mail-reader
Replaces: postfix-doc (<<1.1.7-0), postfix-tls, mail-transport-agent
Suggests: procmail, postfix-mysql, postfix-pgsql, postfix-ldap, postfix-pcre, sasl2-bin, libsasl2-modules, resolvconf, postfix-cdb
Conflicts: mail-transport-agent, smail, libnss-db (<< 2.2-3), postfix-tls
Provides: mail-transport-agent, postfix-tls
Description: high-performance mail transport agent
${Description}
Package: postfix-ldap
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, postfix (= ${Source-Version})
Description: LDAP map support for Postfix
${Description}
.
This provides support for LDAP maps in Postfix. If you plan to use LDAP maps
with Postfix, you need this.
Package: postfix-cdb
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, postfix (= ${Source-Version})
Description: CDB map support for Postfix
${Description}
.
This provides support for CDB (constant database) maps in Postfix. If you
plan to use CDB maps with Postfix, you need this.
Package: postfix-pcre
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, postfix (= ${Source-Version})
Description: PCRE map support for Postfix
${Description}
.
This provides support for PCRE (perl compatible regular expression) maps in
Postfix. If you plan to use PCRE maps with Postfix, you need this.
Package: postfix-mysql
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, postfix (= ${Source-Version})
Description: MYSQL map support for Postfix
${Description}
.
This provides support for MYSQL maps in Postfix. If you plan to use MYSQL
maps with Postfix, you need this.
Package: postfix-pgsql
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, postfix (= ${Source-Version})
Description: PGSQL map support for Postfix
${Description}
.
This provides support for PGSQL maps in Postfix. If you plan to use PGSQL
maps with Postfix, you need this.
Package: postfix-dev
Architecture: all
Section: devel
Depends: postfix (>= ${Upstream}-0), postfix (<< ${Upstream}.0-0)
Description: loadable modules development environment for Postfix
${Description}
.
This provides the headers and library links to build additional map
types for Postfix. If you're not developing postfix modules, then you
do not need this.
Package: postfix-doc
Architecture: all
Section: doc
Suggests: postfix
Replaces: postfix (<<0.0.20020113), postfix-tls
Description: documentation for Postfix
${Description}
.
This package provides the documentation for Postfix.
Attachment:
signature.asc
Description: Digital signature