A) If the forwarding criteria to select SMTP backend1 or SMTP backend2
is the target recipient address, you better use MTA* relay directives:
send all traffic to backend1 and let this one select what is local and
what to forward to backend2

B) If the forwarding criteria to select SMTP backend1 or SMTP backend2
is the asked service (server FQDN), you better use a reverse proxy
(haproxy / sltd**): forward traffic to smtp.example1.net and
smtp.example2.com to each corresponding backend.

C) If the forwarding criteria to select SMTP backend1 or SMTP backend2
is the sender address or login username, better make people setup
different SMTP server name and use method [B].


- Which security use the mail users to login SMTP service? None? SSL? TLS?
- Which port is for users? 587 ?
- Are you solving a situation already in production, or are you
designing the system for a new service?


(*) MTA: Postfix / Exim /etc.
(**) sltd is capable of managing multiple ports, but only one too.
(***) Backends can be referred on IP or on FQDN.


El 16/06/17 a les 22:19, Christian COMMARMOND ha escrit:
> Hello,
> 
> I had a look to haproxy, I don't see what I am looking for anywhere,
> just load balancing of one mail.domain.com <http://mail.domain.com> to
> several servers. 
> sltd, just one page of doc, which says: sltd daemonizes multiple slt
> instances to accept TLS/SSL connections on multiple ports, but I have
> only one.
> 
> I have one IP, but two mails servers: domain1.com <http://domain1.com>
> and domain2.com <http://domain2.com>. if someone sends an email to one
> of these, they will try to connect to the IP on the same port. Am I
> right? I thought that the communication is full text and that it
> contains the full email address, so, we should be able to route this
> communication to the good mail_serveur? 
> 
> But is looks like this is not possible. And maybe, I should just stop now...
> 
> Can someone points me to a page with the solution? I am sorry, I am not
> an email expert. 
> 
> And to user two IP would need that I setup something to manage two
> connections on my network, which is out of my capabilities. (I would
> like, but I do not know where to start, and how to do it without
> breaking what I have)...
> 
> 
> 
> 
> 
> cordialement,
> 
> Christian COMMARMOND
> +33 6 82 33 52 32
> 
> 2017-06-16 17:51 GMT+02:00 Narcis Garcia <[email protected]
> <mailto:[email protected]>>:
> 
>     If you want to route SSL/TLS without needing proxy or IP translation:
>     https://git.actiu.net/libre/sltd/ <https://git.actiu.net/libre/sltd/>
> 
> 
>     El 16/06/17 a les 13:07, Christian COMMARMOND ha escrit:
>     > Hi,
>     >
>     > I am using pound to route my https and http. But I have now the same
>     > need about other services, like mails.
>     >
>     > I have two domains coming to my only IP. On both, I have to manage mails
>     > on port 543.
>     >
>     > Can I do comething like that:
>     > ListenIMAPS
>     >      Address 192.168.11.146
>     >      Port    945
>     >      Cert    "/etc/pound/certs/www.mydomain.eu
>     <http://www.mydomain.eu> <http://www.mydomain.eu>"
>     >
>     >    Service
>     >       HeadRequire "Host:*.imap.mydomain.eu.*"
>     >       BackEnd
>     >          Address  192.168.11.114
>     >          Port     945
>     >       End
>     >   End
>     >
>     >    Service
>     >       HeadRequire "Host:*.imap.myotherdomain.eu 
> <http://imap.myotherdomain.eu>.*"
>     >       BackEnd
>     >          Address  192.168.11.115
>     >          Port     945
>     >       End
>     >   End
>     >
>     >
>     > End
>     >
>     >
>     > If yes, can you tell me where to find the good syntax?
>     >
>     > best regards,
>     >
>     > Christian COMMARMOND
>     > +33 6 82 33 52 32
>     >
>     >
> 
>     --
>     To unsubscribe send an email with subject unsubscribe to
>     [email protected] <mailto:[email protected]>.
>     Please contact [email protected] <mailto:[email protected]> for questions.
> 
> 

--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to