Re: transport map not working

2013-08-20 Thread Wietse Venema
jeffrey j donovan: > > First, Postfix needs to know what domains to receive mail for > > (otherwise mail is rejected with "relay access denied"). You specify > > each domain in one of the four domain lists: mydestination, > > relay_domains, virtual_alias_domains, or virtual_mailbox_domains. In ad

Re: transport map not working

2013-08-20 Thread jeffrey j donovan
On Aug 20, 2013, at 12:17 PM, Wietse Venema wrote: > That depends. > > First, Postfix needs to know what domains to receive mail for > (otherwise mail is rejected with "relay access denied"). You specify > each domain in one of the four domain lists: mydestination, > relay_domains, virtual_ali

Re: transport map not working

2013-08-20 Thread Wietse Venema
jeffrey j donovan: > If I do not use a virtual alias map, is a transport map sufficient > by itself or should I always use the two together ? I only ask > this because this was working before I added the alias map. I just > want to be clear that these two work together. That depends. First, Postf

Re: transport map not working

2013-08-20 Thread jeffrey j donovan
On Aug 20, 2013, at 11:39 AM, wie...@porcupine.org (Wietse Venema) wrote: > If you rewrite an envelope recipient address X with virtual_alias_maps > (or otherwise) into envelope recipient address Y, then Postfix will > use envelope recipient address Y for transport map lookups. > > Therefore you

Re: transport map not working

2013-08-20 Thread Wietse Venema
jeffrey j donovan: > I do have a virtual alias map that i am using for some redirected > mail list. is it because i have no user entry that it delivers > locally ? i thought that it would step down to transport if it did > not find anything. > > virtual_alias_maps = hash:/etc/postfix/virtualmm >

Re: transport map not working

2013-08-20 Thread jeffrey j donovan
On Aug 20, 2013, at 11:08 AM, wie...@porcupine.org (Wietse Venema) wrote: > jeffrey j donovan: >> Aug 20 10:36:41 imap2 postfix/pipe[3641]: 536D3DC23DA: >> to=, > > That is us...@imap2.mydomain.com. > >> us...@mydomain.com smtp:sub1.mydomain.com:25 > > That is not us...@imap2.mydomain.com >

Re: transport map not working

2013-08-20 Thread Wietse Venema
jeffrey j donovan: > Aug 20 10:36:41 imap2 postfix/pipe[3641]: 536D3DC23DA: > to=, That is us...@imap2.mydomain.com. > us...@mydomain.com smtp:sub1.mydomain.com:25 That is not us...@imap2.mydomain.com You need to update your virtual aliases or your transport map. Wietse

Re: transport map not working

2013-08-20 Thread Viktor Dukhovni
On Tue, Aug 20, 2013 at 10:45:44AM -0400, jeffrey j donovan wrote: > Aug 20 10:36:41 imap2 postfix/pipe[3641]: 536D3DC23DA: > to=, orig_to=, relay=dovecot, > delay=0.02, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (delivered via > dovecot service) As documented, transport resolution happens a

transport map not working

2013-08-20 Thread jeffrey j donovan
Greetings i have an old osx server that was working fine and I noticed that the transport maps listed in the config are not being followed. I have one domain name and several imap servers. first i checked if the format for the map was correct in main.cf , hash:/etc/postfix/k12_tm_imap2 I veri