Closed
Bug 435155
Opened 16 years ago
Closed 16 years ago
Cannot accept Meeting request sent to an ID not in my accounts list such as a forwarded address
Categories
(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 420516
People
(Reporter: subs.vk, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.14) Gecko/20080418 Ubuntu/7.10 (gutsy) Firefox/2.0.0.14 Build Identifier: 0.8 In Mozilla Thunderbird 2.0.0.14 and Lightening 0.8, I cannot accept a meeting request if the request is sent to a ID which is not my primary ID. For example, if my mail ID configured in Thunderbird is firstname.lastname@example.com and the request is sent to firstname@example.com (which is being forwarded to firstname.lastname@example.com), I would not be able to accept that invitation. However, I am able to drag the request to the calendar which works fine, but then it does not have any option to send the confirmation back to the sender. The problem is that in my office there are a number of Exchange Distribution Lists configured, and if a meeting request is sent to a distribution list, I am unable to accept it. I was able to accept it in Evolution though. Reproducible: Always Steps to Reproduce: 1. Setup a forwarder in your mail server wherein all mail sent to xyz@yourdomain.com are forwarded to an account configured in Thunderbird. 2. Send an event invitation to the forwarded address (xyz@yourdomain.com) 3. Check that mail in Thunderbird and try to accept/deny it. Actual Results: Once the above steps are performed, nothing happens after clicking the button. All just stays there. Expected Results: The meeting request should have been accepted and a confirmation mail shall be sent to the sender.
Reporter | ||
Updated•16 years ago
|
OS: Linux → All
Version: unspecified → Lightning 0.8
Comment 1•16 years ago
|
||
Same as Bug 420516 or Bug 428392? If possible please retest with a recent Lightning 0.9pre nightly test build.
Comment 2•16 years ago
|
||
(In reply to comment #1) Yes, sounds like dupe to bug 420516.
Comment 3•16 years ago
|
||
Resolving as duplicate of bug 420516 per comment#1 and comment#2.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•