Cloudron Forum

Nevermind, I did a rollback and fixed it

I am somewhat perplexed as to how to setup email forwarding and aliasing in Cloudron.

Coming from Mailcow, alias accounts are created within the user mailbox itself, for which, user credentials are then passed-on, or inherited accordingly.

Though as it stands, I cannot accomplish a similar setup in Cloudron, as the options seem to be that of creating the mailboxes with shared ownership, though I can't seem to figure out how to setup forwarding?

Likewise, I'm having difficulty with webmail, in that SoGo doesn't seem to want to allow the addition of identities in my main account - and so, I'm having to create all of the accounts via IMAP with separate identities - though here again, without a mailbox, taggging, aliasing etc?

• sorry if this is confusing, I'm very new to Cloudron, and having a tough time wrapping my head around the methodology that comes with the software

I just installed Cloudron on a fresh VPS(Ubuntu 22.04), and though I'd take a peek at the logs(sys.info), and found what looks like an endless amount of warnings.

That said, does anyone know what this is, and moreso, if I need to do anything about it?

@girish said in Completely baffled with email forwarding /aliases:

@JohnBee ...When you edit mailbox -> Add Alias -> note the domain is a dropdown (I know it's a bit tricky to get this...)

This was the missing element in my dilemma!
Many thanks

Hi, and thanks so much for the replies - much appreciated

@girish said in Completely baffled with email forwarding /aliases:

@JohnBee ...I tried to look into mailcow docs as to what aliases mean but I didn't find any relevant docs. Do you have a link where we can read more?

Unfortunately, Mailcow isn't very good on documentation - though as I keep a staging server on tap, I can provide screenshots, or even access should you fancy a closer look at the interface etc.

PS, as much as I love Mailcow's creative approach to a turn-key mail server/service, I came to appreciate(the hard way), the inherent risks of using open source software in live environments

@fbartels

So sorry, but was short on time and opted to reinstall the cert. to get back to what seems like normal - and so, I have no information to share in-terms of troubleshooting.

That said, and if /or when this happens again, I'll take the time to properly investigate

NB, for what it's worth, I am using Cloudflare API key, of which has always worked without issue in Cloudron, though for some unknown reason, the cert appears to have expired and would no longer renew. And so I performed as roll-over oin the API/Key side of things, then reissued, and everything appears to be back to normal

Holy crap Batman!

I logged-in Cloudron interface and found an update/reboot notification, did the deed, only to find email /SoGo completely unresponsive after the fact.

Luckily, I had snapshots to fall back-on, but wow, talk about a slap in the face.
No idea what went-wrong, though my current solution is to avoid the update to keep things up and running, which isn't good.

Tried removing SoGo and getting;

Task Error

If a configuration, update, restore or backup action resulted in an error, you can retry the task.

An error occurred during the uninstall operation: External Error: [403] Invalid access token code:9109