mdecimus
d1c35f65b1
Update version number ( closes #1844 )
2025-07-17 08:19:28 +02:00
mdecimus
f5d0f725de
ACME support for DigitalOcean ( closes #1667 )
2025-07-16 17:06:01 +02:00
mdecimus
efdd2c9241
Fix mta-sts setting parsing issue ( closes #1830 )
2025-07-16 16:06:46 +02:00
mdecimus
e79a4c65c7
Disable webadmin auto-updates
2025-07-15 10:56:08 +02:00
mdecimus
bd61ab511a
v0.13.0
2025-07-15 08:33:14 +02:00
mdecimus
6568d61927
Allow APIs to be used with external directories ( closes #1815 )
2025-07-14 14:45:24 +02:00
mdecimus
4f3406d449
Cache invalidation cluster broadcast ( closes #1741 )
2025-07-13 19:21:56 +02:00
mdecimus
aee7337169
Queue autoconfig post install
2025-07-13 12:01:32 +02:00
mdecimus
036cb2ecd4
Small round of MTA queueing improvements
2025-07-12 19:42:27 +02:00
mdecimus
e28769c5ce
MTA queue enhancements ( closes #1246 closes #1035 closes #457 )
2025-07-11 17:51:53 +02:00
mdecimus
d04a4331c3
Project Alouette: je te plume la queue (et je la remplace par mieux)
2025-07-09 20:38:27 +02:00
mdecimus
d844abbaf8
IMAP Custom Name for Shared Folders ignored ( closes #1620 )
2025-06-28 08:18:19 +02:00
mdecimus
861471fde4
Fix OSS build ( closes #1724 )
2025-06-26 15:47:33 +02:00
mdecimus
76c5aaa983
Rollback build
2025-06-25 17:21:19 +02:00
mdecimus
6cd66c3ff6
Add i18n file as include
2025-06-25 17:00:19 +02:00
mdecimus
01f7c8f56d
Assisted CalDAV/CardDAV shared resource discovery ( closes #1691 )
2025-06-24 13:28:29 +02:00
mdecimus
d6fa4fa8dc
Fix logos ( closes #1652 )
2025-06-24 09:33:08 +02:00
mdecimus
7087148d3d
CalDAV Scheduling ( closes #1514 )
2025-06-23 18:32:19 +02:00
mdecimus
367ddeeae4
CalDAV Scheduling - part 6
2025-06-21 19:53:23 +02:00
mdecimus
068457ea87
CalDAV Scheduling - part 5
2025-06-20 18:28:26 +02:00
mdecimus
c07e3d917f
CalDAV Scheduling - part 4
2025-06-18 18:21:46 +02:00
mdecimus
20cb114715
CalDAV Scheduling - part 3
2025-06-17 15:04:01 +02:00
mdecimus
f10ec68d49
Updated copyright notice
2025-06-15 15:09:32 +02:00
mdecimus
d4ec6e32b3
Normalize INBOX name when creating/renaming folders ( fixes #1636 )
2025-06-08 09:26:36 +02:00
mdecimus
d48418b258
Calendar alarm migration implementation
2025-06-07 18:02:37 +02:00
mdecimus
15dddc433a
Calendar email notifications ( #1514 )
2025-06-06 20:03:19 +02:00
mdecimus
4cf3dfc96d
v0.12.4
2025-06-03 12:43:34 +02:00
mdecimus
acba129cd6
Bump to hickory-resolver 0.26
2025-06-03 11:56:53 +02:00
mdecimus
774e80ab32
Strict vCard parsing ( #1607 )
2025-06-01 17:55:20 +02:00
mdecimus
d9e5838081
v0.12.3
2025-05-30 09:00:59 +02:00
mdecimus
fe24cbf41d
Fix XML CDATA injection (credits to @andreymal for the report)
2025-05-29 19:59:51 +02:00
mdecimus
207d370fd9
Fix: Macro references are replaced with their content when writing config file ( closes #1595 )
2025-05-29 19:24:29 +02:00
mdecimus
42fd7d4de1
Store vanished IMAP UIDs and WebDAV paths
2025-05-29 13:38:41 +02:00
mdecimus
48cc823432
Legacy vCard 2.1 and 3.0 serialization support
2025-05-27 12:42:03 +02:00
mdecimus
acd8df28bd
v0.12.2
2025-05-27 08:48:39 +02:00
mdecimus
1df88433b2
Fix: Failed to build OpenTelemetry span exporter: no http client specified ( closes #1571 )
2025-05-26 19:33:53 +02:00
mdecimus
c73de142ad
Fix: Failed to parse setting dav.lock.max-timeout ( closes #1559 )
2025-05-26 16:22:35 +02:00
aszlig
1b1f85a156
acme: Don't restrict challenge types ( #1522 )
...
When testing my Stalwart deployment with Pebble[1], I got the following
ACME error:
ACME error (acme.error) {
reason = "unknown variant `dns-account-01`, expected one of `http-01`, `dns-01`, `tls-alpn-01` at line 15 column 33",
details = JSON deserialization failed
}
In RFC 8555 section 8[2], the validation challenges are meant to be
extensible:
> The identifier validation challenges described in this section all
> relate to validation of domain names. If ACME is extended in the
> future to support other types of identifiers, there will need to be
> new challenge types, and they will need to specify which types of
> identifier they apply to.
The mentioned error refers to the following draft:
https://datatracker.ietf.org/doc/html/draft-ietf-acme-dns-account-label-01
Pebble already implemented[3] this and while it's IMHO too early to
already support this in Stalwart, we should at least make sure that we
don't break existing deployments in case ACME CAs one day add more
challange types like the above.
[1]: https://github.com/letsencrypt/pebble
[2]: https://datatracker.ietf.org/doc/html/rfc8555#section-8
[3]: https://github.com/letsencrypt/pebble/pull/435
Signed-off-by: aszlig <aszlig@nix.build>
2025-05-25 10:43:59 +02:00
mdecimus
1efaedcc27
Train spam messages as ham when the sender is in the user's address book
2025-05-24 10:17:41 +02:00
mdecimus
c19d2ceb43
Fixed tests for FDB and SQL stores
2025-05-23 17:07:36 +02:00
mdecimus
4505b1cad1
Renamed cluster.pubsub to cluster.coordinator
2025-05-21 18:57:38 +02:00
mdecimus
699fca25e0
Bump open-telemetry to 0.29, tokio to 1.45
2025-05-21 15:49:26 +02:00
mdecimus
8511de8a4d
Updated setting names
2025-05-20 18:00:15 +02:00
mdecimus
9cf2863a8e
Stalwart Mail Server is now just Stalwart
2025-05-20 09:59:54 +02:00
mdecimus
c6ef70edd2
Added caching logging + Update config properties
2025-05-19 19:11:15 +02:00
mdecimus
c79367f790
Fixed queue migration, tenant quotas API and bumped dependencies
2025-05-18 11:58:36 +02:00
mdecimus
4e5c4554c7
Updated DAV config properties + Added 'nats' feature to CI job
2025-05-18 10:42:45 +02:00
mdecimus
65fe4b1b49
Sequential change ids
2025-05-17 21:48:30 +02:00
Tobias Genannt
2b36d50c59
Add description to ID token ( #1234 )
2025-05-16 17:19:10 +02:00
mdecimus
dcdf68b774
XOAUTH2 support (closes #1194 closes #1369 )
2025-05-16 17:17:13 +02:00