Open Bug 161286 Opened 23 years ago Updated 3 years ago

Show date/time of last mail fetch

Categories

(Thunderbird :: Mail Window Front End, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: bugzilla.mozilla.org, Unassigned)

Details

It would be nice to see the time of the last POP3/IMAP fetch operation.
Yeah, I agree on that. It is possible with PMMail200 and implemented there in the status line. It's a quick glance to see how much time has passed since the last fetch and how many messages got downloaded then. PMMail2000 does this with a format like this Last Fetch: hh:mm (X) new messages
Status: NEW → ASSIGNED
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Status: ASSIGNED → NEW
Assignee: mail → nobody
QA Contact: olgam → message-display
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Shifted to thunderbird.
Component: MailNews: Message Display → Mail Window Front End
Product: SeaMonkey → Thunderbird
QA Contact: message-display → front-end
Version: Trunk → unspecified
Recognizing the RFE
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.