On 4 February 2010 21:29, Guy <wyldf...@gmail.com> wrote: > On 4 February 2010 10:12, Barney Desmond <barneydesm...@gmail.com> wrote: >> Can you post the output of `postconf -n`? I suspect domain1.org is >> meant to be listed in your $mydestination, but isn't (there's plenty >> of possible causes for this problem, which is >> configuration-dependent). > > postconf -n is below. domain1.org is the domain used for naming all my > servers. The main domain that we redirect all postmaster/abuse etc to > is domain1.net. > >> If I recall, Postfix is actually appending $myorigin to your >> virtual_alias_maps values. > > Yep, which it as far as I understand it should be doing by default > (local_header_rewrite_clients (default: permit_inet_interfaces)). Not > sure whether I can stop it doing that for those aliases or whether I > should be looking to change them in the mailman virtual-mailman file.
Hm, I'll have to defer to more experienced hands, this setup is more interesting than I'm certain about. > r...@pichi:/etc/postfix# postconf -n > mydestination = > myhostname = gateway1.domain1.org > mynetworks = 127.0.0.0/8 > myorigin = $mydomain I'm thinking postfix appends $myorigin and realises it needs to forward it (because $myorigin isn't in $mydestination). However, $myorigin = $mydomain, and $mydomain defaults to $myhostname, minus the first component. I assume this box == domain1.net, in some way. Having an empty mydestination is quite odd, normally you'd at least accept mail for $myhostname, then alias it off somewhere that you *really* want it. Unless I'm mistaken, you'll need a non-empty $mydestination if you're going to use alias_maps.
