OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: problems with virtual maps after upgrading to Postfix 2.3

From: Joe Auty (joenetmusician.org)
Date: Fri Nov 10 2006 - 11:11:38 CST


Sorry for my late response, I was out of town...

On Nov 5, 2006, at 2:34 PM, mouss wrote:

> Joe Auty wrote:
>>
>> I'm not using my alias_maps, but I did double check... my
>> virtual_alias_maps are used, and I don't see a single problem with
>> them. Remember, this same map file worked under Postfix 2.2.x...
>> here is a sample of that file:
>>
>> example.com DOMAIN
>> dianeexample.com diane
>> infoexample.com diane
>
> To avoid surprises, always use fqdn addresses. "diane" will be
> rewritten to diane$myorigin.
>
> Note that your setup doesn't define mydomain, but myhostname =
> mydomain.org. This sounds buggy (see how mydomain is deduced from
> myhostname). again, for less surprises, define mydomain explicitly.

I actually have defined mydomain explicitly:

# postconf | grep mydomain
append_dot_mydomain = yes
mydestination = $myhostname, localhost.$mydomain, localhost,
netmusician.org
mydomain = netmusician.org
myorigin = $mydomain

Is it possible that "diane" is not defaulting to diane$myorigin, and
this is the problem?

I'm not sure why Postfix would be picking up

dianeorg.org

But I can certainly test things by adding the $mydomain suffix to my
map file if you think this would be worth trying....

>> [snip]
>> I'm assuming that by obeying the reply-to header you mean not to
>> alter it... In your case, your personal email was in your reply-
>> to, so this email will be sent to both the list and your personal
>> address.
>>
>
> I was refering to that of Viktor. you CC'ed his From address. see
> Viktor's sig.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFVLLLCgdfeCwsL5ERAq15AJ9Ix5HUVknLzQAyx7OiyzxVADLmPwCfTSAZ
LmWsHP+7k4Ekb+5wyLvX/R8=
=pD0a
-----END PGP SIGNATURE-----