diff --git a/Servers/Email/iRedMail/Query SMTP Outgoing Queue.md b/Servers/Email/iRedMail/Query SMTP Outgoing Queue.md
index 528eec7..cf7fb02 100644
--- a/Servers/Email/iRedMail/Query SMTP Outgoing Queue.md	
+++ b/Servers/Email/iRedMail/Query SMTP Outgoing Queue.md	
@@ -9,17 +9,23 @@ postqueue -p | awk '/^[A-F0-9]/ {id=$1} /from=<[^>]+>/ && $0 !~ /from=<>/ {print
 ```
 
 !!! example "Example Output"
-    10392 problematic@bunny-lab.io
-    301 prettybad@bunny-lab.io
-    39 infrastructure@bunny-lab.io
-    20 nicole.rappe@bunny-lab.io
+    - 10392 problematic@bunny-lab.io
+    - 301 prettybad@bunny-lab.io
+    - 39 infrastructure@bunny-lab.io
+    - 20 nicole.rappe@bunny-lab.io
 
 ### Investigating Individual Emails
-You can run the following command to read detailed information on any specific queued SMTP message:
+You can run the following command to list all queued messages: `postqueue -p`.  You can then run `postcat -vq <message-ID>` to read detailed information on any specific queued SMTP message:
 
 ```sh
 postqueue -p
 postcat -vq 4dgHry5LZnzH6x08 # (1)
 ```
 
-1.  Example message ID gathered from the previous `postqueue -p` command.
\ No newline at end of file
+1.  Example message ID gathered from the previous `postqueue -p` command.
+
+### Attempt to Gracefully Reload Postfix
+You may want to try to unstick things by gracefully "reloading" the postfix service via `postfix reload`.  This will ensure that we don't drop / disconnect / lose all of the active outgoing SMTP sessions in the queue.  It may not help resolve issues, but it's worth noting down:
+
+### Reattempt Delivery
+You can attempt redelivery via running `postqueue -f` to try to free up the queue.  Postfix will immediately re-attempt delivery of all queued messages instead of waiting for their scheduled retry time. It does not override remote rejections or fix underlying delivery errors; it only accelerates the next delivery attempt.
\ No newline at end of file