On Sat, Aug 16, 2014 at 11:02:30PM -0700, Rich Cook wrote:
> >
> > Bad transport table entry, or previously bogus content filter.
> > The solution depends on which. As root:
> >
> > # postsuper -r deferred
> >
> > will clear the content_filter, unless it is configured to be set again.
> >
Thanks again Wietse.
> Hmm. ADDRESS_REWRITING_README describes the address manipulations
> in the order as executed. Presenting these descriptions in a different
> order would be misleading.
Yes. And it's very well written. But assuming or inferring information
that is not in a technical docume
Michael Fox:
> Thanks much, Wietse.
>
> A couple of follow-ups:
>
> > As documented in ADDRESS_REWRITING_README, canonical mapping happens
> > after append_dot_mydomain.
>
> O.K. I read that document but did not see that statement. I just went back
> and read it again and I still don't see tha
Thanks much, Wietse.
A couple of follow-ups:
> As documented in ADDRESS_REWRITING_README, canonical mapping happens
> after append_dot_mydomain.
O.K. I read that document but did not see that statement. I just went back
and read it again and I still don't see that. Perhaps the order of
proces
Michael Fox:
> If I set local_header_rewrite_clients = static:all or permit_mynetworks or
> some other option that would cause a match of the legacy client, then the
> append_dot_domain option takes over and appends the domain of the postfix
> host, rewriting the address as u...@oldhost.standard.or
I'm having difficulty getting the canonical_maps function to work as needed
to repair some incorrect addresses from a legacy client. Here's the
situation and what I've tried so far:
Legacy client (oldhost.legacy.org) does not append its domain (legacy.org)
to addresses in the envelope or the mess
