1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
|
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(1) 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/relay_restrictions_warning
Type: boolean
_Description: Set smtpd_relay_restrictions in main.cf for upgrade?
Postfix version 2.10 adds smtpd_relay_restrictions, to separate relaying
restrictions from recipient restrictions, and you have a non-default value
for smtpd_recipient_restrictions.
.
Failure to do this may result in deferred or bounced mail after the
upgrade. Accept this option to set smtpd_relay_restrictions equal to
smtpd_recipient_restrictions.
Template: postfix/compat_conversion_warning
Type: boolean
Default: true
_Description: Update configuration to avoid compatibility warnings?
This upgrade of postfix changes some default values in the configuration. As
part of this upgrade, the following will be changed: (1) chrooted components
will be changed from '-' to 'y' in master.cf, and (2) myhostname will be set
to a fully-qualified domain name if it is not already such. The install will
be aborted if you do not allow the change.
Template: postfix/lmtp_retired_warning
Type: boolean
Default: true
_Description: Update master.cf for merged lmtp/smtp binary?
This upgrade of postfix drops the "lmtp" symlink, and your configuration
(master.cf) refers to it: lmtp was merged into smtp long ago. The install
will be aborted if you do not allow the change.
Template: postfix/main_cf_conversion_warning
Type: boolean
Default: true
_Description: Update main.cf for daemon_directory change?
This upgrade of postfix changes where daemons are located, and your postfix
configuration explicitly specifies the old location. The install will be
aborted if you do not allow the change.
Template: postfix/dynamicmaps_conversion_warning
Type: boolean
_Description: Update dynamicmaps.cf for 3.0?
Postfix version 3.0 changes how dynamic maps are delivered, and your
dynamicmaps.cf does not reflect that. Accept this option to convert
dynamicmaps.cf to the version required for 3.0.
Template: postfix/sqlite_warning
Type: boolean
_Description: Add 'sqlite' entry to dynamicmaps.cf?
Postfix version 2.9 adds sqlite support to maps, but your dynamicmaps.cf does
not reflect that. Accept this option to add support for sqlite maps.
Template: postfix/kernel_version_warning
Type: boolean
_Description: Install postfix despite an unsupported kernel?
Postfix uses features that are not found in kernels prior to 2.6. If you
proceed with the installation, Postfix will not run.
Template: postfix/retry_upgrade_warning
Type: boolean
_Description: Correct retry entry in master.cf for upgrade?
Postfix version 2.4 requires that the retry service be added to master.cf.
.
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.4 in this respect.
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 incorrect hostname entry?
The string '${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.'
.
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 with 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 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 'service postfix start'.
Template: postfix/mailname
Type: string
Default: /etc/mailname
#flag:comment:4
# Translators, please do NOT translate 'example.org' whch is registered
# as a domain name reserved for documentation as per RFC 2606
_Description: System mail name:
The "mail name" is the domain name used to "qualify" _ALL_ mail addresses
without a domain name. This includes mail to and from <root>: please do not
make your machine send out mail from root@example.org unless root@example.org
has told you to.
.
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: 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.
.
Do not specify more than one 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 relay host 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
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. '${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 [::ffff:127.0.0.0]/104 [::1]/128
_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.
The default includes local host for both IPv4 and IPv6. If just connecting
via one IP version, the unused value(s) may be removed.
.
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), leave
this blank.
Template: postfix/mailbox_limit
Type: string
Default: 0
_Description: Mailbox size limit (bytes):
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 and it does not have an entry
for root, then you should add this entry. Leave this blank to not add one.
Template: postfix/newaliases
Type: boolean
Default: false
_Description: Run newaliases command?
|
