added see also + fix link to jmap spec

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.
 
 ||
 |---|

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 -->

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.
 

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:
 

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:
 

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 -->

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:
 

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 -->

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.
 
 ||
 |---|

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 -->

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.
 

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:
 

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.
 
 ||
 |---|

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 -->

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.
 

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:
 

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.
 
 ||
 |---|

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 -->

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.
 

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: