• 7
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      We use our Confluence wiki for internal communication and to work with our customers in specific projects.

      After the last upgrade to Confluence 5.1.4 we received several emails from our customers that the get a warning/error from our mail server after they shared a page or used an @mention.

      This is true cause our Mailserver does not allow relaying for other mail domains!

      http://en.wikipedia.org/wiki/Open_mail_relay

      So we actually have 2 options:

      1) deactivate @mentions completly
      2) to live on with this mailserver warning/errors.

      But number 2 isn't quite an option.

      It would be best if we could limit this feature to a specific group of people.

      Kind Regards
      René

      P.S. The same goes for "share pages"

            [CONFCLOUD-29961] Limit @mentions and share feature to specific groups

            Lit Felix added a comment -

            really @Atlassian you are neglecting this for 10 years now?

            Lit Felix added a comment - really @Atlassian you are neglecting this for 10 years now?

            Just to note that the share-with issues discussed above apply to the attachment preview functionality well as share-page in v. 5.7+ snd disabling share-page functionality does not also disable share-attachment functionality.
            Share functionality should be configurable, and that configuration should be in one place.

            Carter Snowden added a comment - Just to note that the share-with issues discussed above apply to the attachment preview functionality well as share-page in v. 5.7+ snd disabling share-page functionality does not also disable share-attachment functionality. Share functionality should be configurable, and that configuration should be in one place.

            We read groups from our central user directory (Microsoft Actice Directory) and use them for restrictions. But when you use a group for sharing content, confluence should use the e-mail address of the group instead of informing all group members. Especially avoid performance problems, when you have groups with many users.

            Otherwise an administrator must have the possebility to configure what you can select (user, group, e-mail) or who can select groups, when you want to share content.

            Enrico Skottnik added a comment - We read groups from our central user directory (Microsoft Actice Directory) and use them for restrictions. But when you use a group for sharing content, confluence should use the e-mail address of the group instead of informing all group members. Especially avoid performance problems, when you have groups with many users. Otherwise an administrator must have the possebility to configure what you can select (user, group, e-mail) or who can select groups, when you want to share content.

            HEllo dears,

            any update on this issue?

            We need also limitation on autocomplete - Users list in permission editor.

            • Profiles are shown to every user.
            • and the @mention list which is still depends on autocomplete which returns all the users.

            Regards

            Ibrahim Farhan added a comment - HEllo dears, any update on this issue? We need also limitation on autocomplete - Users list in permission editor. Profiles are shown to every user. and the @mention list which is still depends on autocomplete which returns all the users. Regards

            Santosh Kumar Panigrahi added a comment - - edited

            Hi,

            The dangerous aspect is that all the users are able to view the profiles.

            In a scenario where there are business rivals working with a particular client for the same project, would never what to give any bit of their information for e.g. profile information.

            Regards,
            Santosh

            Santosh Kumar Panigrahi added a comment - - edited Hi, The dangerous aspect is that all the users are able to view the profiles. In a scenario where there are business rivals working with a particular client for the same project, would never what to give any bit of their information for e.g. profile information. Regards, Santosh

            Any update on this?
            We desperately need mention limitations as well. Now we have to disable the whole plugin simply because we don't want our customers to see each others details in different spaces. If it would work same way in confluence as it does in Jira it would be great.

            Regards,
            Timo

            Timo Kupsa added a comment - Any update on this? We desperately need mention limitations as well. Now we have to disable the whole plugin simply because we don't want our customers to see each others details in different spaces. If it would work same way in confluence as it does in Jira it would be great. Regards, Timo

            Stefan added a comment -

            Hi,

            is there any update on this issue?
            This issue is also applicable for the "Share Botton". It is not possible for our mail server to send the notification for a different domain.

            Thanks for your status update.

            Regards
            Stefan

            Stefan added a comment - Hi, is there any update on this issue? This issue is also applicable for the "Share Botton". It is not possible for our mail server to send the notification for a different domain. Thanks for your status update. Regards Stefan

              Unassigned Unassigned
              54200e1bc777 Joachim Sengenberger
              Votes:
              26 Vote for this issue
              Watchers:
              28 Start watching this issue

                Created:
                Updated: