> >The best course of action is to bounce the messages with a > >relocated_maps entry and force the sender to resend? > > "the best" is subjective. using relocated_maps > http://www.postfix.org/relocated.5.html > you make sure people will not receive mail to the old address, and any mail > must be re-sent to new address to pass.
The plan was to migrate the existing username/passwords to the new n...@example.com format and have the users configure their mail client to login to receive their mail from the new address only. The original recommendation involved setting the Reply-To address to be the new address, but I'm not sure of the point of that - is the expectation here that the user will login to both the new and old accounts? If the recommendation is also to reject/bounce mail to the old address, when is someone ever going to see an email from the old address that they would need the reply-to info? > someone may take this for unnecessary work for senders, which aren't > responsible for recipient who wished to change their address. Perhaps "best practices" would have been better language, then. > >How does using virtual_alias_maps affect my existing configuration if > >I'm not currently using virtual domains or virtual maps? Currently the > >server is processing mail for one domain listed in relay_domains. > > virtual_alias_maps is processed each time a mail is received, so you are > able to alias any mail recipient, even those in remote domains: > > http://www.postfix.org/ADDRESS_REWRITING_README.html#virtual Okay, I'll experiment with that.
