# The configuration file uses a set of rules to generate an
# acceptable mail environment for debian.org machines. It deviates
-# considerably from what could be considered a standard exim configuration.
+# considerably from what could be considered a standard Exim configuration.
# This configuration file brings in the necessary information from
# other databases stored in /etc/exim4/ and the files distributed by ud-ldap
# The configuration files in /etc/exim4 are as follows:
# locals - This is a list of domains that are considered local. A local
-# domain is essential one that deliveries to /var/mail
+# domain is essentially one for which deliveries to /var/mail
# will be attempted. The users available for local delivery
-# comes from /etc/passwd and /etc/aliases. Wildcards are not
+# come from /etc/passwd and /etc/aliases. Wildcards are not
# permitted.
# virtualdomains - This is a list of all virtual domains. A virtual domain
# is much like a local domain, execpt that the delivery location
# and allowed set of users is controlled by a virtual domain
# alias file and not /etc/passwd. Wildcards are permitted
# relayhosts - Hostnames that can send any arbitarily addressed mail to
-# us. This is primarily only usefull for emergancy 'queue
+# us. This is primarily only useful for emergency 'queue
# flushing' operations, but should be populated with a list
# of trusted machines. Wildcards are not permitted
# bsmtp_domains - Domains that we deliver locally via bsmtp
# elsewhere. This is designed for use with small volume or
# restricted machines that need to use a smarthost for mail
# traffic. We will relay for them based on ssl cert validation
-# but we need to teach exim how to route the mail to them. This is
+# but we need to teach Exim how to route the mail to them. This is
# that list.
<%- end -%>
# Further details can be found in each of the files.
-# Usefull exim commands:
+# Useful Exim commands:
# exim4 -qf - Try sending all messages right now, including frozen ones
-# exim4 -bt foo@blah - Write what exim would do if it saw the address
+# exim4 -bt foo@blah - Write what Exim would do if it saw the address
# Great for testing virtual domains and forward files
# Special Features for users:
# Heuristic check (none bad enough to cause a hard reject, but in aggregate
# will trigger things like rcpt to rate limiting or possibly a reject if
-# enough hits are triggered.
+# enough hits are triggered).
#
# value is stored in acl_c_scr
# Some operating systems use the "gecos" field in the system password file
# to hold other information in addition to users' real names. Exim looks up
# this field when it is creating "sender" and "from" headers. If these options
-# are set, exim uses "gecos_pattern" to parse the gecos field, and then
+# are set, Exim uses "gecos_pattern" to parse the gecos field, and then
# expands "gecos_name" as the user's name. $1 etc refer to sub-fields matched
# by the pattern.
gecos_pattern = ^([^,:]*)
gecos_name = $1
-# This tells exim to immediately discard error messages (ie double bounces).
+# This tells Exim to immediately discard error messages (ie double bounces).
ignore_bounce_errors_after = 0s
auto_thaw = 1d
timeout_frozen_after=14d
<%- end -%>
# Defer after too many bad RCPT TO's. Legit MTAs will retry later.
- # This is a rough pass at preventing addres harvesting or other mail blasts.
+ # This is a rough pass at preventing address harvesting or other mail blasts.
defer log_message = Too many bad recipients ${eval:$rcpt_fail_count} out of $rcpt_count
message = Too many bad recipients, try again later
# sadly. etch's version attempts to hold the socket open, since that's what
# postfix expects. Exim, on the other hand, expects the remote side to close
# the socket when it's finished sending data, so it see each transaction as
- # an incomplete read. I'm sure there's a way we could force exim to do
+ # an incomplete read. I'm sure there's a way we could force Exim to do
# something sick and clever to force either the interpretation or the socket
# closure, but I'm fairly sure it's now worth it, since the backport of
# policyd-weight is trivial.
#!!# ACL that is used after the DATA command
check_message:
- # Some people put from hostmaster@something.debian.org in the From
+ # Some people put from postmaster@something.debian.org in the From
# header. Take their crack pipe away.
drop condition = ${if match{${lc:$h_From:}}{\Npostmaster@([^.]+\.)?debian\.org\N}}
# current one gets passed on instead. This covers the case where A is
# aliased to B and B has a .forward file pointing to A.
-# For standard debian setup of one group per user, it is acceptable---normal
+# For standard Debian setup of one group per user, it is acceptable---normal
# even---for .forward to be group writable. If you have everyone in one
-# group, you should comment out the "modemask" line. Without it, the exim
+# group, you should comment out the "modemask" line. Without it, the Exim
# default of 022 will apply, which is probably what you want.
userforward_verify:
router_home_directory = ${lookup passwd{$local_part}{${extract{5}{:}{$value}}}fail}
verify_only
-# This is a senmailesque alias file lookup
+# This is a sendmailesque alias file lookup
virt_aliases:
debug_print = "R: virt_aliases for $local_part@$domain"
driver = redirect
headers_add = "Delivered-To: ${local_part}${local_part_suffix}@${domain}\nSubject: ${if and {{first_delivery}{match {$h_subject:}{(?i)(.*?)\\\\[?debian rt\\\\]?[:\\s]*(.*)}}} {$1$2}{$h_subject:}}"
<%- end -%>
-# exim4 fails the router if it can't change to the user/group for delivery
+# Exim fails the router if it can't change to the user/group for delivery
# during verification. So we have to seperate the cases of verifying
# the virts, and delivering to them. blah.
begin transports
-# This transport is used for local delivery to user mailboxes. On debian
+# This transport is used for local delivery to user mailboxes. On Debian
# systems group mail is used so we can write to the /var/mail
# directory. (The alternative, which most other unixes use, is to deliver
# as the user's own group, into a sticky-bitted directory)
projects / mirror / dsa-puppet.git / blobdiff