Hello Andrew,
Add Mohamed who is our CTO.
I see where the confusion is, apologies for not being specific. The email
server is to manage our corporate emails, we can persist configuration,
email related data in a dedicated storage. Google Workspace (gmail) is (i)
too expensive for us, and we require (ii) full control over our
SMTP/IMAP/POP3 service and the data. Good catch on loosing all our data if
the container needs to reset which can happen if Google performs some
maintenance and needs to reset our host.... The received messages will be
stored on a persisted filesystem, can we not configure IMAP to store the
emails on a persistent filesystem outside of the container?
The approach would be:
- EXIM as the MTP, using port 26 to get around port 25 being blocked by the
cloud service provider
- Dovecot to support IMAP.
- IMAP quota of 200MB of stored emails on the cloud
- Employees will need to log into the VPN to be able to send/receive emails
On Sat, Jan 29, 2022 at 2:46 PM Andrew C Aitchison <andrew@???>
wrote:
> On Sat, 29 Jan 2022, Terrance Devor via Exim-users wrote:
>
> > Hello Heiko,
> >
> > It was posted here
> > https://cloud.google.com/compute/docs/tutorials/sending-mail/
> >
> > I would really like to deploy a containerized EXIM using docker to GCP to
> > manage sending email, and also a POP3 server such as dovecot to manage
> > inbound emails. Can you please help direct in the right direction?
>
> I can't point you in the right direction, as I don't run containers
> on a cloud system.
>
> However, I still don't undertand what you want to do.
>
> If you want to receive mail on your server, then I would not have
> thought that containers were the obvous way to go. The important thing
> is to have a reliable place to store the received messages; a
> container instance that comes and goes according to demand is not a
> good place for permanent storage.
>
> If you want outgoing mail from your Kubernetes cluster, the important
> thing is a stable host act as a smarthost that stores messages until
> they are delivered and logs. This smarthost would stay up; your
> containers could closedown once they have completed their work and
> passed emails to the smarthost.
>
> Google Works, Sendgrid, Mailgun Mailjet and Amazon SES could all act as
> your smarthost, but you said you absolutely need to run your own email
> server on your GCP Kubernetes cluster ?
>
> The cloud.google.com page you referred to also mentions corporate mail
> servers. You could also do that if appropriate.
>
> I suppose that if you run a smarthost (SMTP) and mailserver (POP/IMAP)
> on a Kubernetes cluster you might have to use a container, but
> this virtual? machine isn't particularly a container; it just has to be
> put into one to run on the cluster.
>
> >> Terrance Devor via Exim-users <exim-users@???> (Di 28 Dez 2021
> >> 00:28:37 CET):
> >>> I have read that google blocks port 25 and 465. We absolutely need to
> run
> >>> our email own email servers on GCP using our Kubernetes cluster. Did
> >> anyone succeed in this?
>
> --
> Andrew C. Aitchison Kendal, UK
> andrew@???
>
