Paul, Narcis,

thank you for the time you take to help me. I suppose that I am not the
only 'newbie' with this problem.

First, I am not in production. I am a self-employed guy who manage a few
companies. All the email are now managed by gmail and others (OVH...). But
for example, my ggogle account contains 13Gb of emails, because I receive
thousands of reporting mails from the servers that I manage for customers.

And my ressources (money) are limited. And I like to learn... I am an
Oracle DBA, and I know enough to create and manage my 30 servers on 3
different computers, but only one IP (I don't want to use my backup
connexion for this. It is quite slow).

I already use pound to manage these servers, and I thought 'why not manage
emails too?'.

So, no production yet... but soon for one of my customers (a friend in
fact).

So I read what you write, but I really don't understand too much. I spend
one day to try to find something like what I want to do on google. But no
success (I mean I found nothing that I understand).

Do you have any idea of a website which would explain how to setup this
from ground?

Narcis, from your proposition, I would take 'B' (with SSL, my port 25 is
closed from outside). Forwarding from one server to the other is not an
option.

I had a look to postfix, and saw that it can forward emails but I am still
blocked by the fact that it has a 'myhostname' directive... how do I put
two names there? Do you think that this examples is OK?
https://www.howtoforge.com/community/threads/postfix-relay-one-domain-to-smarthost-a-all-else-to-smarthost-b.62955/


I know that this is completely not connected to pound... But I feel, being
quite dumb myself on thse subjects, that to include these explanations to
pound documentation would help people to create a 'complete' solution of
routing. And I would like to use the same server that I already use for
pound, because this is the one which manage my SSL keys already (I use
Let's Encrypt).

Anyway, I thank you for your help and for you sharing your knowledge.

regards,

Christian COMMARMOND
+33 6 82 33 52 32

2017-06-17 10:55 GMT+02:00 Narcis Garcia <[email protected]>:

> 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