Support email split routing
-
+1 for the feature.
Would be very, very helpful for us to have as well! -
@gobenizzle Not implemented yet.
Just re-reading this thread again. Does this mean the "split" routing itself happens using some external software? What software is that? I guess I am trying to figure how to create a setup to test this.
-
@girish sorry for the delayed reply.
In my case and as I understand in OPs case, the split-routing would happen on google workspace.
Hence the feature would only necessitate, that the local routing can be disabled. Meaning all emails are delivered to the remote mail exchanger (in this case google workspace) and then in google workspace the mails cab be re-routed based on the specific email adresses.
This allows to have both email accounts a gmail and email accounts using cloudron, sharing the same domain.Does this make sense?
-
@gobenizzle said in Support email split routing:
Hence the feature would only necessitate, that the local routing can be disabled. Meaning all emails are delivered to the remote mail exchanger (in this case google workspace) and then in google workspace the mails cab be re-routed based on the specific email adresses.
Since, Google Workspace and Cloudron share the same domain, how does one configure Google Workspace to deliver email to Cloudron ? By IP address?
I understand if the domain is not shared, in which case, it is just mail forwarding. That already works without this split routing concept.
-
@girish
exactly.
In google workspace one can define external hosts either by IP adress or by domain.
So in this case I would add the host-name of the cloudon mail sever ( e.g. mail.cloudron.test:587).
The MX record of the domain would point to google.Now for all email adresses which I would like to keep in cloudron I would add the rerouting option to the cloudron mailsever host.
Note: This already works. I tested it.
The problem is that if I then send a mail from an email-adress hosted at the cloudron instance to email adress hosted on google but on the same domain it runs into delivery problems. I suppose this is because cloudron tries to internally deliver the emails.
So I would hope for an option that disables the internal email routing, so that every email is sent to the sever sepcified in the MX record.This is why OP asks for the ability to "disable internal routing for emails on certain domains".
This option would really help massively
-
@gobenizzle unfortunately, no. I was just re-reading this thread. What is your use case for this (sorry, if I missed this).
@tamayers you said use case is "A reason for this (such as my use case) is that you might have inboxes for employees using Google Workplace, Microsoft Exchange, or Cloudron email for user account and then support inboxes for customer inquires or sales that you do not want handled on the same system." I am not sure why this is done, is this to save money because exchange/workspace charges per mailbox?
-
Hi, I am coming back to this because we woudl still really appreciate this feature. Our use case is as with tamayers that different groups of employees use different systems (partly for legacy reasons, partly because they wish to do so). This means we have a group on google workspace, we have a group on microsoft exchange, and I have a group on cloudron. Now our workaround is quite messy and simply adding the option to force cloudron to do an external MX lookup would solve this problem: The problem is that if I then send a mail from an email-adress hosted at the cloudron instance to email adress hosted on google but on the same domain it runs into delivery problems. At the moment, our workaround is to have all of these account also existing on cloudon and then have them forward the emails to a mailbox on a different domain, which is then forwarding the emails back to the Google or the MS Exchange Server. So quite messy.
Hence we would really, really appreciate if you could implement this feature soon.
Do you think there is any chance you can implement this soon?
