Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-12800

Allow emails sent to mail archive address to be flagged as to be stored in archive, but not forwarded on to other site members


    • Type: Feature Request
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.0, 2.4.1, 2.5.0
    • Fix Version/s: 2.8.0
    • Component/s: Email Archive
    • Labels:


      A Faculty member at the University of Cambridge has made the following suggestion:

      "is there a way of setting things up so that >the Email Archive tool does not automatically forward received emails to any >members, but they can inspect and copy mails/save attachments by visiting >the WorkSite and looking at the Archive? "Ideally, there would still be a way for me to email all members through an >alias to let them know of new uploads. This rather implies having two Email >Archive Tools with slightly different behaviours

      This is because I have a collection of about 50 emails received from a central site, most with attachments, a selection of which need to be distributed to the various users in the University. This happens a couple of times a year. It would not be helpful to the users if I were just to email all 50 messages to them, as around 30-40 of them would not be much use. A self-service presentation would be better. So what I would like is to be able to assemble the messages in the email archive without them being relayed to each individual user. Are any of the following possible?

      • that there is a flag somewhere that suppresses mail forwarding but still allows incoming messages to be accumulated in the mail archive?
      • or can there be two or more email tools with different setups and presumably with different aliases
      • that there could be two different aliases for the mail archive, one relaying, the other not ?

      Note that a regular upload, even of several files at a time, would not really simplify things. The manual labour of saving 50 emails, and attachments, in consistent form, with different names etc etc is too awful to contemplate. In previous years when there were about 20, I would manually publish all these on a web page. It was an awful job."

      Is this use case recognised by other Universities?

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  jonespm Matthew Jones
                  hmtruscott Harriet Truscott (Inactive)
                • Votes:
                  0 Vote for this issue
                  1 Start watching this issue


                  • Created:

                    Git Source Code