What's coming in 7.3
-
@girish said in What's coming in 7.3:
(mail) VERP and bounce management for mailtrain and mautic
What about Listmonk? (or does that have such stuff built in already?)
-
@jdaviescoates IIRC, Listmonk is able to uses POP3 to read bounce emails and unsubscribe.
-
@girish really looking forward to external links. Is there any projected release date for 7.3?
-
@girish said in What's coming in 7.3:
Mailbox quota is implemented:
Uhhh very nice! Will there be a warning via email so users know that they're running low on space and what happens if the storage is already over quota? Will there be auto-replies that the mailbox is full?
-
@msbt said in What's coming in 7.3:
Will there be a warning via email so users know that they're running low on space
Yes. Two mails are sent to the user - one for 80% full and another for 95% full. Apps like roundcube also show the quota bar on the main screen.
Will there be auto-replies that the mailbox is full?
Mails will bounce with Quota Exceeded message.
There are also events in the mail event log for quota exceeded and when it falls below 80%.
-
Just preparing the release. Updated the changelog if anyone is interested - https://git.cloudron.io/cloudron/box/-/blob/master/CHANGES#L2511 . The CI is running now, hopefully this is done this week.
-
@girish said in What's coming in 7.3:
Updated the changelog if anyone is interested - https://git.cloudron.io/cloudron/box/-/blob/master/CHANGES#L2511
This may be minor, but may I suggest the changelogs be sorted alphabetically so that we can see related changes easier per function (i.e. mail)?
If we did that, not only would it make it easier for admins to read and parse, but the development team could detect duplicate entries in the changelog easier
Note that there are two duplicate entries such as the following:
mail: fix issue where signature was appended to text attachmentsmail: catch all address can be any domain
Sorted alphabetically:
* Applinks - app bookmarks in dashboard * IPv6: initial support for ipv6 only server * Proxied apps * Randomize certificate generation cronjob to lighten load on Let's Encrypt servers * UI: fix issue where mailbox display name was not init correctly * User directory: Cloudron connector uses 2FA auth * acme: Randomize certificate renewal check over a whole day * backups: Fix precondition check which was not erroring if mount is missing * backups: allow space in label name * backups: optional encryption of backup file names * eventlog: add event for impersonated user login * filemanager: add split view * graphs: cgroup v2 support * graphs: show app disk usage graphs * ldap & user directory: Remove virtual user and admin groups * ldap: remove virtual user and admin groups to ldap user records * mail: accept only STARTTLS servers for relay * mail: add queue management API and UI * mail: add storage quota support * mail: allow aliases to have wildcard * mail: catch all address can be any domain * mail: catch all address can be any domain * mail: fix crash when solr is enabled on Ubuntu 22 (cgroup v2 detection fix) * mail: fix issue where certificate renewal did not restart the mail container properly * mail: fix issue where signature was appended to text attachments * mail: fix issue where signature was appended to text attachments * nginx: fix zero length certs when out of disk space * notification: Fix crash when backupId is null * port bindings: add read only flag * proxyAuth: add supportsBearerAuth flag * redis: restart button will now rebuild if the container is missing * wasabi: add singapore and sydney regions -
@d19dotca that's a good idea for the public release notes, I have made it alphabetical there (this is the one you see when you click update on Cloudron, usually it is more high level and not commit based). This changelog in the repo is really just internal and not meant to be read by end users. I know I posted it on the forum, but was just trying to give a heads up for curious people
-
-
Quick question… the mailbox limit size feature… it’s currently only able to be set on individual mailboxes as opposed to a shared limit domain-wide, right? If true then I’ll file a feature request to make it domain-wide if not already filed, as that’d be excellent.
Just wanted to make sure I hadn’t overlooked something though first. -
