309121 - Add account name for error messages

Status: RESOLVED FIXED

(Thunderbird :: Mail Window Front End, enhancement)

Description

[Marc DVer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

I have a number of pop3 accounts with different servers.  When I hit the Get
Mail button it of course attempts to get all the mail for all the accounts, as
it is supposed to.  However, one or two of them will occasionally produce an
error relating to the pop3 server itself.  However, the message returned does
not say which account is being affected.  If a person has a large enough number
of accounts then trying each one can be burdonsome, and may in fact return bad
results if the issue is related to the computer or internet connection and not
the mail server itself, e.g. timeout errors when trying to fetch mail from
multiple servers at the same time.

Reproducible: Always

Comment 1

[zug_treno]

Related to Suite bug 139788 -> Suite bug 66860?

Comment 2

[OstGote!]

*** Bug 318188 has been marked as a duplicate of this bug. ***

Comment 3

[Magnus Melin [:mkmelin]]

*** Bug 333247 has been marked as a duplicate of this bug. ***

Comment 4

[Magnus Melin [:mkmelin]]

*** Bug 350838 has been marked as a duplicate of this bug. ***

Comment 5

[Magnus Melin [:mkmelin]]

*** Bug 354136 has been marked as a duplicate of this bug. ***

Comment 8

[:aceman]

This is necessary when there are multiple account on the same server. Then the 'Connection to server a.b.c timed out' message is not enough.

Comment 9

[David :Bienvenu]

I'm going to mark this fixed - we should open more specific bugs for other messages that need the account name.

Comment 10

[Thomas D. (:thomas8)]

(In reply to David :Bienvenu from comment #9)
> I'm going to mark this fixed - we should open more specific bugs for other
> messages that need the account name.

Is there some specific bug that fixed this?
Did that bug also fix all the duplicates of this bug?
Something is unresolved here...