Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Ansgar Wiechers (listsplanetcobalt.net)
Date: Thu Apr 08 2010 - 12:14:47 CDT
On 2010-04-08 Thomas wrote:
> Ansgar Wiechers schrieb:
>>> Where /etc/postfix/mydomains lists all domains to be relayed
>> You may want to use a more "speaking" name for your relay domains (like,
>> /etc/postfix/relay_domains ;).
> I need a file with the same content on Server B, where it is referred to
> by $mydestination
> I did not want to use different names for files with the same content ...
I suppose in that case I'd prefer to name the file "domains_COMPANYNAME"
or something, to avoid confusion with domains that are local to the
server. Perhaps a matter of personal opinion, though.
>>> and the relay_transport is the IP of Server B:
>> In your config snippet from server A, the parameter $relay_transport
>> doesn't contain the IP address of server B, but the FQDN of server A.
>> Unless you mis-obfuscated the parameter value you need to correct that
> But why?!?
> It seems to work with the FQDN in square brackets:
> relay_transport = smtp:[mail.example.com]
It should work if the FQDN is the FQDN of server B. It shouldn't work if
the FQDN is the FQDN of server A (which was the case in your config
>>> I would like to let already Server A bounce those mails!
>> # Server A
>> mydestination = $myhostname, localhost.$mydomain, localhost
>> relay_domains = /etc/postfix/relay_domains
>> alias_maps = hash:/etc/aliases
>> local_recipient_maps = $alias_maps
>> relay_recipient_maps = hash:/etc/postfix/relay_recipients
> Der default, that seems to be quite similar already:
> postconf | egrep "^(alias_maps|local_recipient_maps)"
> alias_maps = hash:/etc/aliases
> local_recipient_maps = proxy:unix:passwd.byname $alias_maps
> I can locally expand now, with your suggestion for $mydestination :)
The default includes all local users of the machine, which probably is
not what you want, considering the machine's purpose.
>> The postconf man-page  isn't too clear about this, but I think you
>> need to specify full addresses (user1example.com OK). I have a script
>> somewhere that will generate a list of valid recipients from various
>> (file-based) recipient and domain lists. If I manage to unearth it after
>> I get home tonight, I'll post it here.
> Thanx, but i already created a script - and my users dont change often -
> the file will stay stable for months or even years now :9
> Thank you for your comments and additional help!
"Abstractions save us time working, but they don't save us time learning."