On Mon, 17 Jun 2002, Richard Lithvall wrote:
> According to the documentation qualify_domain only applies to
> locally-generated messages.
That's because only locally generated messages are permitted to supply
unqualified addresses by default.
If you are qualifying addresses in messages arriving from other hosts,
you must have set {sender,recipient}_unqualified_hosts, in order to
overrule the RFC requirement that all addresses be fully qualified.
What the Exim 4 manual says is:
qualify_domain Type: string Default: see below
This option specifies the domain name that is added to any sender
addresses that do not have a domain qualification. It also applies to
recipient addresses if "qualify_recipient" is not set. Such addresses are
accepted by default only for locally-generated messages. Messages from
external sources must always contain fully qualified addresses, unless the
sending host matches "recipient_unqualified_hosts" or
"sender_unqualified_hosts" (as appropriate). If "qualify_domain" is not
set, it defaults to the "primary_hostname" value.
What it fails to say is that if {sender,recipient}_unqualified_hosts IS
set, unqualified addresses from remote hosts are qualified in the same
way as those from local hosts. But it does say it later:
sender_unqualified_hosts Type: host list* Default: unset
This option lists those hosts from which Exim is prepared to accept
unqualified sender addresses. The addresses are made fully qualified by
the addition of "qualify_domain". This option also affects message header
lines. Exim does not reject unqualified addresses in headers that contain
sender addresses, but it qualifies them only if the message came from a
host that matches "sender_unqualified_hosts".
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
