Cloudron Forum

@girish what about just a normal organization level rights separation? I mean - it's really two different set of roles: 1st line support, dealing with mailboxes 2nd or 3rd, making sure the system and services are up and running. I don't need hiding anything, I just want to ensure my users can manage they mailboxes and users for they own. For now I have to temporary give admin permissions to the 1st line and that's kind of risky...

Per https://github.com/Monogramm/autodiscover-email-settings/blob/66c144e923f245dc0b4e64421449afedcad64052/index.js#L89 this is served at /email.mobileconfig?email=username@domain.com . I am yet to find an official doc page that says this though. However, ChatGPT thinks it is configs/email.mobileconfig served with content-type set to application/x-apple-aspen-config ...

There is a "Spam" filter type in next release - 6.4

@d19dotca since we had some recent timeout issue with the services view (and mail being a service here) it could be that also here the mail container or the server overall is busy during that time and thus the search queries timeout. If you see this happening again, a look into the system/box logs as well as mail service logs should reveal this then.

DNSBLs are configurable in 6.4

I just realized part of this is a duplicate of one that @marcusquinn filed earlier for Add a setting for sendmail limits per mailbox per day

For reference, Haraka has a greylisting function built in: http://haraka.github.io/plugins/greylist/ - and it works with the DNSWL / whitelist which we should enable too. That way if an IP is on the DNSWL, it automatically skips any greylisting attributes.

@girish said in Change to the DKIM record hostname in recent version, caused by new feature or from using NO-IP domain provider?: If it was random, I was afraid there is still a possibility that they can conflict across servers Great point - that makes sense. Thanks Girish. Side note: I think it'd still be great for the OCD in some of us to be able to regenerate the DKIM record on demand so it not only follows the new hostname pattern in Cloudron but also generates a new key if desired too.

@nebulon thank you! worked perfectly fine and is very helpful

@mdreira said in Lightmeter - Mail server delivery monitoring: What mail server does Cloudron use? Exim? This is what Cloudron uses for smpt: https://haraka.github.io/

@nebulon Will do, thanks!

You can set flags on the email with sieve filters. I think this is only available in roundcube UI though. [image: 1613671026536-bf4f52b4-5648-41a9-aca2-f799daadb640-image.png] Then, in thunderbird, you can highlight them accordingly - https://support.mozilla.org/en-US/kb/message-tags

@privsec said in Let’s encrypt certificates expiring?: Like can there be a memory within cloudron of all subdomains used and when it comes time to renew, just renew it on all of those subdomains? That's the current behavior. It only renews domains that are in use in Cloudron. AFAIK, there is no way to tell Let's Encrypt to "forget a subdomain" that we had gotten a certificate before. This is the reason why you get the reminder emails from Let's Encrypt about old domains.

@marcusquinn It's a more general tool as an attempt to fix and replace the issues with Email in general. It does that well. It just needs adoption. https://hacker10.com/computer-security/send-email-with-tor-i2p-and-gpg-using-confidant-mail/ https://privacytools.io has other options too

@paenzy I read somewhere that adding terms and disclaimers to emails made then "contractual", so in some cases and places it is better not to have them. I'm always interested in what's supposed to be law and what becomes hearsay law because lots of people do it and tell each other it should be done. I don't have experience either way but tend not to use email signatures from both habit and to be personable.

I really like the blackllist checking being built-in. Frankly, I'd also be a fan of getting notifications about it. I suppose UX-wise, perhaps this is the appropriate sort of thing to trigger a yellow status on email.

The root cause for this was the Cloudron server had the hostname as "box.domain.com" (same as the relay). Debian/Ubuntu has a quirk that it will put the hostname in /etc/hosts to resolve as 127.0.1.1. This meant that when we try to set it as relay, it resolves to 127.0.1.1 instead of the actual IP. To add to the confusion, I suggested using the host command which does not use /etc/hosts (i.e the nsswitch mechanisms) and uses only the DNS. If I had suggested using ping then we would have narrowed down the issue more quickly... Anyway, the fix is simply to hostnamectl set-hostname somethingelse.domain.com and also edit /etc/hosts (for some reason, hostnamectl doesn't change hosts file even after reboot, ).

@girish When will this be exposed in the GUI? Hopefully this can be planned for 7.4 perhaps, along with the many other mail improvements requested?

@drpaneas said in gmail blocks my server?: @jdaviescoates I have cloudron installed at home. Ah, right.