sending of password for user xxxxx did not success. Mail server responded , authentication failed!
This happened to me serveral times in past decade. Yes, I am very busy and never clean my inbox, No need to with other clients!
Everytime, my inbox hit around 10000 messages or large size
then I get locked out and can't login back into my pop mail server to retrieve. there is nothing wrong with my mailserver and I can access it from other mail clients just fine.
I thought this would have been fixed by now! this is not the first time!
So inbox integrity goes out of wack and limitation hits and i keep deleting message and compacting to no avail!
other clients works just fine.
Need solution.
I don't need any answer who is blaming the user or ISP mailservers! This is my own mailserver.
In the past I had to rebuild the inbox on thunderbird , with a procedure ! such a pain! Please send me the link to that procedure.
被采纳的解决方案
Issue resolved!
Summary: Windows workstation Thunderbird will not be able to finish negotiation with qpopper entirely!
All outbound activities were working fine on the workstation, except Thunderbrid or any other mail clients on the workstation were not able to fetch mail from one mailserver. Port 100 of mailserver was sort of telnetable, except without qpopper welcome message: +OK Qpopper (version 4.0.5) at 'servername' starting.
All other workstations can get to mailserver and operate and telnet message were including qpopper message and service interface were up.
qpopper was complaining about this client!
qpopper[3494]: [ID 702911 local0.notice] (null) at localhost (127.0.0.1): -ERR POP timeout from servername
Windows workstation network state outbound to this one pop mail server or perhaps other pop servers were critically disturbed!
However, interestingly enough another virtualbox ubuntu vm was able to telnet successfuly from same windows machine!
You figure! How can the OS of the workstation not be able to communicate with mailserver but a vm inside just launched fresh can communciate fine.
Reboot on windows workstation solved the issue! Nothing was done on mailserver.
unstable state after I had installed a program or somthing got updated that restricted proper communication protocol oubound network request to port 110!
Loved it! Was fun to see telnet half way responding , find qpopper debug syslogd message, fire up another a vm and be suprirsed!
Hope this helps someone else who runs to issue with pop, This was not a thunderbird issue. My bad! but I have worked with corruped mailbox with thunderbird before!
Enjoy!
定位到答案原位置 👍 0所有回复 (1)
选择的解决方案
Issue resolved!
Summary: Windows workstation Thunderbird will not be able to finish negotiation with qpopper entirely!
All outbound activities were working fine on the workstation, except Thunderbrid or any other mail clients on the workstation were not able to fetch mail from one mailserver. Port 100 of mailserver was sort of telnetable, except without qpopper welcome message: +OK Qpopper (version 4.0.5) at 'servername' starting.
All other workstations can get to mailserver and operate and telnet message were including qpopper message and service interface were up.
qpopper was complaining about this client!
qpopper[3494]: [ID 702911 local0.notice] (null) at localhost (127.0.0.1): -ERR POP timeout from servername
Windows workstation network state outbound to this one pop mail server or perhaps other pop servers were critically disturbed!
However, interestingly enough another virtualbox ubuntu vm was able to telnet successfuly from same windows machine!
You figure! How can the OS of the workstation not be able to communicate with mailserver but a vm inside just launched fresh can communciate fine.
Reboot on windows workstation solved the issue! Nothing was done on mailserver.
unstable state after I had installed a program or somthing got updated that restricted proper communication protocol oubound network request to port 110!
Loved it! Was fun to see telnet half way responding , find qpopper debug syslogd message, fire up another a vm and be suprirsed!
Hope this helps someone else who runs to issue with pop, This was not a thunderbird issue. My bad! but I have worked with corruped mailbox with thunderbird before!
Enjoy!