Alice Mail addresses (@alice.it) date back to Telecom Italia’s old ADSL and internet branding, and while the “Alice” name was retired for new customers around 2010, long-time users can still access their @alice.it inbox through the TIM Mail webmail portal. When something breaks, though, the error messages TIM shows aren’t always self-explanatory. This guide walks through what each one actually means and how to get back into your inbox.<\/p>\n
TLDR<\/h3>\n\n- Check whether it’s a general TIM outage before troubleshooting your own account \u2014 use Angie, TIM’s virtual assistant, on the TIM Mail help page.<\/li>\n
- Error Feube001<\/strong> and 71003<\/strong> are server-side issues on TIM’s infrastructure \u2014 waiting it out or contacting support is usually the only fix.<\/li>\n
- Error 71001<\/strong> and messages like “username, password or client certificate incorrect”<\/em> mean your login credentials are wrong \u2014 recheck them or reset your password.<\/li>\n
- If Alice Mail works on the website but not in Outlook, Thunderbird, or your phone’s mail app, the problem is almost always your mail client’s IMAP\/SMTP configuration, not TIM’s servers.<\/li>\n
- Error 554<\/strong> on outgoing mail usually means you tripped an antispam limit, often from sending to too many recipients at once.<\/li>\n<\/ul>\n<\/div>\n\n
On this page<\/h3>\n\n- Is Alice Mail down right now, or is it just you?<\/a><\/li>\n
- Alice Mail error codes explained<\/a><\/li>\n
- Fixing server-side errors (Feube001, 71003)<\/a><\/li>\n
- Fixing login errors (71001, invalid credentials)<\/a><\/li>\n
- Webmail works but Outlook or your phone app doesn’t<\/a><\/li>\n
- Fixing outgoing mail and error 554<\/a><\/li>\n
- Frequently asked questions<\/a><\/li>\n<\/ul>\n<\/div>\n
Is Alice Mail down right now, or is it just you?<\/h2>\n
Before you touch any settings, rule out a general outage on TIM’s side. Alice Mail addresses are serviced through the TIM Mail platform, and TIM runs a built-in diagnostic through its virtual assistant:<\/p>\n
\n- Go to the TIM Mail help page (search “Guida TIM Mail” if you don’t have the link saved).<\/li>\n
- Click the Angie chat icon in the bottom-right corner.<\/li>\n
- If Angie doesn’t run the check automatically, type mail_portale<\/strong> into the chat box.<\/li>\n
- Wait for the progress bar to complete.<\/li>\n<\/ol>\n
![\"Alice](\"https:\/\/seminarsonly.com\/news\/wp-content\/uploads\/2026\/07\/alice-mail-featured.jpg\")
<\/p>\n
If Angie reports that the mail service is working normally with no widespread faults detected, the problem is isolated to your account, device, or app configuration \u2014 skip ahead to the section that matches your situation. If it reports an active fault, there’s nothing to fix on your end; you’ll need to wait for TIM to resolve it.<\/p>\n
Also Read : ZEE5 Customer Care Number<\/a><\/h3>\nAlice Mail error codes explained<\/h2>\n
Here’s what each commonly reported error actually means:<\/p>\n
\n\n\nError<\/th>\n What it means<\/th>\n Where the fault usually sits<\/th>\n<\/tr>\n<\/thead>\n \n\nFeube001<\/strong><\/td>\nMailbox can’t be reached<\/td>\n TIM’s servers<\/td>\n<\/tr>\n \n71003<\/strong><\/td>\nGeneral mail service fault<\/td>\n TIM’s servers<\/td>\n<\/tr>\n \n71001<\/strong><\/td>\nUsername or password entered incorrectly<\/td>\n Your credentials<\/td>\n<\/tr>\n \n403<\/strong><\/td>\nAccess forbidden while loading the mail portal<\/td>\n Usually TIM’s servers, sometimes browser\/cache<\/td>\n<\/tr>\n \n“Username, password or client certificate incorrect” \/ code 535<\/strong><\/td>\nInvalid login when connecting through a mail app<\/td>\n Your credentials or client setup<\/td>\n<\/tr>\n \n554<\/strong><\/td>\nOutbound antispam rule triggered<\/td>\n Your sending pattern (e.g. mass recipients)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nFixing server-side errors (Feube001, 71003)<\/h2>\n
These two are the ones you genuinely can’t fix by changing settings, because the fault sits on TIM’s infrastructure, not your account.<\/p>\n
\n- Wait a couple of hours and try again \u2014 both errors typically resolve on their own once TIM’s systems recover.<\/li>\n
- If it’s still happening after a few hours, contact TIM support and give them the exact error code \u2014 that speeds up diagnosis on their end.<\/li>\n
- As a workaround while you wait, changing your device’s DNS to Google (8.8.8.8 \/ 8.8.4.4) or Cloudflare (1.1.1.1 \/ 1.0.0.1) occasionally resolves connectivity that looks like a mail fault but is actually a DNS routing issue.<\/li>\n<\/ul>\n
Fixing login errors (71001, invalid credentials)<\/h2>\n
If Angie confirms there’s no general fault and you’re getting a credentials-related error, the fix is usually straightforward:<\/p>\n
On this page<\/h3>\n\n- Is Alice Mail down right now, or is it just you?<\/a><\/li>\n
- Alice Mail error codes explained<\/a><\/li>\n
- Fixing server-side errors (Feube001, 71003)<\/a><\/li>\n
- Fixing login errors (71001, invalid credentials)<\/a><\/li>\n
- Webmail works but Outlook or your phone app doesn’t<\/a><\/li>\n
- Fixing outgoing mail and error 554<\/a><\/li>\n
- Frequently asked questions<\/a><\/li>\n<\/ul>\n<\/div>\n
Is Alice Mail down right now, or is it just you?<\/h2>\n
Before you touch any settings, rule out a general outage on TIM’s side. Alice Mail addresses are serviced through the TIM Mail platform, and TIM runs a built-in diagnostic through its virtual assistant:<\/p>\n
\n- Go to the TIM Mail help page (search “Guida TIM Mail” if you don’t have the link saved).<\/li>\n
- Click the Angie chat icon in the bottom-right corner.<\/li>\n
- If Angie doesn’t run the check automatically, type mail_portale<\/strong> into the chat box.<\/li>\n
- Wait for the progress bar to complete.<\/li>\n<\/ol>\n
<\/p>\n
If Angie reports that the mail service is working normally with no widespread faults detected, the problem is isolated to your account, device, or app configuration \u2014 skip ahead to the section that matches your situation. If it reports an active fault, there’s nothing to fix on your end; you’ll need to wait for TIM to resolve it.<\/p>\n
Also Read : ZEE5 Customer Care Number<\/a><\/h3>\nAlice Mail error codes explained<\/h2>\n
Here’s what each commonly reported error actually means:<\/p>\n
\n\n\nError<\/th>\n What it means<\/th>\n Where the fault usually sits<\/th>\n<\/tr>\n<\/thead>\n \n\nFeube001<\/strong><\/td>\nMailbox can’t be reached<\/td>\n TIM’s servers<\/td>\n<\/tr>\n \n71003<\/strong><\/td>\nGeneral mail service fault<\/td>\n TIM’s servers<\/td>\n<\/tr>\n \n71001<\/strong><\/td>\nUsername or password entered incorrectly<\/td>\n Your credentials<\/td>\n<\/tr>\n \n403<\/strong><\/td>\nAccess forbidden while loading the mail portal<\/td>\n Usually TIM’s servers, sometimes browser\/cache<\/td>\n<\/tr>\n \n“Username, password or client certificate incorrect” \/ code 535<\/strong><\/td>\nInvalid login when connecting through a mail app<\/td>\n Your credentials or client setup<\/td>\n<\/tr>\n \n554<\/strong><\/td>\nOutbound antispam rule triggered<\/td>\n Your sending pattern (e.g. mass recipients)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nFixing server-side errors (Feube001, 71003)<\/h2>\n
These two are the ones you genuinely can’t fix by changing settings, because the fault sits on TIM’s infrastructure, not your account.<\/p>\n
\n- Wait a couple of hours and try again \u2014 both errors typically resolve on their own once TIM’s systems recover.<\/li>\n
- If it’s still happening after a few hours, contact TIM support and give them the exact error code \u2014 that speeds up diagnosis on their end.<\/li>\n
- As a workaround while you wait, changing your device’s DNS to Google (8.8.8.8 \/ 8.8.4.4) or Cloudflare (1.1.1.1 \/ 1.0.0.1) occasionally resolves connectivity that looks like a mail fault but is actually a DNS routing issue.<\/li>\n<\/ul>\n
Fixing login errors (71001, invalid credentials)<\/h2>\n
If Angie confirms there’s no general fault and you’re getting a credentials-related error, the fix is usually straightforward:<\/p>\n
Is Alice Mail down right now, or is it just you?<\/h2>\n
Before you touch any settings, rule out a general outage on TIM’s side. Alice Mail addresses are serviced through the TIM Mail platform, and TIM runs a built-in diagnostic through its virtual assistant:<\/p>\n
- \n
- Go to the TIM Mail help page (search “Guida TIM Mail” if you don’t have the link saved).<\/li>\n
- Click the Angie chat icon in the bottom-right corner.<\/li>\n
- If Angie doesn’t run the check automatically, type mail_portale<\/strong> into the chat box.<\/li>\n
- Wait for the progress bar to complete.<\/li>\n<\/ol>\n
<\/p>\nIf Angie reports that the mail service is working normally with no widespread faults detected, the problem is isolated to your account, device, or app configuration \u2014 skip ahead to the section that matches your situation. If it reports an active fault, there’s nothing to fix on your end; you’ll need to wait for TIM to resolve it.<\/p>\n
Also Read : ZEE5 Customer Care Number<\/a><\/h3>\n
Alice Mail error codes explained<\/h2>\n
Here’s what each commonly reported error actually means:<\/p>\n
\n\n
\n \nError<\/th>\n What it means<\/th>\n Where the fault usually sits<\/th>\n<\/tr>\n<\/thead>\n \n Feube001<\/strong><\/td>\n Mailbox can’t be reached<\/td>\n TIM’s servers<\/td>\n<\/tr>\n \n 71003<\/strong><\/td>\n General mail service fault<\/td>\n TIM’s servers<\/td>\n<\/tr>\n \n 71001<\/strong><\/td>\n Username or password entered incorrectly<\/td>\n Your credentials<\/td>\n<\/tr>\n \n 403<\/strong><\/td>\n Access forbidden while loading the mail portal<\/td>\n Usually TIM’s servers, sometimes browser\/cache<\/td>\n<\/tr>\n \n “Username, password or client certificate incorrect” \/ code 535<\/strong><\/td>\n Invalid login when connecting through a mail app<\/td>\n Your credentials or client setup<\/td>\n<\/tr>\n \n 554<\/strong><\/td>\n Outbound antispam rule triggered<\/td>\n Your sending pattern (e.g. mass recipients)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Fixing server-side errors (Feube001, 71003)<\/h2>\n
These two are the ones you genuinely can’t fix by changing settings, because the fault sits on TIM’s infrastructure, not your account.<\/p>\n
- \n
- Wait a couple of hours and try again \u2014 both errors typically resolve on their own once TIM’s systems recover.<\/li>\n
- If it’s still happening after a few hours, contact TIM support and give them the exact error code \u2014 that speeds up diagnosis on their end.<\/li>\n
- As a workaround while you wait, changing your device’s DNS to Google (8.8.8.8 \/ 8.8.4.4) or Cloudflare (1.1.1.1 \/ 1.0.0.1) occasionally resolves connectivity that looks like a mail fault but is actually a DNS routing issue.<\/li>\n<\/ul>\n
Fixing login errors (71001, invalid credentials)<\/h2>\n
If Angie confirms there’s no general fault and you’re getting a credentials-related error, the fix is usually straightforward:<\/p>\n
- Wait for the progress bar to complete.<\/li>\n<\/ol>\n