搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Getting this message - The POP3 mailserver(inbound.att.net) does not support UIDL or XTND XLST

  • 9 个回答
  • 2 人有此问题
  • 1 次查看
  • 最后回复者为 ShotenStar

more options

I'm on Thunderbird 52.8.0 - stable environment, no known changes to Thunderbird or ATT server - last email received from inbound.att.net about 4PM 6/13/18. When Thunderbird is started I receive the following error message;

The POP3 mailserver (inbound.att.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 email, turn off these options in the Server settings for your server in the account Settings window.

"Leave messages on server" is checked, as is, "until I delete them". No changes have been made to the server settings since I began using Thunderbird. Never had any reason to do so.

I'm on Thunderbird 52.8.0 - stable environment, no known changes to Thunderbird or ATT server - last email received from inbound.att.net about 4PM 6/13/18. When Thunderbird is started I receive the following error message; The POP3 mailserver (inbound.att.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 email, turn off these options in the Server settings for your server in the account Settings window. "Leave messages on server" is checked, as is, "until I delete them". No changes have been made to the server settings since I began using Thunderbird. Never had any reason to do so.

被采纳的解决方案

Your provider made the changes. You need to ask them. All the error messages are from their server.

定位到答案原位置 👍 1

所有回复 (9)

more options

Your providers server is telling you they do not support Leave Messages on the Server. You state you have that option turned on. Turning it off as instructed would be a start.

more options

I have been in a stable environment with the mail client and the mail server, no configuration changes were made and I am reluctant to make changes in the middle of an unprovoked problem. This problem happened out of the blue and persisted for a day and a half. As of this morning, it went away just as quickly. I can only assume the server was updated/patched and the update/patch was removed, maybe due to user noise?? Anyway, thanks for the reply.

more options

Do as you wish. The message is from your providers server. Probably trying to force you to switch from Pop to IMAP.

more options

I'm getting the same error message (see attachment) and have unchecked "Fetch headers Only" but cannot find "Maximum Message Size" in the settings. As to "Leave on Server" I have it set to "Leave messages on Server for at most 30 days." Once I unchecked that box TB retrieved incoming emails. So my questions are as follows: 1. Why did this suddenly happen when I'd made no changes to TB? 2. How long will messages stay on the server when the box is unchecked?

thanks,

more options

选择的解决方案

Your provider made the changes. You need to ask them. All the error messages are from their server.

more options

Since Verizon gave it's email business to AOL I'm trying to deal with them. It seems they want $$ to answer even the simplest questions.

more options

Yea, Verizon/AOL sucks. AND when you try to login to the web mail to fix anything, you cannot login without allowing them to load content from advertising.com -- which tracks your browsing.

Also the new TOS says they will collect data FROM YOUR EMAIL TRAFFIC.

Time to move to Proton Mail.

more options

I just unchecked Leave Messages On Server and TB is trying to download 9800 messages.

This is unworkable. Had to Quit to make it stop.

how do I create a new folder? Need to move INBOX into a storage folder so when these 9800 are downloaded, I can delete them & put stuff back...

由VerizonSucks于修改

more options

Also experiencing this, starting last week (circa 18 Oct 18). Since I don't want to reset all the email accounts I use with TBird, I just restarted TBird. Every single time, the problem solved itself.

Don't know what sort of silliness verizon/AOL is suffering, but restarting TBird makes it go away for awhile. It started again today, and restarting TBird fixed it again.

  • star*