Cannot email invitations to secondary (resource) google calendars

RESOLVED INVALID

Status

Calendar
E-mail based Scheduling (iTIP/iMIP)
RESOLVED INVALID
10 years ago
8 years ago

People

(Reporter: Murray Styman, Unassigned)

Tracking

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Build Identifier: Thunderbird/2.0.0.18

I am trying to use a Secondary Google Calendar as a resource.  I can
see the current events when I Invite Attendees (using the published
ClanedarID under Google Calendar settings as the email address).
However, when I email the invite to attendees the email fails to get
to the secondary calendar.

Invites are sucessfully sent to the Primary Calendar if i use that as
a 'Resource'.

Failing email:

This is an automatically generated Delivery Status Notification

THIS IS A WARNING MESSAGE ONLY.

YOU DO NOT NEED TO RESEND YOUR MESSAGE.

Delivery to the following recipient has been delayed:

    XXXXXXXXXXXXXXXXXXXXXXXXXX@group.calendar.google.com

Message will be retried for 1 more day(s)

Technical details of temporary failure:
DNS Error: Domain name not found

  ----- Message header follows -----

Received: by 10.210.125.13 with SMTP id x13mr3683656ebc.
198.1227541327733;
       Mon, 24 Nov 2008 07:42:07 -0800 (PST)
Return-Path: <XXXXXXXXXX@googlemail.com>
Received: from ?192.168.10.2? (host81-149-67-1.in-addr.btopenworld.com
[81.149.67.1])
       by mx.google.com with ESMTPS id g9sm7852660gvc.
0.2008.11.24.07.42.05
       (version=TLSv1/SSLv3 cipher=RC4-MD5);
       Mon, 24 Nov 2008 07:42:06 -0800 (PST)
MIME-version: 1.0
Return-path: murray@XXXXXXXXXXX
To: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@group.calendar.google.com
Subject: Event Invitation: New Event 12
Content-type: multipart/mixed; boundary="Boundary_(ID_qyG4ZdjoAsiZ
+Jo19dCbWQ)"
From: XXXXXXXXX@googlemail.com
Date: Mon, 24 Nov 2008 07:42:06 -0800 (PST)
Message-ID: <492acb4e.096c100a.783e.ffffd6c3@mx.google.com>

End of Failing email.

NSLOOKUP fails to resolve group.calendar.google.com
(calendar.google.com resolves OK)

I have hidden some info with Xes.

Current Config:
     Thunderbird 2.0.0.18 (20081105)
     Lightning 0.9
     Provider for Google Calendar 0.5.1
     Using the Private XML link to access the calendars and supplying
username and pasword when asked.

If I add the Secondary Calendar directly to Lightning I can post OK to
the Public and Private XML links.  But this is not the way a resource
calendar is supposed to be used - or is it?

I could just use the Primary calendar but I will not be able to get
the invites auto accepted. 

Reproducible: Always

Steps to Reproduce:
1.Add the Google Calender as a contact using the published CalendarID (e.g. Jubilee Hall: 89d13mn52cat60sm7tksuijcpk@group.calendar.google.com )
2.Create New event and invite 'Jubilee Hall' (Calendar availability is listed as expected)
3.Ensure 'Send attendees invitations via email' is ticked.
4.Click 'Close and Save'

Actual Results:  
Event is not listed in the secondary google calendar and eventually an email failure message is received as detailed


Expected Results:  
An automatically accepted event in the secondary (resource) google calendar

Workaround: using a primary calendar works but the event is not auto accepted.
However, this does mean that a separate google mail account is required for each resource one is trying to publish!

I did not know whether to log this as a Thunderbird, Lighting, of Provider for Google Calendar problem.  I descided on Thunder bird as it is email related (I think).

I have left the severity as Normal rather that Minor as I don't think that the workaround is easy.
Component: General → General
Product: Thunderbird → Calendar
QA Contact: general → general

Updated

10 years ago
Component: General → E-mail based Scheduling (iTIP/iMIP)
QA Contact: general → email-scheduling
The email you get is probably rather a temporary problem with DNS and not related to the client software at all, rather the network topology.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.