Cloudron Forum

Thanks a lot @girish !
We're running mattermost under the indicated domain. I have disabled the outbound, since we have an external SMTP server running - it works now!

I didn't know that Cloudron overwrites configs, but well: Lessons learned 🙂

@Grienauer I think Services -> Mail -> Restart. This updates the mail server certs. Can you check if it works after that?

@RazielKanos said in can't send mails to gmail:

The IP you're using to send mail is not authorized to send email directly to our servers. Please use the SMTP relay at your service provider instead. Learn more at https://support.google.com/mail/?p=NotAuthorizedError f13-20020a05600c4e8d00b003c6f97b761esi8416758wmq.104 - gsmtp

Oh, I missed this. See https://support.google.com/mail/answer/10336?hl=en . Basically, google does not like your IP. Maybe they have blocked the whole IP range of your VPS provider . You have to use a relay - https://docs.cloudron.io/email/#relay-outbound-mails

@LoudLemur said in After self-hosting my email for twenty-three years I have thrown in the towel. The oligopoly has won.:

@necrevistonnezr said in After self-hosting my email for twenty-three years I have thrown in the towel. The oligopoly has won.:

@humptydumpty said in After self-hosting my email for twenty-three years I have thrown in the towel. The oligopoly has won.:

Well, I host Cloudron in my home office with dynamic IPs on a NUC. Outbound email gateway is my very privacy conscious mail provider mailbox.org. For a small family, that’s more than sufficient.

This is the coolest way to run Cloudron, the way that, I think, could bring Cloudron to the masses.

If you ever have time and the inclination and could create some sort of "how-to" video explaining how to solve the tricky parts of accomplishing your setup, I think that could be massive for Cloudron. @girish @nebulon what do you think?

The cool thing: it’s all already building into cloudron! Dynamic IPs DNS (in the network settings) and support for email gateways.

The only thing you have to do on your side is to report your current IP regularly to the domain provider. This happens via ddclient, most commercial routers have a similar function build-in.

@girish with help from vps and hosting it is been solved.
thank you for replying here

@BrutalBirdie So I figured this out, and it's definitely NOT a Cloudron issue. Actually, it's a Thunderbird issue... so I'll probably go write a quick report on Bugzilla at some point.

It turns out that when you hook up two emails for Thunderbird that (1) go the same mail server and (2) share the same password, that causes Thunderbird to ignore the username.

What this means:

Let's say you set up two mailboxes in Cloudron, your.name@company.com and service@company.com. While your.name@company.com is accessible to you, service@company.com is instead accessible to a group you are a part of. You can use user account password to log into both.

Let's say you first add your.name@compay.com to Thunderbird. It will work fine. However when you add service@company.com, outgoing will be messed up (though incoming will work). Rather than outgoing being registered for service@company.com, it'll go out through your.name@company.com, which is not the correct behavior.

You can fix this by going into Outgoing Servers in Thunderbird, but it's a big pain it doesn't need to be, and I'm sure it's something that can be fixed on the Thunderbird end.

Anyways, that was a fun dive into some email issues... hopefully I can get this fixed and jump back into using groups, as that helps make security issues with emails a little easier to deal with (no having to reset everybody's shared password).

Hope you all have an awesome day!

@roofboard did you get this sorted out?

@foliovision Cloudron should create the DKIM records if you're using the DO API for your domains. Cloudron does not delete existing records so if you add something in manually, rest assured it won't get wiped by Cloudron.

https://docs.cloudron.io/email/#dkim

BTW, if you go to your Cloudron dashboard --> Email --> Status --> and click on "Redo DNS Setup", that should add in the required records. It should be listed as a TXT record in DO's DNS.

Example:

TXT cloudron._domainkey "v=DKIM1; t=s; p=TIDfKL7GCS...

@robi In assumption that there is already at least one domain, the code to add a mailbox for a user is already there --> API documentation of Cloudron.

To implement such feature you would need a checkbox like "create email address", a drop down menu that lists all domains (with mailserver enabled?) and a field for the inbox name.

@smhick said in Bulk changes to default email addresses:

The default email is
shortname@domain.com

Says who? I think you are misunderstanding something here. The email address is whatever you create within the Email Server of Cloudron.

First you need to setup an email address at Cloudrons Email Server and assign it to a user. Lets say you create an Email address within Cloudron for our user "bob" with the display name "Bob Marley" that goes like "bob.marley@domain.com". Now you login to SOGo with the credentials bob.marley@domain.com and the password of bob.

So to be clear: You are in charge of creating firstname.lastname@domain.com in the first place before apps like SOGo and other clients come into play.

@girish said in Domains and existing email configuration:

It is possible to setup Cloudron to receive emails on a subdomain though (like email.example.com). For this, add email.example.com in Domains as well and then you can enable incoming mail for that domain.

This is exactly what I was looking for. I didn't know I had to add that additional email.example.com to the list of domains configured in my Cloudron instance. Thanks a ton.

@girish Oh, never mind, it was an SMTP OUT block by the VPS provider... I didn't think that it would apply to running email from another server through OpenVPN on this one...
Sorry for taking your time with this, and thanks again.

@hustler PTR in your case is about setting a reverse DNS (rDNS) record. Take a look at the Linode tutorial: https://www.linode.com/docs/guides/configure-your-linode-for-reverse-dns/

@girish
as you know we use an external Mail Proxy, imapsieve is a good tool to get spam/ham feedback from our users.
Second, it can be used to automate flow based on where the mail has been moved by the user.

@d19dotca I'm excited by the potential for https://ntfy.sh.
Maybe a cloudron official instance which sets up channels for all customers, so cloudron-generated notifications can be delivered to a customer.
Or maybe there's a better way. I just think ntfy.sh is so easy to implement into scripts.

@girish Yes I did! Thanks for all your help!

I think you're looking for more of a mail relay setup with archival things done for incoming emails.

@qwinter Yep, I understood that. But, what DNS settings in the end worked?

@TechoutDev To debug, open the mail logs window. Mail -> Logs button in top right. And then there is another logs button inside it. Keep that browser window open. Then, use the send test mail button - https://docs.cloudron.io/email/#send-test-email . Can you please post what's in the logs?