nextcloud / nextcloud/server

Calendar Spam addressees turn up in "Recently contacted"

Open
#38,390 10 comments 0 reactions 1 assignee View on GitHub

@ChristophWurst is already working on this.

Since May 31, 2023.

25-feedback 3. to review bug feature: carddav feature: contacts feature: dav
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

Describe the bug

If you are an addressee of calendar spam and import a calendar with such spam into Nextcloud, the other adressees turn up in the contacts app under "Recently contacted" although they have not been recently contacted.

Steps to reproduce
  1. Have an iCloud account with calendar data containing old calendar spam.
Bildschirmfoto 2023-04-30 um 16 33 24
  1. Export this calendar data to .ics files via macOS calendar.

  2. Connect macOS calendar to Nextcloud as described here.

  3. Import the .ics files into the Nextcloud calendar via macOS calendar.

  4. Open the contacts app.

Expected behavior

The addressees of the calendar spam do not appear under "Recently contacted" because they have not been recently contacted.

Actual behavior

The addressees of the calendar spam do appear under "Recently contacted".

Bildschirmfoto 2023-04-29 um 21 03 44
Contact version

6.2.0

Operating system

Raspberry Pi OS Lite (64-bit, Debian Bullseye)

PHP engine version

PHP 7.4

Web server

Other

Database

PostgreSQL

Additional info

I thought my account had been breached and spent an evening on figuring out how someone could have contacted these people through my Nextcloud account. Only once I dumped my database to find where the addresses have been persisted could I draw the connection to the calendar data.

If someone gets here via Google because mysterious email addresses allegedly have been recently contacted by you, check your calendar data for calendar spam.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.