# Outlook vs standard IMAP protocol

A frequent question we receive regarding our IMAP activities [Get Email Message](/actions/tap-actions/mail/get-email-messages.md) and [Move Email Message](/actions/tap-actions/mail/move-mail-message.md)

is why we face the error "could not fetch mail from server " even if we follow the tooltip guidance - INBOX.FolderName.

![](/files/-MT5gEnSt5rRsCOAdTV5)

For instance, in the example below, the configuration is normally correct, however, when running the workflow, we face the error message.

![](/files/-MT5gEnVCUteWk50IzB8)

That is because in Outlook, users can create folders at the same level as Inbox (like in this case InvoicesUNprocessed and InvoicesProcessed).

![](/files/-MT5gEnWjUpAU5_Ml72O)

So the correct configuration is:

![](/files/-MT5gEnXjFVoxn60rMY-)

Secondly, let's take the case of folder "test1", which was created under inbox.

In Thunderbird:

![](/files/-MT5gEnYoRa2sa2MC0FI)

If the robot would connect to Thunderbird to retrieve info about emails from folder test1, the value of the field Folder Name must be **INBOX.test1**.

In Outlook:

![](/files/-MT5gEnZllQYxiZ775cI)

But if the robot would connect to Outlook to retrieve info about emails from folder test1, the value of the field Folder name must be **INBOX/test1** instead of INBOX.test1, as it can be seen also below:

![](/files/-MT5gEn_Tmr4qXDbAVLN)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tailent.com/getting-started/tap-studio/outlook-vs-standard-imap-protocol.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.