efa-project.org

Hello,


we have been using EFA for quite a while now, serving more than 5000 emails at the moment and we are very happy with it. However, i do feel there is either one feature missing or we simply missed it.

We have multiple servers with multiple outbound IP's which run mailservers. However, EFA only serves outgoing mail through one IP address. This is very bad since if one of our mailservers gets hacked and sends out large amounts of spam and EFA by some reason lets it through the only IP address gets blocked by spamlists.

We would like to set up EFA so we can specify which mailserver IP should be routed through which EFA IP so we can set one IP per mailserver and ofcourse set SPF records properly.

So lets say:

1.1.1.1 mailserver through 2.2.2.2 on EFA
3.3.3.3. mailserver throguh 4.4.4.4. on EFA

That way if mailserver 1.1.1.1. gets hacked and sends out spam through EFA 2.2.2.2. and 2.2.2.2. gets blacklisted, mail from 3.3.3.3. will still go through 4.4.4.4. unaffected.

Is this possibe with EFA and how?

Thanks

Very simple with multiple EFA appliances with different IPs.

With a single EFA, I think you would need to set up multiple interfaces and instances of postfix with mail transport rules that route the mail out of the correct interface. This takes some work to accomplish and involves editing transport maps and master configuration. Definitely an advanced postfix topic.

First option, easy, second option, more difficult but everything stays unified.

Would you (or anyone else) be interested in making these changes for us in EFA as a quick project? For a fee ofcourse.

We are able to configure outbound email to load balance on multiple ip's

Please contact us via https://eXtremeSHOK.com

we do this now.. we simply use FQDN instead of IP address for outbound and then use either DNS round robinning or a load balancer..

Steve

Steve9R wrote:we do this now.. we simply use FQDN instead of IP address for outbound and then use either DNS round robinning or a load balancer..

Steve

Would you mind sharing some more details about your solution please?

ovizii wrote:

Steve9R wrote:we do this now.. we simply use FQDN instead of IP address for outbound and then use either DNS round robinning or a load balancer..

Steve

Would you mind sharing some more details about your solution please?

Sure..

DNS roundrobining- the poor mans loadbalancer.. .. https://en.wikipedia.org/wiki/Round-robin_DNS

mail IN A IP.of.1st.EFAserver
mail IN A IP.of.2nd.EFAserver
mail IN A IP.of.3rd.EFAserver

etc etc
Then each time a DNS request is made it goes to the next server in the list.. same goes with outbound..

outbound IN A IP of 1st outbound server
outbound IN A IP of 2nd outbound server .. etc etc..

Steve