Unwanted reply/forward of events in calendar

Hey mejriou,

We'd recommend reviewing this article for more information on Calendar accounts on iPhone: Set up multiple calendars on iPhone - Apple Support

If you have other accounts set up in Calendar, we'd suggest testing to see if they have the same issue as that would help isolate the issue further. If the problem is limited to your Exchange account, we'd recommend reaching out to your Exchange account administrator or Microsoft support for additional information and assistance.

If the issue continues, or isn't specific to your Exchange account, we'd recommend contacting Apple Support for further assistance here: Get Support

Thanks!

Hi mejriou,

Thanks for following up. Testing another account would be the best way to narrow this down. If you're unable to do so, we recommend contacting us directly to look into next steps: Get Support

Cheers.

I have two major problems:

(1) Those who have agreed to participate in the itinerary will be continuously replied to the meeting initiator every day.

The initiator will receive >5~10 identical letters every day.

(2) Originally a participant role

The iPhone automatically copies the content of the original initiator and sends it to all participants in its own name.

(This is the most troublesome thing)

I had a similar issue multiple times,

always it's under an Exchange account, where an event invite for a distribution group arrives.

At least in one occasion I accepted from the notification center of my iphone (ios 17.0.3) by long-tapping and accepting.

I have a additional Google accounts on the phone, though rarely if ever I do I receive invites for multiple attendees with those.

As described in the original post, an event with the same subject and attendees, but for a different timeslot is sent in my name.

Not sure if related, I also observed various random 'new events' with contacts from said exchange account created. No idea how.

from Microsoft Exchange log : Repeated replies

I would like to ask if this problem has been solved, because the same thing happened to our company manager.

We also upgraded to iOS 17.0.3, but the problem was not solved.