Your message dated Wed, 26 Dec 2012 11:50:39 +0100
with message-id <[email protected]>
and subject line Re: Bug#655020: exim4-config: missing features in Debian
configuration template
has caused the Debian Bug report #655020,
regarding exim4-config: missing features in Debian configuration template
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.)
--
655020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655020
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: exim4-config
Version: 4.77-1
Severity: minor
As I read exim documentation in detail, I realized upstream example file
as seen on Debian as /usr/share/doc/exim4-base/examples/example.conf.gz
in exim4-base package has:
| # Specify the location of the Exim server's TLS certificate and private key.
| # The private key must not be encrypted (password protected). You can put
| # the certificate and private key in the same file, in which case you only
| # need the first setting, or in separate files, in which case you need both
| # options.
|
| # tls_certificate = /etc/ssl/exim.crt
| # tls_privatekey = /etc/ssl/exim.pem
|
| # In order to support roaming users who wish to send email from anywhere,
| # you may want to make Exim listen on other ports as well as port 25, in
| # case these users need to send email from a network that blocks port 25.
| # The standard port for this purpose is port 587, the "message submission"
| # port. See RFC 4409 for details. Microsoft MUAs cannot be configured to
| # talk the message submission protocol correctly, so if you need to support
| # them you should also allow TLS-on-connect on the traditional but
| # non-standard port 465.
|
| # daemon_smtp_ports = 25 : 465 : 587
| # tls_on_connect_ports = 465
I do not see these in Debian template. i know they are not the same but some
synching may be good idea for exim4-config.
-- Package-specific info:
Exim version 4.77 #3 built 14-Nov-2011 22:30:32
--- End Message ---
--- Begin Message ---
On 2012-01-07 Osamu Aoki <[email protected]> wrote:
> Package: exim4-config
> Version: 4.77-1
> Severity: minor
> As I read exim documentation in detail, I realized upstream example file
> as seen on Debian as /usr/share/doc/exim4-base/examples/example.conf.gz
> in exim4-base package has:
> | # Specify the location of the Exim server's TLS certificate and private key.
> | # The private key must not be encrypted (password protected). You can put
> | # the certificate and private key in the same file, in which case you only
> | # need the first setting, or in separate files, in which case you need both
> | # options.
> |
> | # tls_certificate = /etc/ssl/exim.crt
> | # tls_privatekey = /etc/ssl/exim.pem
MAIN_TLS_CERTIFICATE / MAIN_TLS_PRIVATEKEY.
> | # In order to support roaming users who wish to send email from anywhere,
> | # you may want to make Exim listen on other ports as well as port 25, in
> | # case these users need to send email from a network that blocks port 25.
> | # The standard port for this purpose is port 587, the "message submission"
> | # port. See RFC 4409 for details. Microsoft MUAs cannot be configured to
> | # talk the message submission protocol correctly, so if you need to support
> | # them you should also allow TLS-on-connect on the traditional but
> | # non-standard port 465.
> |
> | # daemon_smtp_ports = 25 : 465 : 587
> | # tls_on_connect_ports = 465
These are indeed not listed. However the default value works for many
setups, and main configuration option like this one are easily set
locally, even without editing dpkg-conffiles
(/etc/exim4/exim4.conf.localmacros).
> I do not see these in Debian template. i know they are not the same but some
> synching may be good idea for exim4-config.
We keep them roughly in sync. There is build-time check which triggers
automatically when the upstream template changes to make sure we do
not miss changes.
I am closing this report, as it seems to be of wishlist nature.
cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
