Invitation replies are sent with the default SMTP instead of the one associated with the receiving email address

[Simon Déziel]

My Thunderbird has 2 accounts setup: a personal one (default) and another for work.

When I reply to meeting invitation sent to my work email, the SMTP account used to send the reply is my default one.

$ lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

$ apt-cache policy xul-ext-lightning
xul-ext-lightning:
  Installed: 1.0~b2+build2+nobinonly-0ubuntu2
  Candidate: 1.0~b2+build2+nobinonly-0ubuntu2
  Version table:
 *** 1.0~b2+build2+nobinonly-0ubuntu2 0
        500 http://ca.archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xul-ext-lightning 1.0~b2+build2+nobinonly-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic x86_64
Architecture: amd64
Date: Mon May 2 14:19:37 2011
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: lightning-extension
UpgradeStatus: No upgrade log present (probably fresh install)

[Tom Louwrier (tom-louwrier)]

Having the same issue. I think it's related to the bug I filed at 966002.
This is creating quite a mess since my calendars are on a Sogo server and the incorrect <email address hidden> causes all invitations and replies to fall in the catch-all (<email address hidden>) which means a whole group of users get all invites and replies as mails in that particular mailbox.

cheers
Tom

[Tom Louwrier (tom-louwrier)]

update:
I just found out that when I tick the 'Support Outlook and Outlook 2000/XP' box when accepting an invitation, the confirmation includes just me. The appointment, when opened in the Sogo-server based calendar shows '<email address hidden>' (organiser) and '<email address hidden>' (participant). This is correct.
The incorrect '<email address hidden>' attendee is no longer introduced and thus will not get any messages when the appointment is modified or deleted.

Mind you: neither party is using Outlook nor Exchange. This is a Tbird/Lightning/Sogo setup. It does narrow down the source of the issue to the generic and/or CalDAV part of the protocol I think.

For now this is a workaround.

cheers
Tom