Thunderbird error 80004005
Solved
Le Gardian
Posted messages
397
Status
Membre
-
Bardom -
Bardom -
Hello,
For almost a week I've been encountering this type of error when I try to send a message via Thunderbird and the server "laposte.net":
>>>>>>>>>thunderbird:
The message could not be sent.
Failure due to an unexpected error 80004005. No description is available.
The message could not be sent using the outgoing server (SMTP) "smtp.laposte.net" for an unknown reason. Please check that your outgoing server (SMTP) settings are correct and try again.
<<<<<<<<
1- I have several systems (win7, 10, and Debian). all give me the same error.
2- If I write via the webmail of "laposte.net" it works.
3- For security, I normally only use "aliases" or disposable addresses.
4- Using the primary address works.
Of course, I haven't made any recent changes to my accounts.
Other accounts like those from "free" work perfectly fine.
Is it "laposte.net" or is it me?
Additionally, I can't reach "laposte.net" because I get lost in the maze of their questionnaire.
Thank you for your help.
For almost a week I've been encountering this type of error when I try to send a message via Thunderbird and the server "laposte.net":
>>>>>>>>>thunderbird:
The message could not be sent.
Failure due to an unexpected error 80004005. No description is available.
The message could not be sent using the outgoing server (SMTP) "smtp.laposte.net" for an unknown reason. Please check that your outgoing server (SMTP) settings are correct and try again.
<<<<<<<<
1- I have several systems (win7, 10, and Debian). all give me the same error.
2- If I write via the webmail of "laposte.net" it works.
3- For security, I normally only use "aliases" or disposable addresses.
4- Using the primary address works.
Of course, I haven't made any recent changes to my accounts.
Other accounts like those from "free" work perfectly fine.
Is it "laposte.net" or is it me?
Additionally, I can't reach "laposte.net" because I get lost in the maze of their questionnaire.
Thank you for your help.
19 réponses
I just found a solution for Thunderbird.
Go to "account settings".
Select the account "alias" in question.
At the bottom of the window, select "Edit SMTP server".
In the new window, replace the "username" alias with the main account name.
For me, it's working... now I just need to find a solution for the Android email client...
Go to "account settings".
Select the account "alias" in question.
At the bottom of the window, select "Edit SMTP server".
In the new window, replace the "username" alias with the main account name.
For me, it's working... now I just need to find a solution for the Android email client...
Hello,
In fact, I had the same issue (unable to send my ***@*** either via Thunderbird or my Android, all of a sudden, without any changes to the account or settings; receiving has always been fine)
I checked my settings on the laposte.net messaging site (tab "Preferences", then "Accounts" in the left column), and I noticed that my ***@*** address, the one I use daily, is an alias of ***@*** = main account that I do not use... I did this when I created my email address, several years ago, and I had forgotten.
The solution:
1- I changed, in server settings on Android:
Email address: ***@*** (the email I use)
Username: ***@*** (my main account)
Same in "Authentication required to send emails": ***@*** followed by my usual password
2- I changed in Thunderbird in "View settings for this account"/"Modify SMTP server": Username: ***@*** (my main account); I did not change anything else
I should clarify that previously, the email I use (***@***) appeared for both email address AND username, I never indicated the other... and it always worked.
I hope this can help you.
Chantal
In fact, I had the same issue (unable to send my ***@*** either via Thunderbird or my Android, all of a sudden, without any changes to the account or settings; receiving has always been fine)
I checked my settings on the laposte.net messaging site (tab "Preferences", then "Accounts" in the left column), and I noticed that my ***@*** address, the one I use daily, is an alias of ***@*** = main account that I do not use... I did this when I created my email address, several years ago, and I had forgotten.
The solution:
1- I changed, in server settings on Android:
Email address: ***@*** (the email I use)
Username: ***@*** (my main account)
Same in "Authentication required to send emails": ***@*** followed by my usual password
2- I changed in Thunderbird in "View settings for this account"/"Modify SMTP server": Username: ***@*** (my main account); I did not change anything else
I should clarify that previously, the email I use (***@***) appeared for both email address AND username, I never indicated the other... and it always worked.
I hope this can help you.
Chantal
If anyone is still struggling, I just found a solution (not having an alias like many other contributors but just one main address): I simply changed my password via the online space in the "My Account" section at the top right. You just need to enter the new password in Thunderbird, replacing the old one, and it works.
My problem was only with the "aliases". By modifying SMTP, everything works.
However, for security reasons, I strongly recommend using "aliases" that can be revoked/disposable, while the main address cannot, and if it gets hacked, it quickly becomes a nightmare, especially when it's the ISP.
I only use the main addresses for dealings with the service providers, "laposte.net", "free", etc...
However, for security reasons, I strongly recommend using "aliases" that can be revoked/disposable, while the main address cannot, and if it gets hacked, it quickly becomes a nightmare, especially when it's the ISP.
I only use the main addresses for dealings with the service providers, "laposte.net", "free", etc...
Successful operation for the Huawei Psmart 2019 Android smartphone.
First solution, manually configure as soon as this option appears.
Add an account "enter the alias name" then password to validate the incoming IMAP server.
Then configure the outgoing SMTP server by assigning it the name of the main account.
Second solution is to configure everything with the main account automatically, then modify the reception settings (synchronization options). Change the username by replacing it with the Alias.
First solution, manually configure as soon as this option appears.
Add an account "enter the alias name" then password to validate the incoming IMAP server.
Then configure the outgoing SMTP server by assigning it the name of the main account.
Second solution is to configure everything with the main account automatically, then modify the reception settings (synchronization options). Change the username by replacing it with the Alias.
Solution found for Thunderbird
Go to account settings.
Select the "alias" account in question.
At the bottom of the window, click Modify SMTP Server
In the new small window that opens, replace the username "alias" with the main account's name.
And it works for me.
Go to account settings.
Select the "alias" account in question.
At the bottom of the window, click Modify SMTP Server
In the new small window that opens, replace the username "alias" with the main account's name.
And it works for me.
Thank you for your response and your advice on the aliases. I had exactly the same issue sending from Thunderbird (68.5.0) with the smtp server of laposte.net. Since the end of January, it no longer recognized the alias I commonly use for the identifier and displayed an unexplained error message!
With version 68.4.2 it works for me. However, I modified the SMTP server settings to use my main address (I have been using an alias for years without any issues).
Whether on Win 7, Win 10, or Android on smartphone, nothing works. I have the following settings:
- server name: smtp.laposte.net
- port: 465 (default)
- connection security: SSL/TLS
- authentication method: Normal password
- username: [the part before the @ of my main address] (I have no alias)
The password is correct, I entered it again.
Everything related to receiving and copying in folders (including drafts) works very well with IMAP.
- server name: smtp.laposte.net
- port: 465 (default)
- connection security: SSL/TLS
- authentication method: Normal password
- username: [the part before the @ of my main address] (I have no alias)
The password is correct, I entered it again.
Everything related to receiving and copying in folders (including drafts) works very well with IMAP.
I have the same error.
Using the main address in the SMTP settings seems to work, but then Thunderbird gets stuck at 95-99% when trying to copy the message to the sent folder (which makes it impossible to be sure if it was sent correctly).
-UPDATE-
Apparently, it was related to Thunderbird; I had the same issue with other servers (Gmail, work...).
I applied the update and everything is resolved.
Using the main address in the SMTP settings seems to work, but then Thunderbird gets stuck at 95-99% when trying to copy the message to the sent folder (which makes it impossible to be sure if it was sent correctly).
-UPDATE-
Apparently, it was related to Thunderbird; I had the same issue with other servers (Gmail, work...).
I applied the update and everything is resolved.
Hello,
With the "free" server I have no problems. I rather feel the "bug" is on the "laposte.net" side. They unfortunately often have issues with the SMTP server. Well, I'm still waiting for the updates for Thunderbird. Otherwise, I'll raise the alarm with "laposte."
Thanks for the info.
With the "free" server I have no problems. I rather feel the "bug" is on the "laposte.net" side. They unfortunately often have issues with the SMTP server. Well, I'm still waiting for the updates for Thunderbird. Otherwise, I'll raise the alarm with "laposte."
Thanks for the info.
Same reactions since this week with Thunderbird, even updated with an Alias for a poste.net account...
I think it's time to ask "laposte.net"
I will try to do it on Monday through "LSF" (I am deaf!)
--
A poor lonesome Debianner....
I will try to do it on Monday through "LSF" (I am deaf!)
--
A poor lonesome Debianner....
The same problem has also been happening for several days; it is exclusively related to the .net mail service and their SMTP management. We can no longer send via an "alias" address, neither through a PC Thunderbird email client nor through an Android smartphone email client. The two "outages" occurred simultaneously for me.
I tried to communicate with the mail service using the address webmaster"at"laposte.net, which no longer works and redirects us to their "completely unresponsive" online help. Since it refers to obvious outages, our case doesn't fit into the criteria... I fear that the only solution left is to send a paper letter.
I tried to communicate with the mail service using the address webmaster"at"laposte.net, which no longer works and redirects us to their "completely unresponsive" online help. Since it refers to obvious outages, our case doesn't fit into the criteria... I fear that the only solution left is to send a paper letter.
There are dozens of other comments all over other sites: it's therefore massive and likely comes from La Poste rather than users.
There is a basic contact form: regardless of the case selected and the description of the situation provided, it gives general responses based on entered keywords, and it redirects to someone else at best. There is also an advanced form related to sending messages via SMTP: it is not suitable because it requires too much information (it's probably designed that way). I attempted to contact them via Twitter and there is no other means of communication than through the forms, no phone, no email address. The customer service is therefore likely overwhelmed and certainly does not want to be approached. La Poste, really...
There is a basic contact form: regardless of the case selected and the description of the situation provided, it gives general responses based on entered keywords, and it redirects to someone else at best. There is also an advanced form related to sending messages via SMTP: it is not suitable because it requires too much information (it's probably designed that way). I attempted to contact them via Twitter and there is no other means of communication than through the forms, no phone, no email address. The customer service is therefore likely overwhelmed and certainly does not want to be approached. La Poste, really...
Hello everyone, when I logged back in, I noticed that the messages I left the day before yesterday are gone! Too bad, I have solutions... We need to separate the incoming IMAP parameters and outgoing SMTP ones.
Let me continue:
Thunderbird: Tools/ Account Settings/ go to the account in question (envelope)/ at the bottom of the page, modify the SMTP server/ new window/ Username, change the “alias” name to the main account name.
For me, it works.
Android: Settings / sending settings/ same, change the username “alias” to the main account name.
It works for me too.
Let me continue:
Thunderbird: Tools/ Account Settings/ go to the account in question (envelope)/ at the bottom of the page, modify the SMTP server/ new window/ Username, change the “alias” name to the main account name.
For me, it works.
Android: Settings / sending settings/ same, change the username “alias” to the main account name.
It works for me too.
For me too, by changing the SMTP settings it works too.
But that does not solve the issue with the SMTP server of "laposte.net".
So, for now, I do not consider the problem resolved.
But that does not solve the issue with the SMTP server of "laposte.net".
So, for now, I do not consider the problem resolved.
Indeed, I think they've modified their access to the SMTP server by only making it available on the main account... without notifying the users. I doubt they'll reverse their decision! The problem can only be resolved 100% if the post office restores access to aliases. Now the procedure is straightforward and apparently allows sending emails as before.
Hello,
Actually, I had the same issue (unable to send my ***@*** either via Thunderbird or on my Android, suddenly, without any modification to the account or settings; receiving emails was always fine)
I went to check my settings on the laposte.net messaging site (under the "Preferences" tab, then "Accounts" in the left column), and I found out that my ***@*** address, the one I use daily, is an alias of ***@*** = main account that I don't use... I set this up when I created my email address several years ago, and I had forgotten.
The solution:
1- I changed, in server settings on Android:
Email address: ***@*** (the email I use)
Username: ***@*** (my main account)
Same in "Authentication required to send emails": ***@*** followed by my usual password
2- I changed in Thunderbird under "View settings for this account"/"Modify SMTP server": Username: ***@*** (my main account); I didn't change anything else
I want to clarify that before, the email I use (***@***) appeared at both the email address AND username level, I had never specified the other... and it always worked.
I hope this can help you.
Chantal
Actually, I had the same issue (unable to send my ***@*** either via Thunderbird or on my Android, suddenly, without any modification to the account or settings; receiving emails was always fine)
I went to check my settings on the laposte.net messaging site (under the "Preferences" tab, then "Accounts" in the left column), and I found out that my ***@*** address, the one I use daily, is an alias of ***@*** = main account that I don't use... I set this up when I created my email address several years ago, and I had forgotten.
The solution:
1- I changed, in server settings on Android:
Email address: ***@*** (the email I use)
Username: ***@*** (my main account)
Same in "Authentication required to send emails": ***@*** followed by my usual password
2- I changed in Thunderbird under "View settings for this account"/"Modify SMTP server": Username: ***@*** (my main account); I didn't change anything else
I want to clarify that before, the email I use (***@***) appeared at both the email address AND username level, I had never specified the other... and it always worked.
I hope this can help you.
Chantal
Thank you, JLHO!
Indeed, I had this issue for almost a month and couldn't find a solution. I kept running into the complexities of the customer service form, asking for information as "incomprehensible" to the average user as the IP address and the system log file—all for a simple SMTP error. This failure occurred spontaneously when I hadn't changed anything in my configuration: something must have changed in the SMTP server configuration, and we weren't informed about it. Indeed, for the username in my SMTP configuration, I had used an alias. By replacing it with my username as you advised, the problem was resolved like magic. So, THANK YOU!
Indeed, I had this issue for almost a month and couldn't find a solution. I kept running into the complexities of the customer service form, asking for information as "incomprehensible" to the average user as the IP address and the system log file—all for a simple SMTP error. This failure occurred spontaneously when I hadn't changed anything in my configuration: something must have changed in the SMTP server configuration, and we weren't informed about it. Indeed, for the username in my SMTP configuration, I had used an alias. By replacing it with my username as you advised, the problem was resolved like magic. So, THANK YOU!
Even though I haven't questioned "laposte.net" about this issue, I have a feeling that now the "aliases" depend directly on the main address, so it’s the same for the SMTP server.
That being said, I would have liked to know "laposte.net"'s opinion on this subject. It would be nice if they warned us about their changes. They just changed the "login" screen. But that’s only the visible part.
--
A poor lonesome Debianner....
That being said, I would have liked to know "laposte.net"'s opinion on this subject. It would be nice if they warned us about their changes. They just changed the "login" screen. But that’s only the visible part.
--
A poor lonesome Debianner....
Hello,
Receiving Thunderbird OK - Sending KO (note recent update of Thunderbird to 68.5.0)
Solution:
1- Solution with "Main Address" instead of "Alias" had no effect...
2- Login to the main site "Laposte.net" with the original password... then change the password in "My account" to 11 characters and a * (my original password being much longer and more complex!...)
3- In Thunderbird, delete the saved password (Tools\Options\Security\Passwords...)
4- Return to Thunderbird then confirm the new password with saving (incoming and outgoing)
5- Tested sending and it works! ...
Probably a problem following an update on password management (special characters, length, etc.)
I will test...later...saving a stronger password! ...
Addendum at 05:35
Noticing that I had done tests with my main account in Thunderbird (SMTP account settings), I wanted to put my "Alias" back, and there "oops!", error again on test sends...
I had to re-confirm the new password twice to "force" the identification and therefore establish that the chaining does not work between the main account and the "Alias" (is this normal? well, I don’t know...)
Receiving Thunderbird OK - Sending KO (note recent update of Thunderbird to 68.5.0)
Solution:
1- Solution with "Main Address" instead of "Alias" had no effect...
2- Login to the main site "Laposte.net" with the original password... then change the password in "My account" to 11 characters and a * (my original password being much longer and more complex!...)
3- In Thunderbird, delete the saved password (Tools\Options\Security\Passwords...)
4- Return to Thunderbird then confirm the new password with saving (incoming and outgoing)
5- Tested sending and it works! ...
Probably a problem following an update on password management (special characters, length, etc.)
I will test...later...saving a stronger password! ...
Addendum at 05:35
Noticing that I had done tests with my main account in Thunderbird (SMTP account settings), I wanted to put my "Alias" back, and there "oops!", error again on test sends...
I had to re-confirm the new password twice to "force" the identification and therefore establish that the chaining does not work between the main account and the "Alias" (is this normal? well, I don’t know...)
Addendum of 31-10-2020
I had time to notice that 25 characters for the password in "incoming" works, but not in "outgoing" (SMTP)!!! So it was necessary to stick to 19 for everything to work (in my opinion, they should have taken 20, but I'll leave it at that... anyway, <b>well done</b> for the consistency!)
I had time to notice that 25 characters for the password in "incoming" works, but not in "outgoing" (SMTP)!!! So it was necessary to stick to 19 for everything to work (in my opinion, they should have taken 20, but I'll leave it at that... anyway, <b>well done</b> for the consistency!)
It worked.
Well done for the tip.
I will do the same for other aliases.
It works for the others!