Your message dated Sat, 19 Jul 2008 19:02:06 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#486116: fixed in exim4 4.69-6
has caused the Debian Bug report #486116,
regarding [exim4] README.Debian.xml with corrected typos and typography
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
486116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486116
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: exim4
Version: 4.69-5
Severity: wishlist
Tags: patch
--- Please enter the report below this line. ---
Dear DDs,
starting to get in touch with Exim, I read through README.Debian.xml and
tried to correct any mistakes I spotted. See the attached patch.
1. Since Lenny is supposed to support UTF-8 and thanks to NEO [1] I can
utilize the symbols easily, I changed those. Most notably the quotation
marks.
2. English is not my mother tongue. But I hope, I correctly remembered
some rules from school for some corrections I made.
3. I tried to get rid of abbreviations, since it is a written document.
(You’ll → You will, etc.)
4. In some cases package names are used. Are there any tags for
packages, that for example in the html output the package could be
linked to packages.debian.org?
Thanks a lot,
Paul
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.25-2-686
Debian Release: lenny/sid
500 unstable debian.tu-bs.de
--- Package information. ---
Depends (Version) | Installed
====================================-+-=============
debconf (>= 0.5) | 1.5.22
OR debconf-2.0 |
debconf (>= 1.4.69) | 1.5.22
OR cdebconf (>= 0.39) |
exim4-base (>= 4.69) | 4.69-5+b1
exim4-daemon-light | 4.69-5+b1
OR exim4-daemon-heavy |
OR exim4-daemon-custom |
Title: System mail name
Index: README.Debian.xml
===================================================================
--- README.Debian.xml (Revision 2294)
+++ README.Debian.xml (Arbeitskopie)
@@ -353,7 +353,7 @@
- The "mail name" is the domain name used to "qualify"
+ The "mail name" is the domain name used to “qualify”
mail addresses without a domain name.
@@ -379,7 +379,7 @@
The domain name used to qualify unqualified mail addresses
- is called ``mail name'' on Debian systems and entered
+ is called “mail name” on Debian systems and entered
in this debconf dialog. What you enter here will end
up in /etc/mailname, which is a
file that might be used by other programs as well.
@@ -422,7 +422,7 @@
Please enter a semicolon-separated list of recipient
domains for which this machine should consider itself
the final destination. These domains are commonly
- called 'local domains'. The local hostname and 'localhost'
+ called “local domains”. The local hostname and “localhost”
are always added to the list given here.
@@ -545,7 +545,7 @@
Delivery method for local mail
- Exim is able to store locally delivered email in
+ Exim is able to store locally delivered mail 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
@@ -748,7 +748,7 @@
The access lists delivered with the exim4 packages also
- contains quite a few configuration options that are too
+ contain quite a few configuration options that are too
restrictive to be active by default on a real-life site.
These are masked by .ifdef statements, can be activated by
setting the appropriate macros, and are documented in the
@@ -781,7 +781,7 @@
read before
/etc/exim4/exim4.conf.template. To
actually set the macro EXIM4_EXAMPLE to the
- value "this is a sample", write the following line
+ value “this is a sample”, write the following line
EXIM4_EXAMPLE = this is a sample
@@ -825,8 +825,8 @@
DCsmarthost, for example, is set to the
value of $dc_smarthost
in /etc/exim4/update-exim4.conf.conf
- which holds the answer to "Which machine will act as the
- smarthost and handle outgoing mail?"
+ which holds the answer to “Which machine will act as the
+ smarthost and handle outgoing mail?”
The result of these operations is saved as
@@ -844,10 +844,10 @@
script prior to any operation that may invoke an exim process,
and gives an error message if the generated config file is
syntactically invalid. If you want to activate your changes to
- files in conf.d/ just execute "invoke-rc.d exim4 restart".
+ files in conf.d/ just execute invoke-rc.d exim4 restart.
- How do I do minor tweaks to the configuration
+ How do I do minor tweaks to the configuration?
Some times, you want to do minor adjustments to the Exim
configuration to make Exim behave exactly like you want it
@@ -877,7 +877,7 @@
controlled by Exim macros. To find out about these, you
need basic understanding of Exim configuration. Just look
in our Exim configuration and see which macro needs to be
- set to a different value to alter Exim's behavior.
+ set to a different value to alter Exim’s behavior.
gives a closer explanation about
@@ -908,10 +908,10 @@
Using a completely different configuration scheme
If you are an experienced Exim administrator, you might feel
- like working with our pre-fabricated configuration
+ working with our pre-fabricated configuration
cumbersome and complex. You might feel right if you need to
make more complex changes and do not need to receive updates
- from us. This section is going to tell how about how to use
+ from us. This section is going to tell about how to use
your own configuration.
@@ -935,10 +935,10 @@
you can either take
/etc/exim4/exim4.conf.template,
run update-exim4.conf --keepcomments --output
- /etc/exim4/exim4.conf, or use Upstream's
+ /etc/exim4/exim4.conf, or use upstream’s
default configuration file that is installed as
/usr/share/doc/exim4-base/examples/example.conf.gz.
- You're going to lose all magic you get from packaging
+ You are going to lose all magic you get from packaging
though, so you need to be familiar with Exim to build
an actually working config.
@@ -960,9 +960,9 @@
pre-fabricated, static config file to
/etc/exim4/exim4.conf. This is
considered bad advice by the Debian maintainers since
- you're going to disable all updates and service magic
+ you are going to disable all updates and service magic
that Debian might deliver in the future this way. If
- you do not know exactly what you're doing here, this
+ you do not know exactly what you are doing here, this
is a bad choice. We try to comment on external HOWTOs
found on the web in the Debian
@@ -972,12 +972,12 @@
Replacing exim4-config with your own exim4 configuration package.
- We have split off Exim's configuration system (debconf,
- update-exim4.conf, and the files in
+ We split off Exim’s configuration system (debconf,
+ update-exim4.conf, and the files in
/etc/exim4/conf.d) to a separate
package, exim4-config. If you want to, you can replace
exim4-config by something entirely different. The other
- packages don't care. Your package needs to:
+ packages don not care. Your package needs to:
@@ -993,10 +993,10 @@
- Your package must provide an executable update-exim4.conf
- that must be in root's path (/usr/sbin recommended). The init
+ Your package must provide an executable update-exim4.conf
+ that must be in root’s path (/usr/sbin recommended). The init
script will invoke that executable prior to invoking the
- actual exim daemon. If you don't need that script, have it exit 0.
+ actual exim daemon. If you don not need that script, have it exit 0.
If you want to create your own configuration packages, there is a
@@ -1006,8 +1006,8 @@
The Exim 4 Debian svn repository holds sources for a
exim4-config-simple package which contains a simple, not
- debconf-driven configuration scheme as example which can
- be used as template for a classical, exim4.conf based
+ debconf-driven configuration scheme as an example which can
+ be used as a template for a classical, exim4.conf based
configuration scheme.
@@ -1017,22 +1017,22 @@
exim4-config-medium package which contains the conf.d
driven configuration of the main package with the
debconf interaction removed. This can be used to create
- you own non-debconf configuration package that uses the
+ your own non-debconf configuration package that uses the
conf.d mechanism.
Finally, you can invoke the script
- "debian/config-custom/create-custom-config-package"
+ debian/config-custom/create-custom-config-package
which will create a new source package
- "exim4-config-custom" with the debconf-driven config
+ “exim4-config-custom” with the debconf-driven config
scheme of exim4-config for your local modification.
Please note that exim4-config-simple and
- exim4-config-medium are only targetet to be used as
+ exim4-config-medium are only targetet to be used as a
template. The configurations contained are not
suitable for productive use. Of course, the Debian
maintainers appreciate any patches you might find
@@ -1050,7 +1050,7 @@
Exchanging the entire exim4-config package with
something custom comes particularly handy for sites
that have more than a few machines that are
- similarly configured, but don't want to use the
+ similarly configured, but do not want to use the
original exim4-config package. Build your own
exim4-config-custom or exim4-config-foo, and simply
apt that package to the machines that need to have
@@ -1084,7 +1084,7 @@
the server Exim connects to offers it.
- This means that you won't need any special configuration if
+ This means that you will not need any special configuration if
you want to use TLS for outgoing mail. However, if your
server setup mandates the use of client certificates, you
need to amend your remote_smtp and/or remote_smtp_smarthost
@@ -1128,7 +1128,7 @@
Outlook and Outlook Express, and Incredimail) insist on doing
TLS on connect on Port 465. If you need to support these, set
SMTPLISTENEROPTIONS='-oX 465:25 -oP /var/run/exim4/exim.pid'
- in /etc/default/exim4 and "tls_on_connect_ports=465" in the main
+ in /etc/default/exim4 and "tls_on_connect_ports=465" in the main
configuration section.
@@ -1137,11 +1137,11 @@
job will malfunction.
- It might be appropriate to add "+tls_cipher +tls_peerdn" to
+ It might be appropriate to add “+tls_cipher +tls_peerdn” to
any log_selector statement you might already have, or to add a
log_selector statement setting these two options in a local
configuration file. These options have Exim log what cipher
- your Exim and the peer's mailer have negotiated to use to
+ your Exim and the peer’s mailer have negotiated to use to
encrypt the transaction, and they have Exim log the
Distinguished Name of the peer's certificate.
@@ -1160,41 +1160,41 @@
This version of Exim is compiled against GnuTLS. GnuTLS is a
replacement for the restrictively licensed OpenSSL libraries.
GnuTLS does not support varying its Diffie-Hellman parameters.
- Therefore tls_dhparam settings are ignored in Exim's
+ Therefore tls_dhparam settings are ignored in Exim’s
configuration file, and no dhparam file is generated by
- exim-gencerts. GnuTLS uses D-H parameters that are
+ exim-gencerts. GnuTLS uses Diffie-Hellman parameters that are
computed when they are needed. When someone sends STARTTLS,
Exim will compute these parameters and then store these
- parameters in a cache file located in Exim's spool directory
+ parameters in a cache file located in Exim’s spool directory
(/var/spool/exim4/gnutls-params).
The daily cron job and the script
/usr/share/exim4/exim4_refresh_gnutls-params
- take care of new D-H parameters. If neither gnutls-bin nor
- openssl are installed, the gnutls-params file is removed and
- Exim re-generates the file on the fly during the next incoming TLS
+ take care of new Diffie-Helmann parameters. If neither gnutls-bin nor
+ openssl are installed, the gnutls-params file is removed and
+ Exim regenerates the file on the fly during the next incoming TLS
connection. Systems generating little entropy might hang in this
situation after clients invoking a STARTTLS command.
To avoid this behavior, which can possibly lead to a DoS
condition, if the daily cron job finds openssl or gnutls-bin
- installed, it will regenerate the gnutls-params file outside
- of Exim and only replace the gnutls-params file after a new
+ installed, it will regenerate the gnutls-params file outside
+ of Exim and only replace the gnutls-params file after a new
one has been successfully generated. If the new file
generation does not finish after an hour, the process is
killed to avoid sustained entropy depletion. If the
- gnutls-params file gets older than two weeks, the daily cron
+ gnutls-params file gets older than two weeks, the daily cron
job starts sending out warning messages.
- It is "more secure" when you have the gnutls-params file
+ It is “more secure” when you have the gnutls-params file
regenerated more often. You can delete it any time
you wish without any need for synchronization. Exim will
regenerate it automatically. Alternatively, you can manually invoke
/usr/share/exim4/exim4_refresh_gnutls-params
- to re-generate the file.
+ to regenerate the file.
NOTE! The fact that GnuTLS does not support generated
@@ -1222,16 +1222,16 @@
Insuffient entropy available is a frequent cause of TLS
- failures in Exim context. If Exim logs "not enough random bytes
- available", or simply hangs silently when an encrypted
+ failures in Exim context. If Exim logs “not enough random bytes
+ available”, or simply hangs silently when an encrypted
connection should be established, then Exim was
unable to read enough random data from /dev/random to do whatever
cryptographic operation is requested. Please check that
- your /dev/random device is setup properly.
+ your /dev/random device is setup properly.
A process that regularly consumes a lot of entropy is the
- re-generation of the Diffie-Hellman parameters. See
+ regeneration of the Diffie-Hellman parameters. See
for more information.
@@ -1258,7 +1258,7 @@
Using Exim as SMTP-AUTH client
If you want to set up Exim as SMTP AUTH client for delivery
- to your internet access provider's smarthost put the name of
+ to your internet access provider’s smarthost put the name of
the server, your login and password in
/etc/exim4/passwd.client. See the man
page for exim4-config_files(5) for more information about the
@@ -1328,7 +1328,7 @@
How the Exim daemon is started
- The Debian Exim 4 packages' init script is located in
+ The Debian Exim 4 packages’ init script is located in
/etc/init.d/exim4. Apart from the
functions that are required by Debian policy and the LSB, it
supports the commands what, which executes
@@ -1347,13 +1347,13 @@
Miscellaneous packaging issues
The daily cron job
- Exim4's daily cron job
+ Exim4’s daily cron job
(/etc/cron.daily/exim4-base)
does basic housekeeping tasks:
- It reads /etc/default/exim4, so you can use this
+ It reads /etc/default/exim4, so you can use this
file to change any of the variables used in the cron job.
@@ -1382,14 +1382,14 @@
so existing issues will be reported daily until
either the paniclog is rotated due to its sheer
size, or you manually move it away, for example by
- calling logrotate -f /etc/logrotate/exim4-paniclog
+ calling logrotate -f /etc/logrotate/exim4-paniclog
from a shell.
Just in case your system logs transient error
situations to the panic log as well (see, for
example,
- http://www.exim.org/bugzilla/show_bug.cgi?id=92),
+ Exim Bug 92),
you can configure
$E4BCD_PANICLOG_NOISE to a
regular _expression_. If the paniclog contains only
@@ -1413,10 +1413,10 @@
If TLS is enabled, it regenerates the GnuTLS
parameter file. If that process fails (maybe because
your system being short of entropy), and the
- gnutls-params file thus gets older than
+ gnutls-params file thus gets older than
$E4BCD_GNUTLS_PARAMS_MAXAGE, the
cron job logs this to syslog and sends out a warning
- e-mail to root.
+ message to root.
@@ -1437,9 +1437,9 @@
correctly (Just check the archived bug reports of Exim.)
and update-inetd seems to be unmaintained for a long
time, nobody dares to touch it. To quote Mark Baker, the
- maintainer of Exim (v3): "I really wish I had never used
+ maintainer of Exim (v3): “I really wish I had never used
inetd in the first place, but simply set up exim to run
- as a daemon, but it's too late to change that now."
+ as a daemon, but it’s too late to change that now.”
@@ -1448,7 +1448,7 @@
Running from inetd interferes with
- Exim's resource controls (e.g it disables
+ Exim’s resource controls (e.g it disables
smtp_accept_max_per_host and smtp_accept_max).
@@ -1462,7 +1462,7 @@
- Disable exim4's listening daemon by executing
+ Disable Exim 4’s listening daemon by executing
update-exim4defaults --queuerunner
queueonly
@@ -1502,17 +1502,17 @@
Handling incoming mail for local accounts with low UID
Since system accounts (mail, uucp, lp etc) are usually aliased
- to root, and root's mailbox is usually read by a human, these
+ to root, and root’s mailbox is usually read by a human, these
account names have started to be a common target for spammers.
- The Debian exim 4 packages have a mechanism to deal with this
+ The Debian Exim 4 packages have a mechanism to deal with this
situation. However, since this derives rather far from normal
behavior, it is disabled by default.
To enable it, set the macro FIRST_USER_UID to a numeric,
non-zero value. Incoming mail for local users that have a UID
- lower than FIRST_USER_UID is rejected with the message "no
- mail to system accounts". Incoming mail for local users that
+ lower than FIRST_USER_UID is rejected with the message “no
+ mail to system accounts”. Incoming mail for local users that
have a UID greater or equal FIRST_USER_UID are processed as
usual. Therefore, the default value of 0 ensures that the
mechanism is disabled. On Debian systems, setting
@@ -1524,7 +1524,7 @@
/etc/exim4/lowuid_aliases is an alias
file that is only honored for local accounts with UID lower
than FIRST_USER_UID. If you define an alias for such an
- account here, incoming e-mail is processed according to the
+ account here, incoming mail is processed according to the
alias. If you alias the account to itself, messages are
delivered to the account itself, which is an exception to the
rule that messages for low-UID accounts are rejected. The
@@ -1536,10 +1536,10 @@
Sometimes, it might be desireable to be able to bypass local
routing specialities like the alias file or a user-forward
- file. This is possible in the Debian exim4 packages by
- prefixing the account name with "real-". For a local account
- name "foo", "[EMAIL PROTECTED]" will result in direct
- delivery to foo's local Mailbox.
+ file. This is possible in the Debian Exim 4 packages by
+ prefixing the account name with “real-”. For a local account
+ name “foo”, [EMAIL PROTECTED] will result in direct
+ delivery to foo’s local mailbox.
This feature is by default only available for locally
@@ -1547,15 +1547,15 @@
messages delivered from remote as well, set the Exim macro
COND_LOCAL_SUBMITTER to true. If you do not want this at all,
set the macro to false. Please note that the userforward
- router uses this feature to get error messages (notifying the
- user of a syntax error in her .forward file) delivered.
+ router uses this feature to get error messages delivered, i. e., notifying the
+ user of a syntax error in her .forward file.
Using more complex deliveries from alias files
Delivery to arbitrary files, directory or to pipes in the
- /etc/aliases file is dsabled by default
- in the Debian exim 4 packages. The delivery process including the
+ /etc/aliases file is disabled by default
+ in the Debian Exim 4 packages. The delivery process including the
program being piped to would run as the exim admin-user
Debian-exim, which might open up security holes.
@@ -1615,9 +1615,9 @@
If any of your aliases expand to pipes or files or directories
you should set up a user and a group for these deliveries to run
- under. You can do this by setting the "user" and - if necessary
- - a "group" option and adding a "group" option if necessary.
- Alternatively, you can specify "user" and/or "group" on the
+ under. You can do this by setting the “user” and—if necessary—
+ a “group” option and adding a “group” option if necessary.
+ Alternatively, you can specify “user” and/or “group” on the
transports that are used.
@@ -1640,9 +1640,9 @@
rmail is the oldest way to transfer mail to a remote system.
However, today it is normally required to use addresses with
- full domains for that (well, they look like any normal address
- for you, and we don't tell about the other way to not confuse
- you ;). If you want this, you can use this transport:
+ full domains for that (Well, they look like any normal address
+ for you, and we do not tell about the other way to not confuse
+ you ;).) If you want this, you can use this transport:
rmail:
@@ -1655,7 +1655,7 @@
However, all recipients are handled via the command line, so
- you're discouraged to use it.
+ you are discouraged to use it.
bsmtp/rsmtp
@@ -1666,8 +1666,8 @@
batched SMTP or short bsmtp.
- Furthermore, this way won't fail on addresses like "
- "@do.main. If you want this, please use this, if the remote
+ Furthermore, this way will not fail on addresses like “
+ [EMAIL PROTECTED] If you want this, please use this, if the remote
site uses rsmtp (e.g. is Exim 4):
@@ -1703,7 +1703,7 @@
You need a router to tell Exim 4 which mails to forward to
UUCP. You can use this one; please adopt the last line. Of
- course, it's also possible to send mail via more than one way.
+ course, it is also possible to send mail via more than one way.
uucp_router:
@@ -1725,8 +1725,8 @@
If you have a leaf system (i.e. all your mail not for your
local system goes to a single remote system), you can just
forward all non-local mail to the remote UUCP system. In
- this case, you can replace "domains = ..." with "domains = !
- +local_domains", but then you need also to replace
+ this case, you can replace “domains = …” with “domains = !
+ +local_domains”, but then you need also to replace
$domain_data in the transport by the UUCP-name of your
smarthost. The file /etc/exim4/uucp is
not needed in this case.
@@ -1758,7 +1758,7 @@
Updating from Exim 3
- If you use exim4-config from Debian, you'll
+ If you use exim4-config from Debian, you will
get the debconf based configuration scheme that is intended to
cover the majority of cases.
@@ -1770,7 +1770,7 @@
eximconfig on Exim 3 installation. These
answers are then taken as default values for the debconf based
configuration process. Be warned! eximconfig
- from the Exim 3 packages doesn't record the explicit answers
+ from the Exim 3 packages does not record the explicit answers
given on Exim 3 configuration. So we have to guess the answers
from the Exim 3 configuration file
/etc/exim/exim.conf, which is bound to fail
@@ -1778,7 +1778,7 @@
eximconfig.
- This is the reason why we refrained from doing a "silent update", but
+ This is the reason why we refrained from doing a “silent update”, but
only use the guessed answers to get reasonable defaults for our
debconf based configuration process.
@@ -1792,7 +1792,7 @@
If you have used a customized Exim 3 configuration, you can of
course use exim_convert4r4, and install the
resulting file as /etc/exim4/exim4.conf
- after careful inspection. Exim4 will then use that file and
+ after careful inspection. Exim 4 will then use that file and
ignore the file that it generated from the debconf
configuration. To aid future updates, we do, however, encourage
you not to use the
@@ -1805,11 +1805,11 @@
PAM
PAM: On Debian systems the PAM modules run as the same user
- as the calling program, so they can't do anything you
- couldn't do yourself, and in particular can't access
+ as the calling program, so they cannot do anything you
+ could not do yourself, and in particular cannot access
/etc/shadow unless the user is in group
- shadow. - If you want to use
- /etc/shadow for Exim's SMTP AUTH you
+ shadow.—If you want to use
+ /etc/shadow for Exim’s SMTP AUTH you
will need to run exim as group shadow. Only
exim4-daemon-heavy is linked against libpam. We suggest using
saslauthd instead.
@@ -1818,22 +1818,22 @@
Account name restrictions
In the default configuration, Exim cannot locally deliver
- e-mails to accounts which have capitals in their name. This is
+ mail to accounts which have capitals in their name. This is
caused by the fact that Exim converts the local part of incoming
- e-mail to lower case before the comparision done by the
+ mail to lower case before the comparision done by the
check_local_user directive in routers is done.
The router option caseful_local_part can be used to control
this, and we decided not to set this option in the Debian
- configuration since it would be a rather big change to Exim's
+ configuration since it would be a rather big change to Exim’s
default behavior.
No deliveries to root!
- No Exim4 version released with any Debian OS can run
- deliveries as root. If you don't redirect mail for root via
+ No Exim 4 version released with any Debian OS can run
+ deliveries to root. If you do not redirect mail for root via
/etc/aliases to a nonprivileged
account, the mail will be delivered to
/var/mail/mail with permissions 0600 and
@@ -1888,7 +1888,7 @@
- Marc Merlin's Exim 4 Page has a lot of ACL
+ Marc Merlin’s Exim 4 Page has a lot of ACL
examples.
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
--- End Message ---
--- Begin Message ---
Source: exim4
Source-Version: 4.69-6
We believe that the bug you reported is fixed in the latest version of
exim4, which is due to be installed in the Debian FTP archive:
exim4-base_4.69-6_i386.deb
to pool/main/e/exim4/exim4-base_4.69-6_i386.deb
exim4-config_4.69-6_all.deb
to pool/main/e/exim4/exim4-config_4.69-6_all.deb
exim4-daemon-heavy-dbg_4.69-6_i386.deb
to pool/main/e/exim4/exim4-daemon-heavy-dbg_4.69-6_i386.deb
exim4-daemon-heavy_4.69-6_i386.deb
to pool/main/e/exim4/exim4-daemon-heavy_4.69-6_i386.deb
exim4-daemon-light-dbg_4.69-6_i386.deb
to pool/main/e/exim4/exim4-daemon-light-dbg_4.69-6_i386.deb
exim4-daemon-light_4.69-6_i386.deb
to pool/main/e/exim4/exim4-daemon-light_4.69-6_i386.deb
exim4-dbg_4.69-6_i386.deb
to pool/main/e/exim4/exim4-dbg_4.69-6_i386.deb
exim4-dev_4.69-6_i386.deb
to pool/main/e/exim4/exim4-dev_4.69-6_i386.deb
exim4_4.69-6.diff.gz
to pool/main/e/exim4/exim4_4.69-6.diff.gz
exim4_4.69-6.dsc
to pool/main/e/exim4/exim4_4.69-6.dsc
exim4_4.69-6_all.deb
to pool/main/e/exim4/exim4_4.69-6_all.deb
eximon4_4.69-6_i386.deb
to pool/main/e/exim4/eximon4_4.69-6_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Metzler <[EMAIL PROTECTED]> (supplier of updated exim4 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 19 Jul 2008 19:56:36 +0200
Source: exim4
Binary: exim4-base exim4-config exim4-daemon-light exim4 exim4-daemon-heavy
exim4-daemon-custom eximon4 exim4-dbg exim4-daemon-light-dbg
exim4-daemon-heavy-dbg exim4-daemon-custom-dbg exim4-dev
Architecture: source i386 all
Version: 4.69-6
Distribution: unstable
Urgency: high
Maintainer: Exim4 Maintainers <[EMAIL PROTECTED]>
Changed-By: Andreas Metzler <[EMAIL PROTECTED]>
Description:
exim4 - metapackage to ease Exim MTA (v4) installation
exim4-base - support files for all Exim MTA (v4) packages
exim4-config - configuration for the Exim MTA (v4)
exim4-daemon-custom - custom Exim MTA (v4) daemon with locally set features
exim4-daemon-custom-dbg - debugging symbols for the Exim MTA (v4) packages
exim4-daemon-heavy - Exim MTA (v4) daemon with extended features, including
exiscan-ac
exim4-daemon-heavy-dbg - debugging symbols for the Exim MTA (v4) packages
exim4-daemon-light - lightweight Exim MTA (v4) daemon
exim4-daemon-light-dbg - debugging symbols for the Exim MTA (v4) packages
exim4-dbg - debugging symbols for the Exim MTA (v4) packages
exim4-dev - header files for the Exim MTA (v4) packages
eximon4 - monitor application for the Exim MTA (v4) (X11 interface)
Closes: 479466 480282 481638 481765 482319 482641 482714 482752 485384 486105
486106 486116 486667 489171
Changes:
exim4 (4.69-6) unstable; urgency=high
.
[ Debconf translations ]
* Malayalam. Closes: #479466
* Albanian. Closes: #480282
* Polish. Closes: #481638
* Vietnamese. Closes: #482641
* Turkish. Closes: #482714
* Brazilian Portuguese. Closes: #485384
* Finnish. Closes: #489171
.
[ Marc Haber ]
* Have timeout.pl print a meaningful error message if perl-modules
is not installed. Have exim4-base recommend perl-modules.
Thanks to Tom Schouten. Closes: #482319
* Create gnutls-params with mode 644 in the first place.
Thanks to Jean-Luc Coulon. Closes: #481765
* Replace ~/.rnd with $HOME/.rnd in exim_gencerts. Thanks to
Ross Boylan for noticing this.
* exim4-config.config: send hostname --fqdn stderr to /dev/null,
we handle errors properly. Thanks to Andrew Vaughan in #481597.
.
[ Andreas Metzler ]
* Fix typos/other errors in README.Debian.xml. Improve formatting.
(Thank's Georg Neis and Paul Menzel) Closes: #486105, #486106, #486116
* Revert fancy quoting in initscript. Closes: #486667,#482752
(fixes rc-bugs).
* [debian/control README.Debian.xml] Spelling fix ("metapackage" instead of
"meta-package"). Thank's lintian
Checksums-Sha1:
d6ed89a91b67cde2339eeca415fc39b3986f61d7 1570 exim4_4.69-6.dsc
805d0a62880d454f4461b3d6c080c9d9778e6b25 535911 exim4_4.69-6.diff.gz
a730513867d4ed7c0d682c2933ad2fdb9684e2f5 984378 exim4-base_4.69-6_i386.deb
460c45ef89e02aacff4515155481cc970e6187f8 97424 eximon4_4.69-6_i386.deb
217ee0ceabd7a71d64302c273d5d703ac94fca97 421052
exim4-daemon-light_4.69-6_i386.deb
e53747e70061d7f908a1a6ef07ebce58f781c7ef 468926
exim4-daemon-heavy_4.69-6_i386.deb
8a7b4ee8106bf9eaef01034eeb5b6e1b8bc6ef02 672192
exim4-daemon-light-dbg_4.69-6_i386.deb
33bb64fc3ddb158fd547f25e82614dac11c9ac55 757552
exim4-daemon-heavy-dbg_4.69-6_i386.deb
260e84c5d27de50f2a81742b538535a15c0fe85f 263336 exim4-dbg_4.69-6_i386.deb
f0f447dfcdc2c2131efb90edf7ba8f247ffa0b5b 69774 exim4-dev_4.69-6_i386.deb
015ad78fead938609147e37c71a8709a93b9c42d 335428 exim4-config_4.69-6_all.deb
d76caab1f1773eedcfb32eed76f7d5ad74d924ac 7094 exim4_4.69-6_all.deb
Checksums-Sha256:
62a25dfb68b0013a0945711132abf228ba849a5fd9e9478b80398acaf69031f5 1570
exim4_4.69-6.dsc
7edfec6eaaa3919f83e57e817f833906747af29c61a5cd0319cf0384e5c825f4 535911
exim4_4.69-6.diff.gz
16e38e5fdb41bdc1c5f4e251c50d084f413f3f4a8cddc39b7f39d1b30e0a8e5f 984378
exim4-base_4.69-6_i386.deb
6165d73c675a03a88bc7e0766d2695e6af8d6bd4c6e876ec222a0d6b290c5c1c 97424
eximon4_4.69-6_i386.deb
b433fded07039eb7d31bc7b15a71c81fd4e2c6fbbe8a3a0802d18d5152d0505d 421052
exim4-daemon-light_4.69-6_i386.deb
f495a46c27dd0c2c8d384be6e08a56a815bbcb52811d3531d5930af7635c6099 468926
exim4-daemon-heavy_4.69-6_i386.deb
b0f84de8392cf8c25ab3fda066b7beb6c0bb5587f003cfafee1395335aeeccd8 672192
exim4-daemon-light-dbg_4.69-6_i386.deb
602442dd9a1790649b8f4615069c75d332eb6c426b04ebc983cec3e204146dad 757552
exim4-daemon-heavy-dbg_4.69-6_i386.deb
7155b291be384621c55456d717d3a9eb5a40abb54e985dced36e5432a8caa64f 263336
exim4-dbg_4.69-6_i386.deb
077d2a917e84c68177ef270a7233da570b3fb4ccab2f09a47b207f46c3dc09d7 69774
exim4-dev_4.69-6_i386.deb
78cc01226f9cefec6ddb4960be01bbe61fb9dce1d241e740c0445b6cd6c5b6d4 335428
exim4-config_4.69-6_all.deb
b1c0d68f0e96fbe611cc24cfc93fa5a5c2edfdbf56fad1ae4af76893698eeed5 7094
exim4_4.69-6_all.deb
Files:
2872ab59ad0fd435cba092e5b86481a0 1570 mail standard exim4_4.69-6.dsc
bcd8460dd0796c7b61a6c666957a145b 535911 mail standard exim4_4.69-6.diff.gz
8b1483f1cda45518f358ddc3574450d9 984378 mail standard
exim4-base_4.69-6_i386.deb
60b9363b1e9706e72854b17fbc9ae0ed 97424 mail optional eximon4_4.69-6_i386.deb
d80156ab1d80675fa3d80387ec407435 421052 mail standard
exim4-daemon-light_4.69-6_i386.deb
5fac123844e979760b5f1e8caa4bca40 468926 mail optional
exim4-daemon-heavy_4.69-6_i386.deb
0517f842923bdb090216b6c62e8a2ea3 672192 mail extra
exim4-daemon-light-dbg_4.69-6_i386.deb
48a120afa79c61dea54a0baefd2c0440 757552 mail extra
exim4-daemon-heavy-dbg_4.69-6_i386.deb
4cfbef6d9c7b90e486c535c5b71003c0 263336 mail extra exim4-dbg_4.69-6_i386.deb
5c997cfba9c8f90627e12111179293c4 69774 mail extra exim4-dev_4.69-6_i386.deb
5f1b5b7b49dd24a1cb72e23c92644680 335428 mail standard
exim4-config_4.69-6_all.deb
ef5c523d5d031d3ac74c636f6312b4ad 7094 mail standard exim4_4.69-6_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIgjTtHTOcZYuNdmMRAv+lAJ9RCt793gZ8rkz+ml7XAMy37XOOKQCcCvhc
XNehXJ7mB3hA4cJXstTqKks=
=TILS
-----END PGP SIGNATURE-----
--- End Message ---
