Closed Bug 278106 Opened 20 years ago Closed 20 years ago

Desktop context menu selection "Sendto" generates Outlook error

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: drgoon, Assigned: mscott)

Details

Right clicking a file in either Windows Explorer or from the start menu and selecting "Sendto -> Desktop(create shortcut)" generates an MS error from Outlook. See Article ID:813745 on MSDN. The error message is "Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Outlook and set it as the default mail client." Appears to be a MAPI error. System Specs: Win XP Pro - sp2 Thunderbird v.1.0 (set as default client) MS Office XP Pro (includes Outlook)
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.