importing .ical file sends extraneous email to other attendees

[dauith]

When I run gcalcli import --calendar "Tech - Networking" --default-reminders ~/Downloads/invite.ics the event is added to my calendar, but Google Calendar tries to send email to all the other original recipients of the invite.

I'm not sure how much of this is relevant:

• the source invite.ics arrived as an email attachment, so this is a case of importing an event into a different calendar (and why there are other invitees, and why they wouldn't want email about my copy of the event)
• it seems the GCal API has events.import and events.insert, and maybe the former method is what is needed for my attempted use (googleapiclient/discovery_cache/documents/calendar.v3.json mentions "For calendar migration tasks, consider using the Events.import method instead"), but gcalcli/cli.py calls the latter method. (It's mostly just ironic that the gcalcli subcommand which calls insert() is itself named "import", although that did cause me some confusion at first :)
• this is gcalcli 4.5.1
• it looks like this issue has been raised before
  • add attendees when importing a ICS file #27 -- quite old, and only the comments at the end apply
  • Importing calendar event to different calendar re-emails all invitees #587 -- relevant and recent; ended with a suggestion to open an enhancement request, but I can't find such a request

Entirely possible I'm misunderstanding the whole situation; either way, is this a known issue, that might get addressed?

Thanks

[Ticonderoga]

Same problem for me. I stopped using import because of this annoying feature. I would really like a 'dry' import.

Thanks

[hlein]

Just discovered gcalcli and it should do exactly what I need, which is fantastic... except for this problem, still happens to me with either the current import or with import --use-legacy-import.

It looked to me like it created a new event, with me as the owner, and sent out invites to everyone on the list, confusing both me and them.

Reproduced both with an event created & sent to me by an Exchange user, and also with a Google Calendar event I created myself and invited a non-Google-connected address of mine and imported into a different Google Calendar account.

[hlein]

I think I may have found the issue - it looks like the use_legacy_import test in _event_should_use_new_import_api is backwards, causing us to always(?) use the old legacy import, instead of the fixed method; see my comment on the commit above.

[dbarnett]

Hah yeah you're right. use_legacy_import=False makes _event_should_use_new_import_api immediately return False. Good news is it should be easy to fix. Bad news is it'll be disruptive to flip that logic (and still won't work perfectly as expected I'm pretty sure)...

Anyway I'll look into flipping that to work correctly.

[Ticonderoga]

So what is the fix ?
If I don't want to send email ... I have to specify --use-legacy-import or not ?

[hlein]

So what is the fix ? If I don't want to send email ... I have to specify --use-legacy-import or not ?

If you have 405639c applied, then the new method should work and should not trigger emails. The problem was the logic was previously forcing all imports to use the legacy method.

For me I then run into what I'm pretty sure is a different problem, maybe a pebkac one, where I get permissions errors trying to import into my primary calendar (for the email address that was invited). It might be a problem with how I set up the API access, or how my workspace org is configured; I haven't investigated further yet (and if it's not pebkac it's a different issue than this one, I think).

[Ticonderoga]

Thanks a lot

[Ticonderoga]

I just tried and the method import still send emails ... is it possible to have a dry import command ?