maxDateTime does not follow standard

Issues
1

Issue Description

The current maxDateTime value of 65534-12-31T23:59:59Z does not conform to RFC 3339 Section 5.6, which mandates exactly 4 digits for the year.

Side note: ISO 8601 allows year values greater than 9999 if agreed upon between sender and receiver, but requires a sign (+/-) prefix for such values.

As a result, the current value is rejected by conformant parsers, such as Java’s Instant.parse.

Expected behavior

maxDateTime has a year with exactly 4 digits, as required by spec

Stalwart Version

v0.16.x

I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.

on

I have searched this support forum (open and closed topics) and confirm this is not a duplicate.

on

2

This isn’t covered in the current docs. A community member or staff member will follow up.

This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.