Virgilio Mail: IMAP, SMTP and the recovery-email field
You have a Virgilio.it mailbox and want to open it in a mail app. Browser sign-in works, but the app asks for incoming and outgoing servers. Start with the distinction that matters: reading mail and sending mail are separate connections.
This guide explains the provider settings and the email:pass:backup-mail delivery layout. Our Virgilio packages are listed as IMAP/SMTP verified. That description does not replace a check in your chosen app, and it is not a promise of unlimited sending.
What the three fields mean
In this layout, email is the full mailbox address, pass is its password, and backup-mail is the recovery address. They are not three credentials that all belong in an IMAP login form.
The recovery address is not an SMTP server or an OAuth token. An address alone also does not prove that you can open the recovery mailbox. If control of that mailbox is a requirement, ask exactly which credentials are delivered before buying. Do not infer it from a column heading.
A placeholder-only example is ADDRESS:PASSWORD:RECOVERY_ADDRESS. Keep actual delivery rows out of public support chats. Field names and a description of where the import stops are enough to discuss the layout without disclosing credentials.
Virgilio.it IMAP and SMTP settings
Virgilio’s official client setup guide lists these manual settings:
| Purpose | Server | Port | Security |
|---|---|---|---|
| IMAP receiving and synchronization | in.virgilio.it | 993 | SSL/TLS |
| SMTP sending | out.virgilio.it | 465 | SSL/TLS |
Use the complete email address as the username. SMTP requires authentication. After changing a mailbox password, update the apps where it is saved. Do not copy Outlook.com server settings just because you are using the Outlook application: the app and the mailbox provider are different things.
What does “IMAP/SMTP verified” tell you?
It is the package’s stated protocol-access status. The phrase alone does not specify when the check happened, which app was used, or the test conditions. Ask support for those details if your purchase depends on a particular workflow.
Signing in on the website does not test SMTP. Seeing a folder in an app does not prove that a new message arrives correctly either. Keep three separate results: web access, IMAP reading, and SMTP sending.
A small connection check before importing everything
- Check one mailbox through the official Virgilio Mail website.
- Add it to your app using the settings above. If it already has a POP configuration, consult the provider’s migration instructions before changing the protocol.
- Send a test message from another address you control and check that it appears in the app.
- Reply from Virgilio and check the destination inbox. This tests sending separately from receiving.
- Record the app, version and any error with sensitive values removed. Resolve problems before importing more mailboxes.
If receiving works but sending fails
Focus on SMTP instead of changing the incoming settings too. Virgilio’s sending and receiving troubleshooting page recommends comparing webmail with the client. Also check the recipient address and whether your network blocks the connection.
A delivery-failure notice is not necessarily a password problem. Save the error text without credentials and say which checks succeeded. “Reading works, but sending returns this error” gives support a much better starting point than “It does not work.”
Before choosing a package size
Confirm the file layout, your app’s requirements and the recovery details first. Then compare the current Virgilio package prices. More mailboxes do not change provider rules, guarantee inbox placement or automatically include API access or OAuth credentials.
Need a specific check before ordering? Contact support with your app name and required functions. Keep live passwords out of public messages.