Hi list.
Sorry for asking questions again ;)
Quoting Wietse Venema <wie...@porcupine.org>:
As far as I understood the documentation, if those two are at their default:
local_header_rewrite_clients = permit_inet_interfaces
remote_header_rewrite_domain =
local clients are subject to address rewriting, but remote ones are not.
Please pay attention. The feature is called HEADER rewriting
not ADDRESS rewriting.
Ok.. I tried many differend combinations of
append_at_myorigin = yes
append_dot_mydomain = yes/no
with
local_header_rewrite_clients = permit_inet_interfaces
and either
remote_header_rewrite_domain =
or
remote_header_rewrite_domain = domain.invalid
fro both local clients and remote.
I think I found out the following, so can some expert confirm this:
- Header sender and recipient addresses are always rewritten for local
clients (depending on local_header_rewrite_clients) and for remote
clients only if remote_header_rewrite_domain is not empty.
In addition append_at_myorigin and append_dot_mydomain are used for
both to decide what to rewrite.
- Envelope sender and recipient addresses are ALWAYS (regardless of
local or remote clients) rewritten depending on append_at_myorigin and
append_dot_mydomain control.
=> For local clients this makes of course sense.
=> For remote clients I'd see some sense to rewrite the envelope
recipient address.
But why is the envelope sender address rewritten with remote clients??
When I did a "MAIL FROM:<root>" my logs showed that this was expanded
to r...@$myorigin ?
What's the sense behind this?
And are there controls for the envelope address rewriting with respect
to at_myorigin and dot_mydomain that I haven't found yet? Or would I
break things by touching this?
Thanks,
Chris.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
