07357
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of /dev/rob0
Sent: Thursday, April 19, 2018 3:10 PM
To: postfix-users@postfix.org
Subject: Re: Outbound address rewriting
On Thu, Apr 19, 2018 at 09:47:27PM +, Kevin Miller
On Thu, Apr 19, 2018 at 09:47:27PM +, Kevin Miller wrote:
> Quick question: In the docs I don't see a reference to a line in
> main.cf. Will postfix pick up on the existence of the table
> automatically once I hash it, or do I need to add something along
> the lines of:
> virtual_alias_ma
On 19-04-18 23:26, Kevin Miller wrote:
> -Original Message-
>> I think in this case both domains are remote, in which case the
>> bounce issue may be moot. Only users authorized to send outbound
>> mail can create email for the destination in question, and the
>> goal is to "correct" the d
> Use canonical_maps to rewrite all instances of the address
> (header, envelope, sender, recipient).
> Use virtual_alias_maps (not virtual_aias_domains) to rewrite
> the envelope recipient only.
Quick question: In the docs I don't see a reference to a line in main.cf.
Will postfix pick up on
-Original Message-
> I think in this case both domains are remote, in which case the
> bounce issue may be moot. Only users authorized to send outbound
> mail can create email for the destination in question, and the
> goal is to "correct" the destination domain.
Right. As it stands now,
> On Apr 19, 2018, at 4:24 PM, Wietse Venema wrote:
>
> In both maps,
>
>@alaska.com@alaskan.com
>
> would do the domain translation.
>
> Caution: with this, Postfix will accept email for any addr...@alaska.com
> including addresses that are later found to be undeliverable. If
>
Kevin Miller:
> Some years back a local ISP/cable company hosted the alaska.com
> domain. They had just leased the domain, and a couple years ago
> the owners didn't renew the lease. GCI registered a new domain,
> alaskan.com (note the "n" in alaskan). When my users send to
> some...@alaska.com,
