Closed Bug 577074 Opened 16 years ago Closed 14 years ago

Notify is using the wrong email address

Categories

(Calendar :: Lightning Only, defect)

Lightning 1.0b2
x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: ionut.radu, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.4) Gecko/20100622 Fedora/3.6.4-1.fc13 Firefox/3.6.4 Build Identifier: Lightning 1.0b2 I have two email addresses set in thunderbird and I would like for the lightning notification to be sent using one of them. However it is using the other one and there is no way to select this. Reproducible: Always
Have you selected the correct email account during calendar creation? If not: you can change it anytime using the calendars property dialog. To open the properties dialog select the calendar in the left pane and double click it. Or choose menu Edit > Calendar Properties.
I haven't been asked for an email address during calendar creation. I have looked in Edit > Lightning but have found no way to change the email address.
See Comment 1 for description on how to open the properties dialog. Please note that you can't specify an email address directly. Instead you can select one of your Thunderbird email accounts. Lightning will use the address and server that is specified for the account.
I have just one account set up, and it's showing my email when selecting attendees upon event creation. But the actual ICS file attached to the invitation email contains only my surname. So the automatic sending the confirmation email from the receiver after accepting my invitation fails. The calendar is configured with my valid email address.
This is the faulty line btw: ORGANIZER;RSVP=TRUE;PARTSTAT=ACCEPTED;ROLE=CHAIR:Surname I've only replaced my surname. There should be an email address, right?
Ignore me. Wrong ticket. Found a better one.
Ionut Radu, is this still an issue using the recently released Lightning 1.0 (compatible with Thunderbird 8)?
Version: unspecified → Lightning 1.0b2
I stopped using this because of the wrong behavior. Anyway it passed more than one year from my bug report, so who cares anymore?
Marking as INCOMPLETE, because the bug report can't be reproduced and the bug reporter cannot give ffedback on this anymore.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.