From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: MS Live calendar integration with gnus
Date: Tue, 15 Sep 2015 17:30:41 +0200 [thread overview]
Message-ID: <87mvwnog2m.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87y4g7btup.fsf@ucl.ac.uk>
Eric writes:
> Hi,
>
> for a while now, I've been able to process calendar events generated by
> MS Live (Exchange) and, even better, integrate these with my org
> setup. The processing included being able to accept/decline
> events. However, recently, the option to accept or decline events has
> disappeared from what is presented in gnus.
I think I had that problem when receiving event information for someone
that Gnus et al didn't think was me.
I.e. when a meeting was adressed to a group that I am a member of.
Ah, here it is:
,----[ C-h v gnus-icalendar-additional-identities RET ]
| gnus-icalendar-additional-identities is a variable defined in `gnus-icalendar.el'.
| Its value is
| ("...", "blah", ...)
|
| Original value was nil
|
| Documentation:
| We need to know your identity to make replies to calendar requests work.
|
| Gnus will only offer you the Accept/Tentative/Decline buttons for
| calendar events if any of your identities matches at least one
| RSVP participant.
|
| Your identity is guessed automatically from the variables
| `user-full-name', `user-mail-address',
| `gnus-ignored-from-addresses' and `message-alternative-emails'.
|
| If you need even more aliases you can define them here. It really
| only makes sense to define names or email addresses.
`----
Does adjusting that help?
Best regards,
Adam
--
"You have to photosynthesize" Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2015-09-15 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 15:11 Eric S Fraga
2015-09-15 15:30 ` Adam Sjøgren [this message]
2015-09-15 16:00 ` Eric S Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvwnog2m.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).