Cloudron Forum

@girish ( ._.) I got servers with 100+ Mailboxes a global bcc all would be... better 😄
Also Cloudron is used by companies in Germany and they have to abide to the law of archiving business communication https://www.gesetze-im-internet.de/hgb/__257.html and a global BCC option would be very nice.

I figured out my issue. Turns out that even though I read the documentation I made one critical mistake right at the beginning. I had to create my email accounts and the addresses I wanted to work in Cloudron first. Then Install the Snappy mail client and set up the email accounts there second.

Once I deleted the Snappy mail client and reinstalled it everything worked. I'm not sure how but this topic can be marked as resolved.

@Kubernetes lol, thanks, thats both useful, and a laugh at myself, at my new level of stupidity unlocked.

@opensourced yes, should be out next week along with 7.4

@Kubernetes that's correct.

@JOduMonT good idea. I think it would be nice if we had a "migrate domain" which "moves" everything - dashboard, MAIL FROM, mailboxes etc. All these are available individually but not as a single operation.

Can you make a feature request?

have you stress test your mail server .. sending more emails to see its limits ( in 1 gb ram small vps) ?

@msbt said in Can't manage existing email address since v7.3.4 update:

for debugging, lmk if needed

Not needed. Just takes a really long time to fetch for domains with bigger maildata.

@girish thanks! It's working fine now.
This is the reason why I love cloudroun ❤

This is fixed for next release with https://git.cloudron.io/cloudron/box/-/commit/3477cf474f32a51c62aef65015e615db62bca4f7

For the other feature request about domains, please make a separate thread there, but I can already say that Cloudron is still designed to work for a setup of one Cloudron per organization and not many maintaining isolated organizations on one Cloudron. This will add all kinds of complexities for the 99% use-cases Cloudron is currently used for.

@YoMaCloud thank you for the correction / update, useful to know.

I have submitted a PR upstream as a temporary fix - https://github.com/haraka/Haraka/pull/3104

@girish Thanks for getting back. Yea I was able to sort this out. It appears it might have been related to the route I had established for internet traffic.

Strange that it would only effect gmail, but this new route is simpler, and testing shows all mails being delivered without issue.

@girish Sure thing!

@girish hey forgot to mention.
My IP is not listed but the AS network is declared as spammy.

While I contacted OVH for this and I respect their answers, they said they are not willing and paying for deblacklisting their network because it like an hostage situation.

So I asked them to change the IP of my instance, let's see.

@chetbaker I haven't forgotten this one, I am yet to get around to testing this...

@necrevistonnezr not sure about Roundcube as I moved over to SnappyMail, but I think it is similar.
Under Filters you can add a sieve script (maybe they call it 'custom')

And yes I think discard with message is equivalent. But not an expert.

Due to the excellent spamassassin rules posted here https://forum.cloudron.io/post/30512 by @d19dotca, I am not needing to use sieve in SnappyMail. But here is the script which I use in Protonmail. The from can be changed to to I guess.

NB : I put the reject part of the rule before the spam test. Arguably I should have a return after the reject - not sure why I did not do that.

require ["include", "environment", "variables", "relational", "comparator-i;ascii-numeric", "spamtest", "reject", "fileinto", "imap4flags"]; if address :contains "from" ["spammer@blah.co.uk", "spammer.com"] { reject "Spam"; } if spamtest :value "ge" :comparator "i;ascii-numeric" "5" { fileinto "spam"; } if exists "list-unsubscribe" { addflag "\\List"; } # Generated: Do not run this script on spam messages if allof (environment :matches "vnd.proton.spam-threshold" "*", spamtest :value "ge" :comparator "i;ascii-numeric" "${1}") { return; }

@girish said in Mail server - How to expose ports for internal network:

@ChicagoGregg said in Mail server - How to expose ports for internal network:

Is it possible to expose its ports (25,465,587) to the local network so that mail can be sent (relayed) through the mail server and let it handle it going outbound? Figuring that Cloudron has this capability, and I'd only have a few emails per day requiring this, it should be able to provide this.

If I understand correctly, you want to relay mail via another mail server. If so, just sent the relay using the External SMTP relay configuration.

I am not quite following the part about exposing port 25/476/587 though. These are already exposed on the server. You have to configure your router/firewall to port forward those ports to the Cloudron internal IP.

Sorry for the tardy reply here. Thanks for both of your replies @subven and @girish .

Originally, I was simply wanting to do something like

Home Network (App sends email) -> Cloudron (on home network) accepts mail for relay from local home network 10.x.x.x -> sends to server through Internet connection (to my already-configured mail relay server, External w/ authentication)

I was looking for an unauthenticated relay on the home network.

Well, I suppose that Cloudron can't provide an unauthenticated relay point. So, I suppose the workaround is simply to configure a user and relay using authentication using a domain that is configured.

I'm fine going this route... And I get why it's for that reason with security. 🙂

Thanks for the help!

-gregg

@d19dotca I can't believe I missed that. Literally read right past it. Thank you!

@girish Hmm, that didn't match the behaviour I saw. I ended up with two separate SPF records in Hetzner. One that I had already set up from my own DNS setup, and one added from Cloudron - which didn't contain the content of my own record. Thankfully it wasn't difficult to fix, once I read up on it.