Re: Postfix Transport Maps and MXs Ignored After Upgrade to Lenny
- From: Eric Cunningham <eric@xxxxxxxx>
- Date: Fri, 01 May 2009 14:00:24 -0400
I think I've found a/the fix for re-enabling the original behavior of my transport maps and MX relaying. I added .$mydomain to mydestination in main.cf. This is in addition to $mydomain which was already in mydestination.
$mydomain vs. .$mydomain is subtle but apparently important.
Eric Cunningham wrote:
I just upgraded from etch to lenny and my previously working postfix transport map seems to now be ignored under postfix 2.5.5-1.1. Messages that used to be relayed successfully are now rejected with "Relay access denied." Also, messages addressed to any machines whose MX points to this server running lenny postfix 2.5.5-1.1 are also rejected with "Relay access denied."
I've found a workaround in listing the subdomains in /etc/postfix/transport and MX'd machines as relay_domains in /etc/postfix/main.cf, but this seems redundant.
Have there been any similar reports of this behavior? Any thoughts on how to address this issue? If anyone is able to look into this, I'd be happy to send along any needed details & info.
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Prev by Date: Re: xorg (fglrx, radeon, radeonhd, vesa) not working after upgrade
- Next by Date: Re: No sound on fresh 5.01
- Previous by thread: No sound on fresh 5.01
- Next by thread: IO APIC resources couldn't be allocated