From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Michael Maymann
Sent: Thursday, March 29, 2012 4:01 AM
To: postfix-users@postfix.org
Subject: Re: LoadShared Failover
Hi List,
Only problem I see now is when one of the postfix servers dies. Clients
Michael Maymann:
> ; zone file fragment
> IN MX 10 mail.example.com
> .
>
> mailIN A 10.10.10.100
> IN A 10.10.20.100
>
> 3. Clients will use mail.example.com as server.
>
> Only problem I see now is when one of the postfix servers dies. Clients
> will st
Hi List,
I have now looked all over the web to try and find best possible solution
for me... (redundant loadshared sending-only mailgw)... this is currently
what I think of doing...:
1. Setup 2 postfix servers in 2 physical different location with same
configuration (handles by our HostConfigurati
There is one correction, in-line.
> Kris Deugau:
> > We found that DNS-based round-robin strategies didn't actually balance
> > the load very well.
>
> This looks like the same problem that was found (and solved) with
> Postfix outbound connection caching; if a destination host became
> slow for
Kris Deugau:
> We found that DNS-based round-robin strategies didn't actually balance
> the load very well.
This looks like the same problem that was found (and solved) with
Postfix outbound connection caching; if a destination host became
slow for whatever reason, it became a fatal attractor for
Stan Hoeppner wrote:
On 3/12/2012 2:28 AM, Michael Maymann wrote:
Hi,
Stan: My question is not how I setup the solution, but how I *BEST* (best
practice) setup the loadshared/failover postfix solution I described
earlier.
I dunno if there is a BCP covering smtp submission/relay server load
ba
On 3/12/2012 2:28 AM, Michael Maymann wrote:
> Hi,
>
> Stan: My question is not how I setup the solution, but how I *BEST* (best
> practice) setup the loadshared/failover postfix solution I described
> earlier.
I dunno if there is a BCP covering smtp submission/relay server load
balancing/fail ov
Hi,
Stan: My question is not how I setup the solution, but how I *BEST* (best
practice) setup the loadshared/failover postfix solution I described
earlier.
If there isn't a nice howto already, I guess I can figure this out myself -
bonding is easy, if this is the prefered solution for a postfix in
On 3/10/2012 8:30 AM, Michael Maymann wrote:
> How do I best setup a loadshared failover postfix mailrelay solution for
> this on RHEL6 ?
You consult the RHEL6 documentation. If you don't find the answer
there, you contact Red Hat support who will point you in the right
direction. Isn't this wh
Hi,
Wietse: always nice with a bit of humor... :) !
I guess I then only need A records, as this will be our only mailserver
inhouse for R&D.
Benny: I guess this is not needed then, but just out of curiosity: for a
internal sending-only mailrelay why can't I use RFC1918 IPs ?
1. Is best practice t
Den 2012-03-10 09:47, Michael Maymann skrev:
; zone file fragment
IN MX 10 mail.example.com.
mail IN A 192.168.0.4
IN A 192.168.0.5
IN A 192.168.0.6
dont list rfc1918 ip in mx, but if its just a question on model, go for
this solution
Michael Maymann:
> How do I best setup a loadshared failover postfix mailrelay solution for
> this on RHEL6 ?
To repeat my previous response:
- MX records are useful only for MTAs.
- If you have end-user clients, use A records.
Perhaps surprisingly, that response still stands. The mail protocol
Hi,
Wietse: thanks for your quick reply :) !
We have the following internal clients:
- R&D Linux sendmail clients
- some special_home_brew websolutions that endusers maintain
- NetApp storage systems
- etc.
Mail path:
Internal_clients->my_postfix_mailrelay(s)->external_receiving_mailserver
We're
Michael Maymann:
> If RoundRobin is best practise/preferred solution, should I then do:
>
> ; zone file fragment
> IN MX 10 mail.example.com.
>
> mailIN A 192.168.0.4
> IN A 192.168.0.5
> IN A 192.168.0.6
>
> or
>
> ; zone file fragment
>
If RoundRobin is best practise/preferred solution, should I then do:
; zone file fragment
IN MX 10 mail.example.com.
mailIN A 192.168.0.4
IN A 192.168.0.5
IN A 192.168.0.6
or
; zone file fragment
IN MX 10 mail.example.com.
I
15 matches
Mail list logo
