ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Getting error from email retrieve for yahoo. Doc at yahoo says is TB bug needs caps on imap cmd.

  • 2 (ردّان اثنان)
  • 1 has this problem
  • 1 view
  • آخر ردّ كتبه harley91stc

more options

Getting mail on windows TB from yahoo imap seeing message "The current operation on 'Inbox' did not suceed. The mail server for the account ricc@ricchardingsoftware.com responded: [CLIENTBUG] SELECT Command is not valid in this state." Looked at several problems that are similar and developer dialog went to tahoo to TB with TB going to capitalize the IMAP command names was last exchange I saw on July 16 2017. I am on latest TB release but still cannot get mail from yahoo... Can someone help me out with what I am missing to get thye fix for this or is it just in the pipeline somewhere being done? aTdHvAaNnKcSe Harley

Getting mail on windows TB from yahoo imap seeing message "The current operation on 'Inbox' did not suceed. The mail server for the account ricc@ricchardingsoftware.com responded: [CLIENTBUG] SELECT Command is not valid in this state." Looked at several problems that are similar and developer dialog went to tahoo to TB with TB going to capitalize the IMAP command names was last exchange I saw on July 16 2017. I am on latest TB release but still cannot get mail from yahoo... Can someone help me out with what I am missing to get thye fix for this or is it just in the pipeline somewhere being done? aTdHvAaNnKcSe Harley

الحل المُختار

All Replies (2)

more options

الحل المُختار

Did you try any of the steps cited here?

https://support.mozilla.org/en-US/questions/1168740

more options

changing the server to att.net allowed me to receive the email since I have an account on att.net... then with no other change switched back to yahoo.com and it works again... guess it was just needing to get out of that "state" that it was in... Hysteria, or confusion... one of those states I think... yes, the suggestion to switch server out (and then I switched it back) did whatever was necessary to fix the state... I had installed the beta too though so maybe working together... (beta 55)