Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

I get an error on trying to download e-mail asking me to disable UIDL or XTND XLST. Where are these settings?

  • 1 отговор
  • 2 имат този проблем
  • 1 изглед
  • Последен отговор от Stans

more options

The full error reads: The POP3 mail server (pop.verizon.net) does not support UIDL or XTND XLST, which are required to implement the ``Leave on Server, ``Maximum Message Size or ``Fetch Headers Only options. To download your mail, turn off these options in the Server Settings for your mail server in the Account Settings window." I cannot find these setting in the Account Settings window and a search in the Help screen did not unearth these settings. Is this a know issue?

The full error reads: The POP3 mail server (pop.verizon.net) does not support UIDL or XTND XLST, which are required to implement the ``Leave on Server'', ``Maximum Message Size'' or ``Fetch Headers Only'' options. To download your mail, turn off these options in the Server Settings for your mail server in the Account Settings window." I cannot find these setting in the Account Settings window and a search in the Help screen did not unearth these settings. Is this a know issue?

Всички отговори (1)

more options

Yes, this is a known issue with Yahoo/Frontier/Verizon/AOL/AT&T or whatever they call themselves these days. I strongly recommend ditching POP for IMAP instead. See http://kb.mozillazine.org/Yahoo#The_POP3_email_server_.28plus.pop.mail.yahoo.com.29_does_not_support_UIDL_or_XTND_or_XLST

This forum is littered with similar reports and the issue dates back several years! All I can tell you is that this is an error message originating from the POP server from which you're fetching emails, not a Thunderbird bug or issue.