Mino changes

queuemail · Jul 13, 2023 · 1a2af23 · 1a2af23
1 parent 702aa79
commit 1a2af23
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 5 deletions.
diff --git a/api-blacklists.md b/api-blacklists.md
@@ -47,7 +47,7 @@ You will get a JSON response like this:
 }
 ```
 
-- **idsending** email sending id if blacklist has been created due to a email sending.
+- **idsending** email sending id if blacklist has been created due to an email sending.
 - **ip** ip origin of blacklist add.
 - **created** when the email has been added to blacklist.
 

diff --git a/api-emails.md b/api-emails.md
@@ -90,7 +90,7 @@ You will get a JSON response like this:
 - **notvalidrecipients** array with all recipient not valid emails addresses.
 
 
-<!-- tab:Get email sending info -->
+<!-- tab:Get email info -->
 
 
 
@@ -136,7 +136,12 @@ You will get a JSON response like this:
 }
 ```
 
-- **status** field = 'Q' means email has been queued up correctly.
+- **status** = 
+    - 'Q' means email has been queued up correctly. 
+    - 'R' means email is been sent at now. 
+    - 'C' means email has been cancelled. 
+    - 'E' means email send has failled. 
+    - 'F' means email has been sent sucessfully.
 - **inittime** is the estimated time for sending email.
 - **logsdeleledby** it the time when email logs will be deleted.
 - **attachments** array with all url attachments.

diff --git a/features-blacklists.md b/features-blacklists.md
@@ -1,4 +1,4 @@
-Blacklists feature let recipients to include their email addresses in a blacklist in order to block future email sendings from app asociated to that blacklist.
+Blacklists feature let recipients to include their email addresses in a blacklist in order to block send future emails from app asociated to that blacklist.
 
 Also, the system can include a email address in a auto-blacklist when it detects that email address has permanent errors.
 

diff --git a/features-smtpstrategies.md b/features-smtpstrategies.md
@@ -6,7 +6,7 @@ When [creating/editing your app](apps.md), you can choose beetween RANDOM and PR
 
 If you don't specify *strategy* parameter, RANDOM strategy is assumed by default.
 
-If you specify *strategy=PRIORITY*, in each email sending SMTP server with higher priority will be use at first. In case of error, next SMTP with higher priority will be used, and so on.
+If you specify *strategy=PRIORITY*, when sending emails, SMTP server with higher priority will be use at first. In case of error, next SMTP with higher priority will be used, and so on.
 
 You can define priority for each SMTP when [creating/editing your SMTP servers](api-smtps.md).