On 3/20/2013 11:59 AM, David Koski wrote: >> On 3/19/2013 7:24 PM, David Koski wrote: >>> I need to relay for a domain by default but deliver for specific users >>> locally (Dovecot). >> >> Configure the domain as a normal relay_domain, define the users in >> relay_recipient_maps. >> >> List the specific users to be delivered by dovecot in transport >> pointing to the dovecot transport (assuming the master.cf entry is >> named "dovecot"). >> >> # transport file >> us...@example.com dovecot: >> us...@example.com dovecot: >> # and if the relay domain needs a helper transport entry: >> example.com relay:[somewhere.example.com] > > I am trying to avoid keeping a list of relay recipients separate so I don't > have to maintain two lists, one on the relay server and one on the default > destination server. I'm looking for a way to relay by default but deliver > locally for specific users using dovecot. I do this with another server > using > Courier (maildrop for virtual transport). > > Regards, > David Koski > dko...@sutinen.com >
Recipient validation at the internet gateway is required to prevent your queue from being clogged with undeliverable bounces, and to prevent you from getting blacklisted as a backscatter source. http://www.postfix.org/postconf.5.html#relay_recipient_maps If you control the destination, and have a list of recipients on the destination, it's silly to not use that list on the gateway. Use rsync or a version control system to sync the list between the two computers. Set it up once and let the computer do the work. If there's some reason you can't sync the list to the gateway, use verification probes to let postfix build the list for you. http://www.postfix.org/ADDRESS_VERIFICATION_README.html#recipient -- Noel Jones
