为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

Thunderbird occasionally “Automatically downloads all (not just new) messages from the POP server.

  • 4 个回答
  • 2 人有此问题
  • 8 次查看
  • 最后回复者为 _ms_

more options

Thunderbird occasionally “Automatically downloads all (not just new) messages from the POP server. The number of download messages are based on the client server settings “leave messages on server” and “for at most <number> days”.

This has happened several times (maybe eight, with four different accounts and two different POP servers) within about a month. Nothing “I have” changed around that time; maybe some automatic updates or server-side changes I haven’t kept track of.

To clean up the Inbox To remove the hundreds of re-downloaded old messages as new: 1. Upon discovery “sort by read” and select and move to new folder. 2. Then “sort by date” looking for matching date & times and then matching subject. 3. When found identify by comparing that time with the time found by selecting View > Message Source (or Ctrl+U), the first line contains either the original same date or a different recent redownload date. 4. Move original message back to Inbox. Once complete delete all remaining redownload messages which all should have the same first line date & time when viewing Message Source info.

Doing this every few weeks is becoming a pain this last month or so.

Leaving messages on the server for a few months is required for recovery if required. Have been operating this way with TB since 1999; excite@home days.

Thunderbird occasionally “Automatically downloads all (not just new) messages from the POP server. The number of download messages are based on the client server settings “leave messages on server” and “for at most <number> days”. This has happened several times (maybe eight, with four different accounts and two different POP servers) within about a month. Nothing “I have” changed around that time; maybe some automatic updates or server-side changes I haven’t kept track of. To clean up the Inbox To remove the hundreds of re-downloaded old messages as new: 1. Upon discovery “sort by read” and select and move to new folder. 2. Then “sort by date” looking for matching date & times and then matching subject. 3. When found identify by comparing that time with the time found by selecting View > Message Source (or Ctrl+U), the first line contains either the original same date or a different recent redownload date. 4. Move original message back to Inbox. Once complete delete all remaining redownload messages which all should have the same first line date & time when viewing Message Source info. Doing this every few weeks is becoming a pain this last month or so. Leaving messages on the server for a few months is required for recovery if required. Have been operating this way with TB since 1999; excite@home days.

被采纳的解决方案

Who are your email providers?

I ask because of this thread: https://support.mozilla.org/en-US/questions/1212501#answer-1097676

定位到答案原位置 👍 2

所有回复 (4)

more options

UPDATE: Just happen again, around "Sat Apr 7 07:07:12 2018" eastern US.

more options

选择的解决方案

Who are your email providers?

I ask because of this thread: https://support.mozilla.org/en-US/questions/1212501#answer-1097676

more options

Zenos said

Who are your email providers? I ask because of this thread: https://support.mozilla.org/en-US/questions/1212501#answer-1097676

Email provider is AOL also, after a Verizon moved me there a few months ago.

Thanks Zenos for making this connection, this is what I was looking for if others were having the same issue. When I asked my wife about her account (she setup the same way) she didn’t notice. Since then she realizes it was happening to her too.

I’ll investigate the suggested option and see which, if not all, will work for me.

Again, Thanks Zenso and Thanks Matt

more options

I'm slightly skeptical about the idea that this is just an aol problem, although all but one of reoccurrences for me happened with my pop.verizon.net account hosted by aol. But the one other occurrence happened on my other account, which uses an imap server: imap.csail.mit.edu