search for: olddomaon

...h "translate" I mean that olddomain should be treated as if it > were newdomain. No translation, but more like an alias. > > MJ Don't use wildcard aliases.? They break recipient validation and cause postfix to accept all addresses. Instead use 1-1 aliases, such as user1 at olddomaon? user1 at newdomain user2 at olddomaon? user2 at newdomain user3 at olddomaon? user3 at newdomain ... ? -- Noel Jones

Hi, We're running dovecot 2.2.13, virtual users, with postfix. We have an olddomain and a new domainname. To 'translate' *@olddomain into *@newdomain, I have configured: > cat /etc/postfix/canonical > @olddomain.com @newdomain.com While this seems to work, lately we have noticed that dovecot occasionally creates mailboxes for non-existent users, like: >

Hi No?l, Thanks for your response! On 08/23/2017 06:03 PM, Noel wrote: > Don't use wildcard aliases. They break recipient validation and > cause postfix to accept all addresses. > > Instead use 1-1 aliases, such as > user1 at olddomaon user1 at newdomain > user2 at olddomaon user2 at newdomain But we have 500+ addresses in ldap, surely there must be some 'automated' way to 'transform' any incoming mail sent to random at olddomain.com into random at newdomain.com? (and then have it processed regularly, so...

On 8/23/2017 2:53 PM, mj wrote: > > On 08/23/2017 06:03 PM, Noel wrote: >> Don't use wildcard aliases.? They break recipient validation and >> cause postfix to accept all addresses. >> >> Instead use 1-1 aliases, such as >> user1 at olddomaon? user1 at newdomain >> user2 at olddomaon? user2 at newdomain > > But we have 500+ addresses in ldap, surely there must be some > 'automated' way to 'transform' any incoming mail sent to > random at olddomain.com into random at newdomain.com? > > (and then ha...