On Mon, 13 Jan 2003, Wietse Venema wrote:

> The -o feature should be used very sparingly.
>

Amen. I think that we need to lower the barrier to adoption of multiple
instances to make "-o" substantially obsolete.

With multiple instances and a fairly complex 1.1.X configuration I only
have combined the following "-o" options in three master.cf files:

  -o disable_dns_lookups=yes
  -o myhostname=localhost.$mydomain
  -o smtp_connect_timeout=$jarna_connect_timeout
  -o smtp_helo_timeout=$jarna_helo_timeout
  -o smtp_connect_timeout=$relay_connect_timeout

The first is obsolete with 2.0 ("smtp" no longer canonicalizes sender and
recipient domains). The second is the usual "localhost" trick for the
downstream "smtpd". The last three are timeout tweaks for custom "smtp"
transports. All can be eliminated if:

- An smtpd_hostname parameter is added, analogous to smtp_helo_name.
  I only have one "smtpd" per instance, so setting this in main.cf would
  be cleaner.

- The smtp_mumble parameters are first looked up as <transport>_mumble,
and only then as smtp_mumble.

I believe that all "-o" arguments in master.cf are workarounds for missing
features. It should IMHO be possible to configure all parameters in
main.cf.

-- 
	Viktor.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]