You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Gautier DI FOLCO (Jira)" <se...@james.apache.org> on 2020/06/12 09:47:00 UTC

[jira] [Updated] (JAMES-3213) Enrich contact auto completion mailet pipeline with replyTo field

     [ https://issues.apache.org/jira/browse/JAMES-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gautier DI FOLCO updated JAMES-3213:
------------------------------------
    Description: 
When an attendee changes his participant status, there is a notification email is sent to the event organizer from the attendee.

Then a third party sends an ITIP request to the CardAV server to handle realtime update.

If the sender email does not exist in the list attendee, the CardAV ITIP broker will add him to the attendee list.

This is not correct in cases:
 * When an external attendee accept the event, the notification email should send from the third party system ([no-reply@example.org|mailto:no-reply@open-paas.org])
 * When the attendee forwards the invitation email to an external user, then the external user (is not included in attendee list) accepts.

Both cases above should not lead to the behavior that adding the sender to the attendee list.

  was:
When an attendee changes his participant status, there is a notification email is sent to the event organizer from the attendee.

Then a third party sends an ITIP request to the CardAV server to handle realtime update.

If the sender email does not exist in the list attendee, Sabre ITIP broker will add him to the attendee list.

This is not correct in cases:
 * When an external attendee accept the event, the notification email should send from the third party system ([no-reply@example.org|mailto:no-reply@open-paas.org])
 * When the attendee forwards the invitation email to an external user, then the external user (is not included in attendee list) accepts.

Both cases above should not lead to the behavior that adding the sender to the attendee list.

        Summary: Enrich contact auto completion mailet pipeline with replyTo field  (was: Prevent non-participant add in CardAV)

> Enrich contact auto completion mailet pipeline with replyTo field
> -----------------------------------------------------------------
>
>                 Key: JAMES-3213
>                 URL: https://issues.apache.org/jira/browse/JAMES-3213
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: Gautier DI FOLCO
>            Priority: Minor
>
> When an attendee changes his participant status, there is a notification email is sent to the event organizer from the attendee.
> Then a third party sends an ITIP request to the CardAV server to handle realtime update.
> If the sender email does not exist in the list attendee, the CardAV ITIP broker will add him to the attendee list.
> This is not correct in cases:
>  * When an external attendee accept the event, the notification email should send from the third party system ([no-reply@example.org|mailto:no-reply@open-paas.org])
>  * When the attendee forwards the invitation email to an external user, then the external user (is not included in attendee list) accepts.
> Both cases above should not lead to the behavior that adding the sender to the attendee list.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org