On 2023-04-15 17:05, Sebastian Arcus via Exim-users wrote: > On 15/04/2023 17:00, Fabio Martins wrote:
>> I believe you are trying to use the same IP address for the 3 exim
>> instances, otherwise the solution would be quite simple binding each
>> instance to the proper IP address. Right? Or do you have 3 different
>> public IP addresses?
>
> That's correct - there is only one IP address on the VPS/proxy - which
> needs to serve all the Exim servers behind
>
Ok, so solution will work.
>>
>> If you have only 1 public IP, does a solution forwarding to a
>> subdomain via system_aliases+dsearch+local_parts+cron job updating
>> user list, would satisfy?
>>
>> example:
>>
>> adam@??? -> adam@???
>> eve@??? -> eve@???
>> keyser@??? -> keyser@???
>> soze@??? -> soze@???
>> contact@??? -> contact@???
>
> I can't say that I am really following what you are trying to suggest -
> but I don't think having emails on subdomains would help with my
> problem
>
>
The subdomain trick is just a way to reach the right Exim box.
Cloud Box configuration:
box1 VPN IP: bind it to IP 172.20.10.1
box2 VPN IP: bind it to IP 172.20.10.2
box3 VPN IP: bind it to IP 172.20.10.3
VPN configuration for each client ( adjust IP addresses for your
configuration ):
Box1 will bind to port 25 on VPN IP 172.20.10.1
Box2 will bind to port 25 on VPN IP 172.20.10.2
Box3 will bind to port 25 on VPN IP 172.20.10.3
internal DNS configuration of cloud box ( unbound shall do the trick ):
internal.company1.com MX points to 172.20.10.1
internal.business2.com MX points tp 172.20.10.2
internal.designer3.com MX points to 172.20.10.3