updated README.md

Author: pinhead84

README.md

@@ -8,7 +8,6 @@ For example we are using this application, to send push notifications via [ntfy]
 messages. The example callback script [`callback/ntfy.sh`](callback/ntfy.sh) illustrates, how to send those push
 notifications for incoming emails.
 
-
 ## How to install
 
 Make sure, you have **Python 3** and **virtualenv** installed. Clone the repository, enter the repository root and
@@ -27,7 +26,6 @@ the example file to any location you like and make your changes.
 
 You might setup **as many IMAP accounts** as you like within one configuration file.
 
-
 ## How to setup the callback script
 
 In your `config.ini` you should provide for each mail account a callback script, that is called for each newly received
@@ -41,23 +39,23 @@ can be used to see all passed environment variables.
 
 These environment variables with informations about the incoming message are passed to the callback script:
 
-| variable              | example value                 | description                                         |
-|-----------------------|-------------------------------|-----------------------------------------------------|
-| `MESSAGE_ID`          | <[email protected]>             | `Message-Id` header value                           |
-| `MESSAGE_REPLY_TO_ID` | <[email protected]>             | `In-Reply-To` header value                          |
-| `MESSAGE_DATE`        | 2023-07-12 23:31:07           | message date                                        |
-| `MESSAGE_SENDER`      | John Doe <[email protected]>   | complete `Sender` header value                      |
-| `MESSAGE_SENDER_NAME` | John Doe                      | name part of `Sender` header value                  |
-| `MESSAGE_SENDER_MAIL` | [email protected]              | mail part of `Sender` header value                  |
-| `MESSAGE_FROM`        | John Doe <[email protected]>   | complete `From` header value                        |
-| `MESSAGE_FROM_NAME`   | John Doe                      | name part of `From` header value                    |
-| `MESSAGE_FROM_MAIL`   | [email protected]              | mail part of `From` header value                    |
-| `MESSAGE_AUTHOR`      | John Doe <[email protected]>   | either `MESSAGE_FROM` or `MESSAGE_SENDER`           |
-| `MESSAGE_AUTHOR_NAME` | John Doe                      | either `MESSAGE_FROM_NAME` or `MESSAGE_SENDER_NAME` |
-| `MESSAGE_AUTHOR_MAIL` | [email protected]              | either `MESSAGE_FROM_MAIL` or `MESSAGE_SENDER_MAIL` |
-| `MESSAGE_TO`          | Frank Doe <[email protected]> | complete `To` header value                          |
-| `MESSAGE_TO_NAME`     | Frank Doe                     | name part of `To` header value                      |
-| `MESSAGE_TO_MAIL`     | [email protected]             | mail part of `To` header value                      |
+| variable              | example value                   | description                                         |
+|-----------------------|---------------------------------|-----------------------------------------------------|
+| `MESSAGE_ID`          | \<[email protected]\>             | `Message-Id` header value                           |
+| `MESSAGE_REPLY_TO_ID` | \<[email protected]\>             | `In-Reply-To` header value                          |
+| `MESSAGE_DATE`        | 2023-07-12 23:31:07             | message date                                        |
+| `MESSAGE_SENDER`      | John Doe \<[email protected]\>   | complete `Sender` header value                      |
+| `MESSAGE_SENDER_NAME` | John Doe                        | name part of `Sender` header value                  |
+| `MESSAGE_SENDER_MAIL` | [email protected]                | mail part of `Sender` header value                  |
+| `MESSAGE_FROM`        | John Doe \<[email protected]\>   | complete `From` header value                        |
+| `MESSAGE_FROM_NAME`   | John Doe                        | name part of `From` header value                    |
+| `MESSAGE_FROM_MAIL`   | [email protected]                | mail part of `From` header value                    |
+| `MESSAGE_AUTHOR`      | John Doe \<[email protected]\>   | either `MESSAGE_FROM` or `MESSAGE_SENDER`           |
+| `MESSAGE_AUTHOR_NAME` | John Doe                        | either `MESSAGE_FROM_NAME` or `MESSAGE_SENDER_NAME` |
+| `MESSAGE_AUTHOR_MAIL` | [email protected]                | either `MESSAGE_FROM_MAIL` or `MESSAGE_SENDER_MAIL` |
+| `MESSAGE_TO`          | Frank Doe \<[email protected]\> | complete `To` header value                          |
+| `MESSAGE_TO_NAME`     | Frank Doe                       | name part of `To` header value                      |
+| `MESSAGE_TO_MAIL`     | [email protected]               | mail part of `To` header value                      |
 
 The variables `MESSAGE_AUTHOR`, `MESSAGE_AUTHOR_NAME` and `MESSAGE_AUTHOR_MAIL` are some kind of special. By default
 they contain the `From` header value. But if the `From` header is not present, the `Sender` header value is used
@@ -81,7 +79,6 @@ ANOTHER_ADDITIONAL_VARIABLE=test2
 Take a look at [`callback/ntfy.sh`](callback/ntfy.sh) as an example, how to send push notifications for incoming email
 messages (via [ntfy](https://ntfy.sh/)) by using some of the provided environment variables.
 
-
 ## How to run
 
 Assuming your configuration file is called `config.ini`, you might test the settings first via:
@@ -101,9 +98,9 @@ configured account.
 
 If the callback mechanism works as expected, feel free to setup a cronjob or Systemd service.
 
-
 ## FAQ
 
 ### Does it work with gmail or other providers using OAuth?
 
-OAuth is currently not supported as we don't need it for our daily work. Feel free to provide a pull request. We also take donations for improvements like that.
+OAuth is currently not supported as we don't need it for our daily work. Feel free to provide a pull request. We also
+take donations for improvements like that.