Incoming Email
-
@nebulon said in Loomio - Package Updates:
We've included the new "email to group" feature. This means as a member of a group, you can send or forward an email to your group email address and it will become a new thread in the group.
I'm trying to get incoming email to work. Right now, the log isn't showing any mailin errors but no inbound email functionality seems to be working.
I've added a and mx records to my DNS
A loomio.domain.com, cloudron_IP MX loomio.domain.com, loomio.domain.com, priority 0I've also configured the reply-to hostname in env.sh
# reply-to in email notifications export REPLY_HOSTNAME=loomio.domain.comAnd for good measure even changed the app's MAIL FROM address to originate from my desired subdomain (loomio.domain.com) so that we're not presenting multiple email hosts to end users.
What else might I need to do to get inbound email working?
-
@nebulon said in Loomio - Package Updates:
We've included the new "email to group" feature. This means as a member of a group, you can send or forward an email to your group email address and it will become a new thread in the group.
I'm trying to get incoming email to work. Right now, the log isn't showing any mailin errors but no inbound email functionality seems to be working.
I've added a and mx records to my DNS
A loomio.domain.com, cloudron_IP MX loomio.domain.com, loomio.domain.com, priority 0I've also configured the reply-to hostname in env.sh
# reply-to in email notifications export REPLY_HOSTNAME=loomio.domain.comAnd for good measure even changed the app's MAIL FROM address to originate from my desired subdomain (loomio.domain.com) so that we're not presenting multiple email hosts to end users.
What else might I need to do to get inbound email working?
-
OK, https://github.com/loomio/mailin-docker/blob/master/Dockerfile is the Dockerfile. mailin listens on port 25 and calls a webhook. Listening on port 25 won't work on Cloudron, so that solution is unviable. We have to write a standalone script that scans IMAP mailbox and calls the wekhook. mailin code that calls the webhook is at https://github.com/loomio/mailin/blob/master/lib/mailin.js .
-
OK, https://github.com/loomio/mailin-docker/blob/master/Dockerfile is the Dockerfile. mailin listens on port 25 and calls a webhook. Listening on port 25 won't work on Cloudron, so that solution is unviable. We have to write a standalone script that scans IMAP mailbox and calls the wekhook. mailin code that calls the webhook is at https://github.com/loomio/mailin/blob/master/lib/mailin.js .
@girish said in Incoming Email:
OK, https://github.com/loomio/mailin-docker/blob/master/Dockerfile is the Dockerfile. mailin listens on port 25 and calls a webhook. Listening on port 25 won't work on Cloudron, so that solution is unviable. We have to write a standalone script that scans IMAP mailbox and calls the wekhook. mailin code that calls the webhook is at https://github.com/loomio/mailin/blob/master/lib/mailin.js .
Did you ever get around to doing this?
I just installed Loomio and immediately tried to start a thread by email and was sad that it didn't Just Work as I've become accustomed to expect on Cloudron
-
@girish said in Incoming Email:
OK, https://github.com/loomio/mailin-docker/blob/master/Dockerfile is the Dockerfile. mailin listens on port 25 and calls a webhook. Listening on port 25 won't work on Cloudron, so that solution is unviable. We have to write a standalone script that scans IMAP mailbox and calls the wekhook. mailin code that calls the webhook is at https://github.com/loomio/mailin/blob/master/lib/mailin.js .
Did you ever get around to doing this?
I just installed Loomio and immediately tried to start a thread by email and was sad that it didn't Just Work as I've become accustomed to expect on Cloudron
-
@jdaviescoates don't think so , no. Unless there is simpler setup, this is really hard to automate in Cloudron.
@girish that's a shame.
Being able to start and reply to threads by email is a core features of Loomio.
Without that we don't really have Loomio at all.
-
@darren thanks.
mailinseems quite outdated (7 years ago). Looks like they tried to replace it upstream as well - https://github.com/loomio/loomio-deploy/issues/99 .@girish said in Incoming Email:
@darren thanks.
mailinseems quite outdated (7 years ago). Looks like they tried to replace it upstream as well - https://github.com/loomio/loomio-deploy/issues/99 .Looks like they did it already in Oct '24
https://github.com/loomio/haraka-rails-dockerThis should work
-
@girish said in Incoming Email:
@darren thanks.
mailinseems quite outdated (7 years ago). Looks like they tried to replace it upstream as well - https://github.com/loomio/loomio-deploy/issues/99 .Looks like they did it already in Oct '24
https://github.com/loomio/haraka-rails-dockerThis should work
@robi said in Incoming Email:
@girish said in Incoming Email:
@darren thanks. mailin seems quite outdated (7 years ago). Looks like they tried to replace it upstream as well - https://github.com/loomio/loomio-deploy/issues/99 .Looks like they did it already in Oct '24
https://github.com/loomio/haraka-rails-dockerThis should work
-
@robi said in Incoming Email:
@girish said in Incoming Email:
@darren thanks. mailin seems quite outdated (7 years ago). Looks like they tried to replace it upstream as well - https://github.com/loomio/loomio-deploy/issues/99 .Looks like they did it already in Oct '24
https://github.com/loomio/haraka-rails-dockerThis should work
@jdaviescoates I'd really like to start using Loomio with a group that involves people in their 80s who would be orders of magnitude more likely and able to participate if they could do so via email and so I'm really hoping @staff can take a look to see if the updated email stuff @robi shared above means that we might be able to get incoming email working for Loomio!
-
Not related to the problem, but simply curious why email flow is required other than something fancy ? Practically all tools I have used in previous companies are web based. In fact, it's explicitly disabled to reply via email for internal forums and enterprise github . The mail parsers are often buggy and the injesters get the timestamp wrong and mix comments ordering incorrectly. Email can also be forged (not to mention spam) and you have to worry about integrity. It's just a world of pain for no benefit (other than people holding on to replying via email on emacs
). -
Not related to the problem, but simply curious why email flow is required other than something fancy ? Practically all tools I have used in previous companies are web based. In fact, it's explicitly disabled to reply via email for internal forums and enterprise github . The mail parsers are often buggy and the injesters get the timestamp wrong and mix comments ordering incorrectly. Email can also be forged (not to mention spam) and you have to worry about integrity. It's just a world of pain for no benefit (other than people holding on to replying via email on emacs
).@joseph said in Incoming Email:
It's just a world of pain for no benefit
There are still LOADS of people (including my friend and group member who is 85 years old) who are still MUCH more comfortable with emails than web or phone apps.
