Closed Bug 370090 Opened 17 years ago Closed 16 years ago

Outlook parity (tracking bug)

Categories

(Thunderbird :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: shattered, Unassigned)

References

(Depends on 5 open bugs)

Details

(Keywords: meta)

User-Agent:       Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.8.0.8) Gecko/20061122 SeaMonkey/1.0.6
Build Identifier: 

Tracking issues that may block migration from Outlook to Thunderbird

Reproducible: Always
Depends on: 203570
No longer depends on: 203750
Depends on: 243184
I'm not sure what the purpose of this bug would be, but if you insist on keeping it, please only add bugs that really have anything with outlook feature parity to the list. Obscure bugs, or minor differences in behavior are hardly it.

You do realize your dependency changes spam a whole lot of innocent people? Dependency changes might be interesting sometimes...

From looking quickly over this list, it's little more than a list of your pet bugs, IMO.
Keywords: meta
Perhaps I shouldn't have used the word 'block' -- the idea was to identify problems that may sufficiently annoy users that are accustomed to Outlook+Exchange.

Let me explain the rationale for including some of these bugs.

bug 59704: A non-issue if there's only one Exchange server, or if there's a frontend server and multiple mailbox servers.  Considering that Outlook (in MAPI mode) handles referrals transparently, there may not be a frontend server at all.
bug 204350: Outlook can easily forward, save, reply to an attachment.
bug 290451, bug 312265, bug 330743: Users should be free to name their folders in any way they please.
bug 232104, bug 292120, bug 313694, bug 344304: So, do I have new mail or not?
Depends on: 324012
No longer depends on: 336400
Assignee: mscott → nobody
Is this meta bug still maintained?
Doesn't really matter here I think, so let's close and not add more deps. WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.