Cloudron Forum

Setting up the sieve rule means I have to have the password and set all of that up.

Using the "mailing list" settings means I don't have to do any of that, don't need to create an inbox, and it doesn't need to be owned by any accounts (and cloudron users with email admin / admin / superadmin can modify as needed).

Screen Shot 2023-12-15 at 5.08.26 PM.png

So I guess I answered my own question 🙂 I'll write it up. for people who ask in the future. "How do I set up email forwarding to external accounts without having to provision Cloudron accounts" == mailing list.

@luckow thanks for the SoGo -- looks like that does take care of everything.

@robi said in SnappyMail on Cloudron: How to setup your domain name's email with SnappyMail:

@jdaviescoates Cool, what recording extension did you use?

Also love the Bitwarden workflow, didn't know it was so slick now.

VokoscreenNG is good:
https://linuxecke.volkoh.de/vokoscreen/vokoscreen.html

@loudlemur Here are some of the possible trouble indicators in the logs (I have obfusticated the domain names/email addresses)

One clue might be that though I am actually able to send mail, none of it appears in the "Sent" folder.

Also, if I go into "Manage folders", i can't create a folder or even click on those toggle buttons on the "inbox" for example. They don't respond.

Dec 17 17:09:50 (node:90) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version. Dec 17 17:09:50 (Use `node --trace-deprecation ...` to show where the warning was created) Dec 17 17:09:50 [INFO] [outbound] secured verified=false cipher=TLS_AES_256_GCM_SHA384 version=TLSv1.3 error=ERR_TLS_CERT_ALTNAME_INVALID cn=*.mydomain.com organization="" fail:zen.spamhaus.org [core] hook=connect plugin=dnsbl function=connect_multi params="" retval=DENY msg="host [123.456.789.012] is blacklisted by zen.spamhaus.org"

@phil24840552 said in Roundcube Login:

@nebulon
I dont know how to download them..
That seems to be the most popular.
https://packagist.org/packages/kolab/calendar
But i cant follow your tutorial. As the post before indicated alredy.

Just follow the instructions on https://github.com/kolab-roundcube-plugins-mirror/calendar (which is linked on the page you gave)

@girish Could a rule be setup in roundcube / other IMAP client to move inbox emails after a set time? I never really messed around with this idea but I could see it coming in handy for large environments that cannot afford huge data storage.

@jdaviescoates it should be array_push($config['plugins'], 'myplugin');

@girish said in Roundcube seems to be out-of-date again.:

Thanks for notifying! We use an app called release bell to get notifications and it has bug for some repos like roundcube where we don't get notification. Generally, I check on these apps monthly manually. For the moment, if I missed it, just open a forum post here and I can push out an update.

We are fixing release bell in the mean time to support gitlab/gogs/gitea as well.

I found the github email notifications very reliable when setting "Watch -> Releases only".

And thanks for updating!

@robi said in Roundcube Login:

Oh I see, so it's not FF integrated in Hamsket, it's just another instance of FF (portable).

Can you run more than one instance?

You can on Windows, as many as you want. Don’t know about Mac/Linux.

I have pushed out 1.4.2. Note that the package is a "major" version upgrade since the UI is kinda different (so you have to click update manually in the Cloudron dashboard, it won't auto update).

Changed 🙂 As it is the default configuration for Roundcube it is working like intended and we could leave it like this? I don't think its a rare use case but maybe it could be added to the documentation (which I always found very helpful).