Ville Walveranta wrote:
On Sat, Nov 8, 2008 at 6:19 PM, Wietse Venema <[EMAIL PROTECTED]> wrote:
Postfix uses the names that YOU specify. It does not
magically rename things.
From the MASTER(5):
" The service name is specified as host:port,
" denoting the host and port on which new con-
" nections should be accepted. The host part
" (and colon) may be omitted. Either host or
" port may be given in symbolic form (host or
" service name) or in numeric form (IP address
" or port number). Host information may be
" enclosed inside "[]", but this form is not
" necessary.
If there is a service 192.168.1.10:smtp, can this be aliased to a
symbolic form (such as, in this example, "smptd1") so that it can more
easily referred to in main.cf, or is the name really
"192.168.1.10:smtp" as in 192.168.1.10:smtp_client_restrictions? :-)
Let's try again. Here is another example.
192.168.1.1 ... smtpd
-o smtpd_client_restrictions=${joe_client_restrictions}
-o smtpd_recipient_restrictions=${joe_recipient_restrictions}
-o foobar=${joe_foobar}
....
192.168.1.2 ... smtpd
-o smtpd_client_restrictions=${tagada_client_restrictions}
-o smtpd_recipient_restrictions=${tagada_recipient_restrictions}
-o foobar=${tagada_foobar}
...
now you can define
joe_.... = ....
and
tagada_.... = ...
in main.cf and use them in master.cf. These services will use any
smtpd_* config parametere except if you override it with -o ... as above.
look at it again, it has nothing to do with the service name, nor with
its order in master.cf, ... etc. Is it clear now?
