Closed
Bug 523807
Opened 15 years ago
Closed 15 years ago
FYI: Mac users explaining why they prefer Mail to Thunderbird.
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: u360812, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Build Identifier:
If Mozilla can fix these Thunderbird problems, then there would be more Mac users:
http://forums.macrumors.com/showthread.php?t=424750
Reproducible: Always
Solving these problems would also encourage Mac Mail users to migrate to Thunderbird:
http://www.twistermc.com/blog/2005/07/20/import-apple-mail-to-thunderbird/
The fact that after importing from Mail to Thunderbird, all e-mails are unread has GOT to be resolved.
I've got tens of thousands of e-mails, in hundreds of mailboxes.
There's no way I'd make the migration if every e-mail in Thunderbird was marked as unread.
Also, if possible, please keep Mail's red flags during the transfer.
More Mac feedback about Thunderbird:
http://forums.mactalk.com.au/11/66484-mac-mail-thunderbird.html
Comment 4•15 years ago
|
||
This bug is way too vague and amorphous to be a usable bug for fixing, especially as there really was no concrete rationale given against Thunderbird in the first link. It also violates the "one issue per bug" rule too much.
If you have *specific* *bugs*, such as import marking email as unread, you can file those individually; if you have support requests, the proper place for that is <http://getsatisfaction.com/mozilla_messaging/products/mozilla_thunderbird>.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Comment 5•15 years ago
|
||
Bryan a bunch of links for you to read.
Apologies for violating the "one issue per bug rule," Ludovic.
Just trying to be helpful to the code building team.
While I'm here, here's another link for Bryan :o).
http://www.cultofmac.com/new-mac-os-x-mail-app-correo-blends-thunderbird-and-camino/1686
Best,
Michael
You need to log in
before you can comment on or make changes to this bug.
Description
•