The dbmail.com messaging service, a remnant of the DartyBox era, now operates on Microsoft’s Outlook infrastructure. This technical migration, rarely detailed in consumer guides, profoundly changes how to connect, secure your account, and resolve sending issues. Here, we outline the technical points that truly pose problems for users of this messaging service.
POP3 and SMTP Protocols on dbmail.com: Updated Server Settings
The switch of dbmail.com to Microsoft servers requires specific settings that many users have never updated in their email client. The old DartyBox settings no longer work and cause looping authentication errors.
For clients like Thunderbird or Outlook desktop, the settings to enter are as follows:
- Incoming POP server: pop3.live.com, port 995, SSL/TLS encryption, normal password authentication
- Outgoing SMTP server: smtp.live.com, port 587, STARTTLS encryption, authentication required with the same credentials
- Username: the full address in @dbmail.com, associated with the linked Microsoft account password
The most common error we observe concerns the SMTP port. Many old configurations used port 25 (unencrypted), which is now blocked by Microsoft. Switching to port 587 with STARTTLS is the only functional combination for sending.
If your client displays “Logon failure: unknown user name or bad password” after correctly entering the password, the issue generally does not stem from the password itself. It arises from the fact that the associated Microsoft account requires modern authentication (OAuth2) that some older clients do not support. Thunderbird has supported OAuth2 since version 78, but sometimes you need to delete the account in the software and recreate it to force the switch of the authentication protocol.
If you wish to access the Dbmail Darty messaging service without using a heavy client, the Outlook.com webmail remains the most direct solution: log in with the @dbmail.com address and the Microsoft password.
Email Blocking to Gmail from dbmail.com: A Domain Reputation Issue
Emails sent from dbmail.com to Gmail are frequently rejected, and this is not a sporadic bug. The problem is structural.
Google has tightened its filtering policies for sender domains that do not meet SPF, DKIM, and DMARC authentication standards. However, the dbmail.com domain, historically managed by a French ISP and then transferred to Microsoft, suffers from a degraded sender reputation. Gmail servers interpret some dbmail.com emails as potentially non-compliant and reject them with a postmaster message such as “the recipient’s mail provider rejected it.”
We recommend two approaches to address this blocking:
Check Alias Configuration in Outlook
Log in to account.microsoft.com and verify that the @dbmail.com address is correctly declared as the primary alias. A misconfigured alias can lead to sending from a default @outlook.fr address, creating an inconsistency between the “From” header and the SMTP envelope. This inconsistency is enough to trigger a rejection on the Gmail side.
Use an Alternative Sending Domain for Gmail Contacts
If the blocking persists despite a clean configuration, the pragmatic solution remains to create a Gmail address or a free alias (GMX, for example) to correspond with Gmail recipients. This is not an elegant solution, but the reputation of the dbmail.com domain does not depend on the end user: it is the responsibility of Microsoft and the domain’s history.
Securing a dbmail.com Account via the Microsoft Ecosystem
A dbmail.com account is a Microsoft account. Therefore, the entire security chain goes through the Microsoft portal, not Darty.
Enabling two-step verification is the top security measure. It can be configured from the “Security” page of the Microsoft account (account.microsoft.com/security). Available options include the Microsoft Authenticator app, a phone number, or a backup email address.
A technical point often overlooked: once two-step verification is enabled, email clients that do not support OAuth2 will no longer be able to log in with the main password. You will need to generate an “app password” from the Microsoft security portal. This specific password replaces the usual password only in the email client authentication field.
For password recovery, Microsoft does not recognize old DartyBox credentials. The procedure goes exclusively through the Microsoft recovery form (account.live.com/password/reset). If no recovery method (phone, secondary email) has been associated with the account, the only remaining option is the manual identity verification form, which can take several days to process.
dbmail.com Migration and Address Longevity After Darty Termination
The question of the survival of a dbmail.com address after the termination of a DartyBox subscription arises regularly. The address remains functional since it is hosted by Microsoft, not by the ISP. Terminating the Darty internet subscription does not delete the email account.
This situation is part of a broader trend among French ISPs: outsourcing email services to major cloud players. SFR also uses a shared infrastructure, and former DartyBox subscribers are entirely dependent on Microsoft’s service conditions for the preservation of their mailbox.
The real risk is not immediate deletion, but prolonged inactivity. Microsoft reserves the right to disable an account after a long period without connection. We recommend logging into the Outlook webmail at least once a month to keep the account active, even if you no longer use the dbmail.com address as your primary email.
Data portability remains possible via export to PST format from Outlook or via the IMAP protocol (server imap-mail.outlook.com, port 993, SSL) to transfer archives to another provider.