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
|
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 ~72 characters.
__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, manually convert from handcrafted Exim v3 configuration, no configuration at this time
_Description: General type of mail configuration:
Select the 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 "smart host"
for delivery. You can choose to receive mail on such a system; or to have no
local mail delivery, except mail for root and postmaster.
Template: exim4/exim3_upgrade
Type: boolean
Default: true
_Description: Configure Exim4 manually?
You indicated that you have a handcrafted Exim 3 configuration.
To convert this to Exim 4, you can use the exim_convert4r4(8) tool
after the installation. Consult
/usr/share/doc/exim4-base/examples/example.conf.gz and
/usr/share/doc/exim4-base/README.Debian.gz!
.
Until your mail system is configured, it will be broken and cannot be
used.
Template: exim4/no_config
Type: boolean
Default: true
_Description: Really leave the mail system unconfigured?
Until your mail system is configured, it will be broken and cannot be
used. You can of course configure it later, either by hand or by running
"dpkg-reconfigure exim4-config" as root.
Template: exim4/mailname
Type: string
_Description: System 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) unless
hidden with rewriting.
.
This name will be also be used by other programs; it should be the
single, full domain name (FQDN) from which mail will appear to originate.
.
This name won't appear on From: lines of outgoing mails if you enable
rewriting.
Template: exim4/dc_other_hostnames
Type: string
Default:
_Description: Other destinations for which mail is accepted:
Please enter a list of domains for which this machine should consider
itself the final destination, apart from the mail name (${mailname})
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
files afterwards.
.
If there are any more, enter them here, separated by colons. You may
leave this blank if there are none.
Template: exim4/dc_relay_domains
Type: string
Default:
_Description: Domains to relay mail for:
Please enter here the domains for which you accept to relay the mail.
.
Such domains are domains for which you are prepared to accept mail
from anywhere on the Internet. Do not mention local domains here.
.
The domains you enter here should be separated by colons. Wildcards
may be used.
Template: exim4/dc_relay_nets
Type: string
Default:
_Description: Machines to relay mail for:
Please enter here the networks of local machines for which you accept to
relay the mail.
.
This should include a list of all machines that will use us as a smarthost.
.
If there are any, enter them here, separated by colons. You should use
the standard address/length format (e.g. 194.222.242.0/24).
.
You need to double the colons in IPv6 addresses (e.g.
5f03::1200::836f::::/48)
Template: exim4/dc_readhost
Type: string
_Description: Visible domain name for local users:
Since you enabled hiding the local mailname in outgoing mail, you must
specify the 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: exim4/dc_smarthost
Type: string
_Description: Machine handling outgoing mail for this host (smarthost):
Enter the hostname of the machine to which outgoing mail is sent.
.
Refer to /usr/share/doc/exim4-base/README.SMTP-AUTH 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 is usually
redirected to the user account of the actual system administrator.
If you leave this value 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 you choose should not redirect their mail off this machine. Use
a "real-" prefix to force local delivery.
.
Enter one or more usernames separated by spaces.
Template: exim4/dc_noalias_regenerate
Type: boolean
Default: false
_Description: Overwrite existing /etc/aliases?
You already have an /etc/aliases file, but it does not redirect mail for
root to a user account, which is strongly recommended. If you accept
overwriting it, the old file will be kept and renamed to aliases.O.
Template: exim4/dc_local_interfaces
Type: string
Default: notset
_Description: IP-addresses to listen on for incoming SMTP connections:
Enter a colon-separated list of IP-addresses to listen on. You need to
double the colons in IPv6 addresses (e.g. 5f03::1200::836f::::).
.
If you leave this value empty, Exim will listen for connections on the SMTP
port of all available network interfaces.
.
If this computer does not receive e-mail directly per SMTP from OTHER
hosts, but only from local services like fetchmail or your e-mail program
(MUA) talking to localhost you should prohibit external connections to
Exim by setting this option to 127.0.0.1 and therefore disabling 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 makes DNS-lookups at startup, when
receiving or delivering message, etc. for logging purposes and to keep the
number of hard-coded values in the configuration file small.
.
If this were a host without permanent DNS-nameserver-access using
Dial-on-Demand this might have the unwanted consequence that starting up
exim or running the queue (even with no messages waiting) might trigger a
costly dial-up-event.
.
Enable this feature if you are using Dial-on-Demand; otherwise, disable it.
Template: exim4/exim4-config-title
Type: title
_Description: Configuring Exim v4 (exim4-config)
Template: exim4/use_split_config
Type: boolean
_Description: Split configuration into small files?
The Debian exim4 packages can either use a single monolithic file
(/etc/exim4/exim4.conf.template) or about 40 small files in
/etc/exim4/conf.d/ to generate the final configuration.
.
The former is better suited for large modifications and is generally
more stable, whereas the latter offers a comfortable way to make smaller
modifications but is more fragile and might break if modified
extensively.
.
If you are unsure then you should not use split configuration.
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, replacing "${mailname}" "localhost"
and "${dc_other_hostnames}" in From, Reply-To, Sender and Return-Path.
|
