Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

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

Thread ini telah diarkib. Sila tanya soalan baru jika anda perlu bantuan.

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

  • 1 balasan
  • 2 ada masalah ini
  • 1 paparan
  • Balasan terakhir oleh Stans

patti.aha
patti.aha
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?

All Replies (1)

Stans
Stans
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.