diff --git a/docs/API/EmailObjectClass.md b/docs/API/EmailObjectClass.md
index e7d4a6297ebaa7..f3fc96367a8ba5 100644
--- a/docs/API/EmailObjectClass.md
+++ b/docs/API/EmailObjectClass.md
@@ -27,7 +27,7 @@ This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variabl
 
 Email objects provide the following properties:
 
-> 4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the Email object.
+> 4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the Email object.
 
 ||
 |---|
diff --git a/docs/API/IMAPTransporterClass.md b/docs/API/IMAPTransporterClass.md
index 81906240b8dc75..a46280db5a4fba 100644
--- a/docs/API/IMAPTransporterClass.md
+++ b/docs/API/IMAPTransporterClass.md
@@ -158,6 +158,16 @@ $flags["$seen"]:=True
 $status:=$transporter.addFlags(IMAP all;$flags)
 ```
 
+#### See also
+
+[`.removeFlags()`](#removeflags) 
+
+
+#### See also
+
+[`.removeFlags()`](#removeflags) 
+
+
 <!-- END REF -->
 
 <!-- REF IMAPTransporterClass.append().Desc -->
diff --git a/docs/language-legacy/Mail/mail-convert-from-mime.md b/docs/language-legacy/Mail/mail-convert-from-mime.md
index d178c363a8ceae..e44f8262315f07 100644
--- a/docs/language-legacy/Mail/mail-convert-from-mime.md
+++ b/docs/language-legacy/Mail/mail-convert-from-mime.md
@@ -33,7 +33,7 @@ displayed_sidebar: docs
 
 The `MAIL Convert from MIME` command <!-- REF #_command_.MAIL Convert from MIME.Summary -->converts a MIME document into a valid email object<!-- END REF -->.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the returned email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the returned email object.
 
 Pass in *mime* a valid MIME document to convert. It can be provided by any mail server or application. You can pass a BLOB or a text *mime* parameter. If the MIME comes from a file, it is recommended to use a BLOB parameter to avoid issues related to charset and line break conversions.
 
diff --git a/docs/language-legacy/Mail/mail-convert-to-mime.md b/docs/language-legacy/Mail/mail-convert-to-mime.md
index a84f476747de29..3a3d62f615251b 100644
--- a/docs/language-legacy/Mail/mail-convert-to-mime.md
+++ b/docs/language-legacy/Mail/mail-convert-to-mime.md
@@ -38,7 +38,7 @@ The `MAIL Convert to MIME` command <!-- REF #_command_.MAIL Convert to MIME.Summ
 
 In *mail*, pass the content and the structure details of the email to convert. This includes information such as the email addresses (sender and recipient(s)), the message itself, and the type of display for the message.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the email object.
 
 In *options*, you can set a specific charset and encoding configuration for the mail. The following properties are available:
 
diff --git a/versioned_docs/version-19/API/EmailObjectClass.md b/versioned_docs/version-19/API/EmailObjectClass.md
index e954a0647203c4..24abddaff0c76e 100644
--- a/versioned_docs/version-19/API/EmailObjectClass.md
+++ b/versioned_docs/version-19/API/EmailObjectClass.md
@@ -20,7 +20,7 @@ You send `Email` objects using the SMTP [`.send()`](SMTPTransporterClass.md#send
 
 Email objects provide the following properties:
 
-> 4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the Email object.
+> 4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the Email object.
 
 ||
 |---|
@@ -388,7 +388,7 @@ The `.to` property contains the <!-- REF #EmailObjectClass.to.Summary -->primary
 
 The `MAIL Convert from MIME` command <!-- REF #_command_.MAIL Convert from MIME.Summary -->converts a MIME document into a valid email object<!-- END REF -->.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the returned email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the returned email object.
 
 Pass in *mime* a valid MIME document to convert. It can be provided by any mail server or application. You can pass a BLOB or a text *mime* parameter. If the MIME comes from a file, it is recommended to use a BLOB parameter to avoid issues related to charset and line break conversions.
 
@@ -480,7 +480,7 @@ The `MAIL Convert to MIME` command <!-- REF #_command_.MAIL Convert to MIME.Summ
 
 In *mail*, pass the content and the structure details of the email to convert. This includes information such as the email addresses (sender and recipient(s)), the message itself, and the type of display for the message.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the email object.
 
 In *options*, you can set a specific charset and encoding configuration for the mail. The following properties are available:
 
diff --git a/versioned_docs/version-19/API/IMAPTransporterClass.md b/versioned_docs/version-19/API/IMAPTransporterClass.md
index f379836c58043b..254ddbd956a2cc 100644
--- a/versioned_docs/version-19/API/IMAPTransporterClass.md
+++ b/versioned_docs/version-19/API/IMAPTransporterClass.md
@@ -221,6 +221,11 @@ $flags["$seen"]:=True
 $status:=$transporter.addFlags(IMAP all;$flags)
 ```
 
+#### See also
+
+[`.removeFlags()`](#removeflags) 
+
+
 <!-- END REF -->
 
 <!-- REF IMAPTransporterClass.append().Desc -->
diff --git a/versioned_docs/version-20/API/EmailObjectClass.md b/versioned_docs/version-20/API/EmailObjectClass.md
index ebef6a2aff0ba8..e7dc2c218b7ebe 100644
--- a/versioned_docs/version-20/API/EmailObjectClass.md
+++ b/versioned_docs/version-20/API/EmailObjectClass.md
@@ -20,7 +20,7 @@ You send `Email` objects using the SMTP [`.send()`](SMTPTransporterClass.md#send
 
 Email objects provide the following properties:
 
-> 4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the Email object.
+> 4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the Email object.
 
 ||
 |---|
@@ -387,7 +387,7 @@ The `.to` property contains the <!-- REF #EmailObjectClass.to.Summary -->primary
 
 The `MAIL Convert from MIME` command <!-- REF #_command_.MAIL Convert from MIME.Summary -->converts a MIME document into a valid email object<!-- END REF -->.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the returned email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the returned email object.
 
 Pass in *mime* a valid MIME document to convert. It can be provided by any mail server or application. You can pass a BLOB or a text *mime* parameter. If the MIME comes from a file, it is recommended to use a BLOB parameter to avoid issues related to charset and line break conversions.
 
@@ -479,7 +479,7 @@ The `MAIL Convert to MIME` command <!-- REF #_command_.MAIL Convert to MIME.Summ
 
 In *mail*, pass the content and the structure details of the email to convert. This includes information such as the email addresses (sender and recipient(s)), the message itself, and the type of display for the message.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the email object.
 
 In *options*, you can set a specific charset and encoding configuration for the mail. The following properties are available:
 
diff --git a/versioned_docs/version-20/API/IMAPTransporterClass.md b/versioned_docs/version-20/API/IMAPTransporterClass.md
index 1e616057c70a54..845263ea32a7cc 100644
--- a/versioned_docs/version-20/API/IMAPTransporterClass.md
+++ b/versioned_docs/version-20/API/IMAPTransporterClass.md
@@ -226,6 +226,11 @@ $flags["$seen"]:=True
 $status:=$transporter.addFlags(IMAP all;$flags)
 ```
 
+#### See also
+
+[`.removeFlags()`](#removeflags) 
+
+
 <!-- END REF -->
 
 <!-- REF IMAPTransporterClass.append().Desc -->
diff --git a/versioned_docs/version-21-R2/API/EmailObjectClass.md b/versioned_docs/version-21-R2/API/EmailObjectClass.md
index 4c8a37ee508e68..bca378e545aa2c 100644
--- a/versioned_docs/version-21-R2/API/EmailObjectClass.md
+++ b/versioned_docs/version-21-R2/API/EmailObjectClass.md
@@ -20,7 +20,7 @@ You send `Email` objects using the SMTP [`.send()`](SMTPTransporterClass.md#send
 
 Email objects provide the following properties:
 
-> 4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the Email object.
+> 4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the Email object.
 
 ||
 |---|
diff --git a/versioned_docs/version-21-R2/API/IMAPTransporterClass.md b/versioned_docs/version-21-R2/API/IMAPTransporterClass.md
index 8569c0a8553ce2..a0042ec1497e79 100644
--- a/versioned_docs/version-21-R2/API/IMAPTransporterClass.md
+++ b/versioned_docs/version-21-R2/API/IMAPTransporterClass.md
@@ -157,6 +157,11 @@ $flags["$seen"]:=True
 $status:=$transporter.addFlags(IMAP all;$flags)
 ```
 
+#### See also
+
+[`.removeFlags()`](#removeflags) 
+
+
 <!-- END REF -->
 
 <!-- REF IMAPTransporterClass.append().Desc -->
diff --git a/versioned_docs/version-21-R2/commands/mail-convert-from-mime.md b/versioned_docs/version-21-R2/commands/mail-convert-from-mime.md
index 7d4e8360e1ea52..788a72ffdb1c14 100644
--- a/versioned_docs/version-21-R2/commands/mail-convert-from-mime.md
+++ b/versioned_docs/version-21-R2/commands/mail-convert-from-mime.md
@@ -32,7 +32,7 @@ displayed_sidebar: docs
 
 The `MAIL Convert from MIME` command <!-- REF #_command_.MAIL Convert from MIME.Summary -->converts a MIME document into a valid email object<!-- END REF -->.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the returned email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the returned email object.
 
 Pass in *mime* a valid MIME document to convert. It can be provided by any mail server or application. You can pass a BLOB or a text *mime* parameter. If the MIME comes from a file, it is recommended to use a BLOB parameter to avoid issues related to charset and line break conversions.
 
diff --git a/versioned_docs/version-21-R2/commands/mail-convert-to-mime.md b/versioned_docs/version-21-R2/commands/mail-convert-to-mime.md
index b76aed213899ce..a8dbc497052102 100644
--- a/versioned_docs/version-21-R2/commands/mail-convert-to-mime.md
+++ b/versioned_docs/version-21-R2/commands/mail-convert-to-mime.md
@@ -37,7 +37,7 @@ The `MAIL Convert to MIME` command <!-- REF #_command_.MAIL Convert to MIME.Summ
 
 In *mail*, pass the content and the structure details of the email to convert. This includes information such as the email addresses (sender and recipient(s)), the message itself, and the type of display for the message.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the email object.
 
 In *options*, you can set a specific charset and encoding configuration for the mail. The following properties are available:
 
diff --git a/versioned_docs/version-21-R3/API/EmailObjectClass.md b/versioned_docs/version-21-R3/API/EmailObjectClass.md
index e7d4a6297ebaa7..f3fc96367a8ba5 100644
--- a/versioned_docs/version-21-R3/API/EmailObjectClass.md
+++ b/versioned_docs/version-21-R3/API/EmailObjectClass.md
@@ -27,7 +27,7 @@ This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variabl
 
 Email objects provide the following properties:
 
-> 4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the Email object.
+> 4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the Email object.
 
 ||
 |---|
diff --git a/versioned_docs/version-21-R3/API/IMAPTransporterClass.md b/versioned_docs/version-21-R3/API/IMAPTransporterClass.md
index 81906240b8dc75..00af31535a2cbd 100644
--- a/versioned_docs/version-21-R3/API/IMAPTransporterClass.md
+++ b/versioned_docs/version-21-R3/API/IMAPTransporterClass.md
@@ -158,6 +158,11 @@ $flags["$seen"]:=True
 $status:=$transporter.addFlags(IMAP all;$flags)
 ```
 
+#### See also
+
+[`.removeFlags()`](#removeflags) 
+
+
 <!-- END REF -->
 
 <!-- REF IMAPTransporterClass.append().Desc -->
diff --git a/versioned_docs/version-21-R3/language-legacy/Mail/mail-convert-from-mime.md b/versioned_docs/version-21-R3/language-legacy/Mail/mail-convert-from-mime.md
index d178c363a8ceae..e44f8262315f07 100644
--- a/versioned_docs/version-21-R3/language-legacy/Mail/mail-convert-from-mime.md
+++ b/versioned_docs/version-21-R3/language-legacy/Mail/mail-convert-from-mime.md
@@ -33,7 +33,7 @@ displayed_sidebar: docs
 
 The `MAIL Convert from MIME` command <!-- REF #_command_.MAIL Convert from MIME.Summary -->converts a MIME document into a valid email object<!-- END REF -->.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the returned email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the returned email object.
 
 Pass in *mime* a valid MIME document to convert. It can be provided by any mail server or application. You can pass a BLOB or a text *mime* parameter. If the MIME comes from a file, it is recommended to use a BLOB parameter to avoid issues related to charset and line break conversions.
 
diff --git a/versioned_docs/version-21-R3/language-legacy/Mail/mail-convert-to-mime.md b/versioned_docs/version-21-R3/language-legacy/Mail/mail-convert-to-mime.md
index a84f476747de29..3a3d62f615251b 100644
--- a/versioned_docs/version-21-R3/language-legacy/Mail/mail-convert-to-mime.md
+++ b/versioned_docs/version-21-R3/language-legacy/Mail/mail-convert-to-mime.md
@@ -38,7 +38,7 @@ The `MAIL Convert to MIME` command <!-- REF #_command_.MAIL Convert to MIME.Summ
 
 In *mail*, pass the content and the structure details of the email to convert. This includes information such as the email addresses (sender and recipient(s)), the message itself, and the type of display for the message.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the email object.
 
 In *options*, you can set a specific charset and encoding configuration for the mail. The following properties are available:
 
diff --git a/versioned_docs/version-21/API/EmailObjectClass.md b/versioned_docs/version-21/API/EmailObjectClass.md
index 4c8a37ee508e68..bca378e545aa2c 100644
--- a/versioned_docs/version-21/API/EmailObjectClass.md
+++ b/versioned_docs/version-21/API/EmailObjectClass.md
@@ -20,7 +20,7 @@ You send `Email` objects using the SMTP [`.send()`](SMTPTransporterClass.md#send
 
 Email objects provide the following properties:
 
-> 4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the Email object.
+> 4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the Email object.
 
 ||
 |---|
diff --git a/versioned_docs/version-21/API/IMAPTransporterClass.md b/versioned_docs/version-21/API/IMAPTransporterClass.md
index 7dca398f7f50fc..733b30243dedf8 100644
--- a/versioned_docs/version-21/API/IMAPTransporterClass.md
+++ b/versioned_docs/version-21/API/IMAPTransporterClass.md
@@ -157,6 +157,11 @@ $flags["$seen"]:=True
 $status:=$transporter.addFlags(IMAP all;$flags)
 ```
 
+#### See also
+
+[`.removeFlags()`](#removeflags) 
+
+
 <!-- END REF -->
 
 <!-- REF IMAPTransporterClass.append().Desc -->
diff --git a/versioned_docs/version-21/commands/mail-convert-from-mime.md b/versioned_docs/version-21/commands/mail-convert-from-mime.md
index 7d4e8360e1ea52..788a72ffdb1c14 100644
--- a/versioned_docs/version-21/commands/mail-convert-from-mime.md
+++ b/versioned_docs/version-21/commands/mail-convert-from-mime.md
@@ -32,7 +32,7 @@ displayed_sidebar: docs
 
 The `MAIL Convert from MIME` command <!-- REF #_command_.MAIL Convert from MIME.Summary -->converts a MIME document into a valid email object<!-- END REF -->.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the returned email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the returned email object.
 
 Pass in *mime* a valid MIME document to convert. It can be provided by any mail server or application. You can pass a BLOB or a text *mime* parameter. If the MIME comes from a file, it is recommended to use a BLOB parameter to avoid issues related to charset and line break conversions.
 
diff --git a/versioned_docs/version-21/commands/mail-convert-to-mime.md b/versioned_docs/version-21/commands/mail-convert-to-mime.md
index b76aed213899ce..a8dbc497052102 100644
--- a/versioned_docs/version-21/commands/mail-convert-to-mime.md
+++ b/versioned_docs/version-21/commands/mail-convert-to-mime.md
@@ -37,7 +37,7 @@ The `MAIL Convert to MIME` command <!-- REF #_command_.MAIL Convert to MIME.Summ
 
 In *mail*, pass the content and the structure details of the email to convert. This includes information such as the email addresses (sender and recipient(s)), the message itself, and the type of display for the message.
 
->4D follows the [JMAP specification](https://jmap.io/spec-mail.html) to format the email object.
+>4D follows the [JMAP specification](https://jmap.io/spec/rfc8621/) to format the email object.
 
 In *options*, you can set a specific charset and encoding configuration for the mail. The following properties are available: