Closed Bug 397026 Opened 17 years ago Closed 16 years ago

Organizer's E-Mail Account should be selectable

Categories

(Calendar :: E-mail based Scheduling (iTIP/iMIP), enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: andy, Assigned: dbo)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20061201 Firefox/2.0.0.6 (Ubuntu-feisty)
Build Identifier: 2007062504

When creating an event and sending an invitation via email, the organizer is just an email address.

It would be great if you could choose the email account that's used as organizer.

I created an event some days ago and the organizer was an email address the attendees shouln't know.

Reproducible: Always

Steps to Reproduce:
1. create event
2. add at least one attendee
3. check the "send email invitation" checkbox
4. save the event
Actual Results:  
the organizer is an email address, i don't know exactly which one
The Lightning Enhancer Plugin adds a Organizer field to the event dialog.
<http://www.inverse.ca/english/contributions/lightning_enhancer_plugin.html>

Maybe this already fits your needs.
I think this is something we need to be able to correctly implement Email based scheduling.

Note also, that it should be possible for certain calendar providers to make the organizer read-only. i.e gdata needs the organizer to be the actual user of the calendar. If you are not the organizer of the event, or the organizer of the event doesn't fit to the calendar it lives in (gdata case), then the field should also be read-only.
Status: UNCONFIRMED → NEW
Component: Lightning Only → E-mail based Scheduling (iTIP/iMIP)
Ever confirmed: true
OS: Linux → All
QA Contact: lightning → email-scheduling
Hardware: PC → All
Bug 431522 adds a configuration option to select the email identity used for
sending. That one is used as the ORGANIZER.
Depends on: 431522
Assignee: nobody → daniel.boelzle
fixed with bug 431522
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.9
Checked in build 2008071619 -> VERIFIED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.