Mailcow behind OVH mails

Hi

/story-time-start

We use OVH (provider) exchanges standard pro inboxes (basic smtp imap pop3 roundcube). We have a big volume of email (lets not discuss why), and each inbox can receive more than 500mo of mail each month. And we need to keep them all.

We were doing manual local achieving, and we are looking for a way to automate and improve it.

The idea would be to keep using OVH SMTP endpoints for email delivery; but forward all OVH received email to a self hosted mailcow instance => we will provide each user a 50G/unlimited inbox size here; they will also access their email history on the same inbox without having to access an archieve mail, that’s an improvement.

/story-time-end

So:

• The idea would be to keep using OVH SMTP to deliver emails (we wont handle IP ban issues).
• But auto forward all userXY@domain.com emails to a Mailcow self hosted instance userXY@selfhost.domain.com.

Our user would use Mailcow’s IMAP but OVH SMTP…

Would that work ? I think it would, do you have any advice or warnings ?

As the end goal is also about archieving How could we implement a email-lock mechanism to prevent deletion of received emails ? This is apparently not available ( disable delete emails

mailcow communityDiscussion

disable delete emails

R rezaqes

Hello I want to disable the ability to delete emails through sogo, what way do you suggest for this?

6 2 Sep 23, 2023

Thanks

DISCLAMER: IT IS KNOW THAT AND I’D PREFER NOT TO DISCUSS THAT : THE MAILCOW BEHIND OVH MAIL IDEA IS FOR SUR NOT AN IDEAL DESIGN. SOFTWARES/SERVICES DEDICATED TO ARCHIEVING EXISTS. COMMERCIAL MAIL HOST EXISTS THAT WOULD PROVIDE ENOUGH STORAGE.