This guide explains how to centralize the display of your different Infomaniak email addresses when you have multiple accounts and messaging offers.

Display email addresses from all Organizations

A first approach is to display the global Mail web app for all Organizations to which your Infomaniak account is linked:

1. Click here to access the Infomaniak Mail web app (online service ksuite.infomaniak.com/mail).
2. Then click on the chevron ‍ to the right of the displayed email address.
   • The other addresses of the Organization for which you have permission will be displayed.
3. If you have access to other addresses on other Organizations that your user accesses, click on the chevron ‍ to the right of the active Organization:
   
4. Either you click on another Organization (my kSuite for example) to display only the other specific email address…
5. Or you click on All Organizations to display all email addresses in the interface:
   
6. The shortcut for this common display is https://ksuite.infomaniak.com/all/mail:
   

If an email address you know is not visible:

• Check at the top right that you are logged in with the correct Infomaniak account.
• Check with the address administrator that you have access to the address in question with your current Infomaniak account login.

If, on the other hand, you want to remove an address from the list, refer to this other guide.

This guide explains how to add or modify one or more SRV type records in the DNS zone (of a domain name) managed on the Manager Infomaniak.

Preamble

• This type of record allows you to indicate which services are available for a domain.
• They are often used for XMPP, LDAP protocols or to configure Microsoft Office 365.

Modify the DNS zone

To manage this type of record in a DNS zone:

1. Click here to access the management of your domain on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the domain in question.
3. Click on DNS zone in the left sidebar.
4. Click the button to add a record:
   
5. Click on the radio button SRV to add a record.
6. Click on the Next button:
   
7. Enter the values of the SRV required for your DNS zone (the ._tcp.domain… is already entered).
8. Leave the default value for the TTL.
9. Click on the Save button:
   

Check the correct addition of the complete SRV in the records table:

This guide explains the steps required for you, as an employee, collaborator, family member, or in any other situation, to access an email address created on Infomaniak by a third party.

Request to be a user of the email address

Prerequisites

• If you already have an Infomaniak account, check that the email address is actually inaccessible to your user at the moment.
• Note your login ID: click on the badge with your initials / avatar in the top right of the Infomaniak Manager:
  

Then, contact the manager of the email address concerned (demo@primary-domain.ch in this example):

1. Ask him to follow the instructions provided in this other guide faq.infomaniak.com/1478 to add your login ID as a user of the address “demo” on the Mail Service “primary-domain.ch”.
2. Provide him with your login ID, for example faq@example-domain.ch.

He will then be able to add your login ID at point 6, as a user of the email address:

• either directly, because you are already part of the same Organization as him:
  
• or via an invitation link system, which he can send you by message, email for example:
  

Once the operation is complete, you will see the content of the mailbox concerned appear on your interface ksuite.infomaniak.com/all/mail:

This guide explains how to create a "catchall" type email address on a Service Mail.

✘ UNAVAILABLE with
kSuite free
my kSuite / my kSuite+
Service Mail Starter

Preamble

• A "catchall" type email address retrieves all emails sent to non-existent email addresses on the domain.
  • This is ideal if you want to receive all messages for which there is no specific address on your domain.
  • This type of address cannot be used to send emails.
• If you configure the "Automatic Reply" (out-of-office message) function on a catchall@ address, no automatic reply will be sent to senders who contacted a non-existent address on your domain.
  • This restriction notably avoids reply loops and the sending of unwanted messages.
• Also, take note of the important recommendations at the end of this guide.

Create a catchall address

Prerequisites

• Have a Service Mail on your Infomaniak Manager.
• Have a quota of available free addresses or adjust it in advance if necessary.

Then, the administrator of a Service Mail creates a new generic email address:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the product concerned.
3. Click on the chevron to the right of the blue button Create an email address.
4. Click on Create a generic email address:
   
5. Choose Catchall.
6. Click on Continue:
   

Once the catchall address is created, it is automatically visible on your Infomaniak Mail web app.

To use it elsewhere, you just need to add a password for your devices/users.

Example of use

Once the address catchall created:

1. You are using the email address jonnie.smith@domain.xyz which works and exists on the Mail Service domain.xyz.
   • You have also created an address catchall@domain.xyz on the Mail Service domain.xyz.
2. An email is sent to smith.johnny@domain.xyz because the sender misspelled the recipient's address.
3. The email will still arrive in the catchall@domain.xyz box which is enough to consult in the Mail interface of your choice.
4. Same if you delete the address jonnie.smith@domain.xyz one day; if you keep the catchall address, then it is the latter that will receive everything that is still addressed to the non-existent address...

Important recommendations

Creating this type of account is not recommended:

• Catchall addresses receive all emails sent to any domain address; this means they are often flooded with spam, which can be difficult to manage and filter.
• Due to the high volume of spam, legitimate messages can be drowned out and lost in the mass, which can result in the loss of important communications.
• Catchall addresses can potentially be used by attackers to target your domain with brute force attacks or other methods, as they provide an easy target for testing different address combinations.

This guide explains how to create email addresses in bulk instead of adding them one by one within an Infomaniak Mail Service.

Preamble

• To ensure responsible use of the services, a limit of up to 50 email addresses per 24-hour period has been set.
• Contact Infomaniak support to lift this restriction.

Create new email addresses in bulk

Prerequisites

• Have a tool to manage CSV files (format .csv).
• Have a Mail Service on your Infomaniak Manager.
• Have a quota of available addresses or adjust it in advance if necessary.

Obtain the example CSV file

Importing is done using a CSV file (format .csv) which, once filled out, can be imported to add the addresses to your Mail Service in one go.

To download the CSV file to configure the creation of addresses:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click on the chevron ‍ to the right of the blue address creation button.
3. Click on Create multiple email addresses
   
4. Download the proposed template (CSV file in .csv format):
   

Complete the CSV file

1. Open the example CSV file; do not touch the first line, then from the second line on:
   1. 1st column, specify the address to create (without the domain)… example: john.
   2. 2nd column, specify if necessary a complete email address to which to redirect emails.
   3. 3rd column, specify whether to delete (1) messages after redirection.
      

• The second and third columns are optional (you can leave them completely empty).

Import the CSV file

Once the .csv file is completed, save it in the same format as the proposed model and then:

1. Click on the chevron ‍ to the right of the blue address creation button.
2. Click on Create multiple email addresses.
3. Click on Select a CSV file:
   
4. Browse your device and select your CSV file.
5. Click on Continue; after a few minutes, the email addresses will be added (without any password being assigned to them yet), according to the instructions in the imported file.

This guide helps you if you receive error mails that mention SPF when you write to gmail, microsoft, or similar addresses.

Are all your services with Infomaniak?

The Global Security tool informs you of any configuration inconsistency regarding your Infomaniak Mail Service.

Are some of your services elsewhere?

To resolve an email sending issue when your email is managed by Infomaniak and your website is with another provider (like Wix for example) and in this situation the DNS zone of the domain name is managed elsewhere, refer to this other guide.

This guide explains how to restore backups of previous versions of your files and other web data from your Infomaniak hostings, and how to set up an effective backup policy if the automatically and freely provided backups no longer meet your availability or security needs.

Web Hostings (Starter, Shared, Cloud Server)

Refer to these guides to restore automatic backups:

• of an entire hosting (FTP + MySQL),
• of specific files on the hosting,
• of specific databases,
• of a Web Application (Wordpress & Apps),
• of Cloud Server SSH crons.

Refer to these guides to backup and restore:

• a hosting with Swiss Backup and Restic (advanced),
• WordPress with Swiss Backup,
• WordPress with an extension.

Also refer to https://faq.infomaniak.com/snapshot.

Messaging

• Restore messages from Infomaniak automatic backups.
• Restore contacts or calendar events.
• Backup the current content of an email account:
  • by downloading the current content locally,
  • by duplicating all current content to a backup box,
  • by copying future emails as they arrive to a backup box.

Domains / DNS Zones

• Restore deleted DNS records from Infomaniak automatic backups.
• Restore an expired domain in redemption period.

This guide will help you resolve an issue if you received, after sending an email, a message containing the failure reason "Spam Message Rejected" or "5.7.0 AV: Message is rejected by headers rule filter.. 554 Please check the message and try again"...

Must be checked

Check that your email did not contain:

• words or phrases that are often associated with spam, as it could be identified as unwanted and rejected
• any unusual indication in the signature, a link formulated incorrectly (http//.domain.xyz for example), etc.
• an attachment with one of these forbidden extensions: .exe, .com, .cmd, .cpl, .hta, .scf, .sct, .lnk, .bat, .js, .jse, .wsh, .ws, .wsf, .wsc, .vbe, .vb, .vbs, .shs, .pif, .scr... including inside a compressed file (.zip for example)

To send a file (js or exe for example) and confirm that it is virus-free, store it on your hosting space and create a link to it (if the file is large and you are sending it from the Infomaniak Web app Mail (online service ksuite.infomaniak.com/mail), it will be placed on a temporary server allowing it to be sent to your correspondent who will receive a download link in this case) or via Swisstransfer.com.

Also check your SPF record. If your domain does not have an SPF record or if this record is incorrect, this will very likely result in the rejection of your message.

If you believe you are receiving a "Spam Message Rejected" message without reason, contact Infomaniak support.

This guide details the “bogus HELO” email error to help you understand its origin and how to fix it.

When and why does this error occur?

The SMTP protocol (used for sending emails) has several phases. The first involves the sender's server introducing itself to the recipient's server using the HELO command (or EHLO for extended SMTP). This command must be followed by a valid hostname.

If you receive an error mentioning “bogus HELO,” it means the identifier provided by the sending server does not comply with RFC 5321. This check is an essential security measure that helps filter out a large number of misconfigured servers, often used for spreading viruses and spam.

Infomaniak rejects any message from a server that identifies itself generically (e.g., “server”) or locally. The server must use a FQDN (Fully Qualified Domain Name), i.e., a complete and resolvable hostname such as “server.domain.xyz.”

Examples of configurations leading to rejection:

Using a local or loopback IP address:

220 mta-gw.infomaniak.ch ESMTP Infomaniak Network Mail Servers; HELO 127.0.0.1

Using an IP address in brackets instead of a domain name:

220 mta-gw.infomaniak.ch ESMTP Infomaniak Network Mail Servers; HELO [192.168.1.1]

Using an unqualified local hostname:

220 mta-gw.infomaniak.ch ESMTP Infomaniak Network Mail Servers; HELO localhost 220 mta-gw.infomaniak.ch ESMTP Infomaniak Network Mail Servers; HELO mon-serveur

Using a banned or obviously fake domain name:

220 mta-gw.infomaniak.ch ESMTP Infomaniak Network Mail Servers; HELO fakedomain.xyz

In these cases, the SMTP transaction will fail with the following code:

MAIL FROM: user@domain.com 250 2.1.0 user@domain.com... Sender ok RCPT TO: recipient@infomaniak.ch 550 5.7.1 recipient@infomaniak.ch... Access denied - bogus HELO [1]

How to resolve this issue?

If you use a programming script (PHP, Python, etc.) to send emails via SMTP, ensure that the library used is configured to send a valid domain name in the HELO command and not the web server's IP address.

This guide details the allowed and disallowed characters when creating an email address (up to 64 characters) in an Infomaniak Mail Service.

Preamble

• The allowed characters differ depending on whether they appear before or after the at sign @. For example, in username.mail@domain-name.xyz :
  • Before the at sign: the part username.mail corresponds to the username.
  • After the at sign: the part domain-name.xyz corresponds to the domain name.
• To learn about the possibilities offered at the domain name level (part after the at sign @), refer to this other guide.

Part before the at sign: username.mail

The RFC 5321 and RFC 5322 standards define the general syntax of email addresses. However, email providers — including Infomaniak — apply additional restrictions to ensure security, consistency, and compatibility with the majority of email software/clients.

For example, an address such as -@example.com is syntactically valid according to RFC 5322, but is not accepted when created on Infomaniak servers.

These additional rules notably allow:

• to avoid abuse (spam, malicious automation, etc.);
• to respect naming conventions (an identifier composed solely of - makes no sense);
• to ensure compatibility with email software/clients that poorly handle certain address formats.

In summary: RFC 5322 defines what is syntactically possible, but each server determines what is actually usable in practice.

Allowed characters before the at sign

The following characters can be used in the part before the at sign of an Infomaniak email address:

Forbidden characters before the at sign

The following characters (at sign, exclamation mark, hash, dollar, percent, caret, ampersand, asterisk, parenthesis, equal sign, bracket, chevron, comma, quotation marks, semicolon, question mark...) cannot be used to create an Infomaniak email address

This guide explains why some attachments sent from Microsoft Outlook arrive in winmail.dat format on your e-mail address hosted by Infomaniak, and how to permanently resolve the issue on the sender's side (where it originates).

Preamble

• winmail.dat is the container used by Outlook/Exchange when a message is sent in RTF / TNEF.
  • It encapsulates the formatting and attachments.
• Many non-Microsoft e-mail clients do not know how to interpret TNEF:
  • The formatting disappears and the attachments become a single winmail.dat file.

Resolving the issue (actions to request from the sender)

The most effective solution is to modify the Outlook configuration on the sender's side.

Disable RTF/TNEF and resend the message in HTML or plain text

• Classic Outlook for Windows (Microsoft 365/2021/2019, Win32 application)
  Menu: File > Options > Mail
  Composition: Compose messages in this format: select HTML (or Plain text).
  Message format: in When sending messages in Rich Text format to Internet recipients, select Convert to HTML (or Convert to plain text).
  Case by case (single e-mail): in the message window, tab Text format > select HTML.

• New Outlook for Windows (Outlook on the Web-based application)
  Menu: Settings (gear icon) > Mail > Compose and reply
  Message format: Compose messages in: select HTML (or Plain text).
  This client does not expose an RTF option; sending in HTML/text avoids winmail.dat.

• Outlook on the Web (Exchange Online/Outlook.com)
  Menu: Settings > Mail > Compose and reply > Message format > select HTML (or Plain text).

• Outlook for Mac
  Menu: Outlook > Preferences > Composition > check/uncheck Compose messages in HTML by default.
  For a single message: in the composition window, tab Options > toggle HTML or Plain text.

Notes: if the sender has attached files, they will be readable by all recipients as long as the message is sent in HTML/text. Zipping the attachments (.zip) does not prevent Outlook from encapsulating the message if RTF/TNEF is still active.

Disable RTF for specific recipients (you, for example)

• Classic Outlook Windows: open the Contact card > double-click the e-mail address > Outlook Properties > Internet Format: select Send as plain text only (or Let Outlook decide if the admin already forces the conversion).

• Clear the auto-complete (it may “remember” RTF for a recipient): File > Options > Mail > Send messages > Empty the Auto-Complete List, then retype the address manually for the next send.

• Microsoft 365 administrators (on the sender's side): in the Exchange Admin Center: Mail flow > Remote domains > Default > Rich Text format: select Never. In PowerShell: Set-RemoteDomain Default -TNEFEnabled $false.

Failing that: use another client to send (e.g., Thunderbird), or check that Calendar invitations are sent in iCalendar (File > Options > Calendar > enable Use iCalendar format for external recipients).

If you do not wish to recontact the sender

You can extract the content of winmail.dat with TNEF decoding tools (online or desktop applications). Search for “open winmail.dat” and choose a reputable tool for your system (Windows, macOS, Linux). This usually restores the attachments, but it is not a lasting fix. Moreover, privacy and security are not guaranteed during these operations.

This guide concerns Greylisting, a protective measure that is implemented on Infomaniak's mail servers.

How Greylisting Works

Greylisting is a technique used by Infomaniak's mail servers (among others) to combat spam. It relies on the principle of temporarily delaying the delivery of an email to verify the legitimacy of the sender. This method exploits the fact that spam servers often send emails without complying with message retransmission standards.

1. Initial Reception

When a mail server receives an email, it records three elements:

• the sender's IP address
• the sender's email address
• the recipient's email address

2. Temporary Rejection

The server temporarily rejects the delivery of the email and sends a temporary error message (4xx code). This means that the message is not permanently rejected, but the sending server must try to send it again later.

3. Retry

Legitimate mail servers are programmed to retry delivering messages after a certain delay. Spam servers, on the other hand, often do not bother to retry.

4. Acceptance

Upon retry, if the email comes from the same trio (sender's IP, sender's address, recipient's address) noted previously, the message is accepted and delivered to the recipient.

This guide covers the steps to follow when you are healthcare professionals, Infomaniak customers, and wish to comply with the HIN system.

Preamble

• The acronym HIN stands for "Health Insurance Network".
• A HIN-type email address is an address used to send confidential and sensitive messages, such as medical records or test results, between healthcare professionals who have been authorized to use them.
• These addresses are protected by additional security measures to ensure that sensitive information does not fall into the wrong hands.

Obtain an encrypted HIN email address

For your Infomaniak email address to be HIN-compatible:

1. Click here to access the page of services offered by HIN and subscribe to their offer.
2. Contact Infomaniak support in writing as soon as a contract is concluded, clearly mentioning the address(es) concerned (pay special attention to the domain name and its extension .com, .ch etc.).
3. Wait for HIN to notify Infomaniak and for the solution to be implemented (several hours or days).

This guide helps you find the public IP address of your device, which can be useful for certain support requests, among other things.

Display the public IP address on the connected device

Click here to obtain the public IP address of your device in IPv4 and IPv6 format.

Alternative methods

Visit ipinfo.io or ifconfig.me.

... on macOS

1. From a Terminal type application (command-line interface, CLI / Command Line Interface) on your device, run the command curl ifconfig.me and press enter.
2. The displayed address is the public IP address of the computer.

To automate the search for the public IP address, use commands or scripts that query services such as api.ipify.org ...

This guide explains how to connect the mobile app Microsoft Outlook (application for smartphone or tablet iOS / Android) to an email address hosted by Infomaniak.

Preamble

• The app Outlook Lite is not compatible with the IMAP protocol… Only install the version offered above.
• Instead of the manual configuration below, it is recommended to use the app Infomaniak Mail (iOS / Android).
• The various services offered by Infomaniak are all compatible with the corresponding standard protocols (IMAP/SMTP for email, for example), therefore if you encounter a problem with third-party software, contact its publisher or a Partner and consult the support policy as well as article 11.9 of the Infomaniak Terms of Service.

Add the email address to the application

Prerequisites

• Create the email address within my kSuite or a Mail Service / kSuite.
• Create a password for the email address for the device you are going to configure.

To configure the email application:

1. Open the application.
2. Click on Add an account:
   
3. Enter the email address to be linked.
4. Click on Continue:
   
5. Click on IMAP:
   
6. Check and complete the missing information.
7. Click on the icon ✓ at the top right.
8. Click on the left to complete the configuration:
   
9. That's it, your email address is now configured in the application:
   

Recommended settings

• Incoming IMAP server = mail.infomaniak.com
• IMAP port = 993 (with SSL)
• Outgoing SMTP server = mail.infomaniak.com
• SMTP port & encryption protocol and command/method to activate this protocol: 587 + STARTTLS
• Username = full & complete email address ( ? )
• Password = the one generated for the email address you want to access
• Authentication required for sending emails:
  • It is activated in the SMTP settings of your application.
  • Check "use the same parameters as the incoming server" or, depending on the software/email clients, enter a username (= full & complete email address) and the generated password.

Refer to this other guide if you are looking for information about other compatible messaging ports and protocols (SSL / TLS for example).

In case of problem

Check that the Mail Service is configured optimally.

It is not necessary to contact Infomaniak Support if your email address works well outside the application. The most common error concerns the use of an incorrect password. The troubleshooting guides help you resolve any potential issues:

• Refer to the solutions given in this other guide regarding email in general.
• This other guide is more specifically about Outlook.

… and if your Outlook no longer works since a change of email password, refer to this other guide.

This guide details the security measures implemented as part of the Infomaniak email offers to detect abusive and abnormal use of an email address. These measures protect you from malicious use of your computer or your account.

Number of recipients per email

Regardless of the email offer chosen, whether it is free or paid, the total number of recipients per message is limited to 100.

This restriction applies regardless of the field used to insert the email addresses of the recipients (To, CC, or BCC).

Other email limits

• Outgoing email limits per 24 hours
• Email size limits

This guide details how to disable the SMTP protocol, thereby preventing a specific user from sending emails from a specific email address.

Preamble

• Removing the sending right from a user will prevent them from sending a message (new, reply, reaction, etc.) from the Infomaniak Web Mail app (online service ksuite.infomaniak.com/mail) and the mobile app.
• If the user in question is also specified in the connected devices, sending will also be impossible from a software/email client like Outlook, Apple Mail, Thunderbird, etc.
• There is a specific permission regarding out-of-office messages if you also want to prevent this type of message from being sent.

Prevent a user from sending messages from a specific email address

New user

Do you want to allow a new collaborator to access an email address (be able to read incoming emails) but without allowing them to send new messages?

1. Click here to access the management of your Mail Service on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the Mail Service concerned:
   
3. Click on the email address concerned in the table that appears:
   
4. Click to Add a new user:
   
5. In this example, the collaborator is external, so click to Create an invitation link.
6. Click to manage the permissions of this user on the email address concerned:
   
7. Click on Send emails to remove their sending rights.
8. Save the change:
   
9. Click on Add to complete the invitation:
   
10. Enter an email address to which to send the invitation.
11. Click on Send:
    

The invited user accepts the invitation: they thus access the email address and its messages, but the button to compose a new message will remain grayed out with no possibility for them to draft a message (or even reply, react, etc. as these buttons will also be grayed out/deactivated):

Prevent sending to an existing user

Do you want to allow collaborators to continue to access an email address (be able to read incoming emails) but without allowing them to send new messages?

1. Click here to access the management of your Mail Service on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the Mail Service concerned:
   
3. Click on the email address concerned in the table that appears:
   
4. Click on Send emails to remove the send permission:
   

The user will access the email address and its messages, but the button to compose a new message will remain grayed out with no possibility for them to draft a message (or even reply, react, etc. as these buttons will also be grayed out/deactivated):

Prevent sending from an SMTP email client/software

If you want to prevent the user from sending emails from an email client/software or any fixed and mobile device containing an SMTP email app, start by following the steps above.

You will then need to create a password (= "connected device") linked to this user (so at point 8 of this other guide instead of “Without user” you will need to specify the identifier of the collaborator concerned, already added in the users tab):

Thus, their email client/software can be configured to receive emails but will not allow any sending, causing a continuous error (password request) if the user insists on sending an email:

This guide presents commands that can be executed to test a connection or a network and thus specify the source of a potential error.

Perform a Telnet...

TELNET allows you to test the connection to a server without considering all the additional settings of a mail or FTP application in order to determine the origin of a problem. If the connection does not go through on an SMTP server, for example, you will need to check if your firewall is not blocking port 587 or 465.

... on macOS

1. Search for Network Utility.
2. Go to the Ping, Lookup, or Traceroute tab depending on what you want to test.
3. You can also use a Terminal type application (command line interface, CLI / Command Line Interface) on your device and, depending on what you want to test, enter:
   traceroute [server]
nc [server] [port]
   Replace [server] with the server name or its IP address, same for [port]...

... on Windows

Enable Telnet if necessary.

1. Use a Terminal type application (command line interface, CLI / Command Line Interface) on your device, for example by typing Run then cmd.
2. In the window that opens, depending on what you want to test, type:
   tracert [server]
telnet [server] [port]
   Example: telnet mail.infomaniak.com 587 (allows you to test the SMTP port if your software/email client does not allow sending emails)...

... on Android

1. Use the application Simple Telnet Client which allows you to test very simply via 2 fields to fill in (for example mail.infomaniak.com and port 143 or 993)...

Perform a PING

PING allows you to know if a machine is accessible via the Internet. You can also check with this tool if you are addressing the correct machine, for example during a DNS change, by looking at the IP address obtained. It is possible to perform a ping on a domain name, a hostname or an IP address.

This guide explains the behavior of email in the case of a redirection activated on an email address managed with Infomaniak, and whose target is a Gmail address.

Message not displayed on Gmail

If you send an email…

• … from abc@gmail.com …
• … to xyz@domain.xyz (domain that you have with Infomaniak)…

… and this email address xyz@domain.xyz with Infomaniak has an automatic redirection…

• … to abc@gmail.com …

… then abc@gmail.com will never display your email as a new message in the inbox. Nothing will happen on Gmail.

Why?

The problem is not that the redirection does not work: it is rather a peculiarity of Gmail: an email from Gmail to an email address with Infomaniak redirected to the same Gmail address as the sender, will cause a problem on Gmail's side, in the way it handles email.

Your message will never arrive (because in fact, for it, it is already in the inbox, in the sent items). In this case, you need to delete the redirection of emails.