This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

Why does TB ignore the email set up in calendar properties when sending out event invitations?

  • 6 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 18 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย cliffmitchell

more options

When creating an event and sending event invitations the email address set in calendar properties is ignored. Also the 'Notify attendees' and 'Separate invitation per attendee' boxes are greyed out. The calendar is synced with an ownCloud server (using the Sogo connector) and TB seems to be picking up the server email address from ownCloud. This means recipients get an email from an address they don't recognise. Surely TB should use the email address set in calendar properties when sending invitations - that's what it's there for! Any help in resolving this would be appreciated. Thanks.

When creating an event and sending event invitations the email address set in calendar properties is ignored. Also the 'Notify attendees' and 'Separate invitation per attendee' boxes are greyed out. The calendar is synced with an ownCloud server (using the Sogo connector) and TB seems to be picking up the server email address from ownCloud. This means recipients get an email from an address they don't recognise. Surely TB should use the email address set in calendar properties when sending invitations - that's what it's there for! Any help in resolving this would be appreciated. Thanks.

การตอบกลับทั้งหมด (6)

more options

Didn't you already ask this? You found out that the wrong e-mail address was in your ownCloud account, so the sync to Thunderbird over-rid what Thunderbird thought that the e-mail address should be.

more options

Bruce A. Johnson said

Didn't you already ask this? You found out that the wrong e-mail address was in your ownCloud account, so the sync to Thunderbird over-rid what Thunderbird thought that the e-mail address should be.

I have tried to refine my question because there is still something strange going on and it looks increasingly like a bug. On ownCloud each user has their own set of calendars and their own email address. In addition, the ownCloud server has an email address for sending out password resets and other notifications that is not associated with any user or calendar. The email address that TB is using for calendar invitations is the server level email address for ownCloud, not the email address of the calendar owner on ownCloud, and not the email address set in the calendar settings in ownCloud. Indeed in my case the email address that is being used is not even set up in TB. This makes no sense and recipients of calendar invitations get emails from a completely unknown address. Surely this is not what TB intends?

more options

I understand now, and I cannot help (obviously).

My guess is that Mozilla will blame ownCloud, and ownCloud will blame Mozilla. Hopefully you are attacking this issue from both ends. You will probably get better support from ownCloud, since you pay for their product and they have paid support people. It seems to me that ownCloud should be able to change the e-mail address they push out with your calendar, especially since the e-mail address they are pushing out is wrong.

more options

At a guess I think we perhaps should point to the sogo connector.

Have you tried using the calendar as caldav? there is an endpoint that can be used, but you basically have to have an apple product with the calendar configured to locate it. As I understand things anyway.

This page indicates the endpoint is http://example.com/remote.php/caldav

more options

Thanks to everyone who contributed to this thread.

For anyone else having this problem it looks like a bug in ownCloud is the underlying cause, and the bug should be fixed in the next release:

https://github.com/owncloud/core/issues/25470

Cliff