[Building Sakai] Sakai 10 vast amounts of email generated moving content between sites

Matthew Jones matthew at longsight.com
Mon Aug 25 08:48:57 PDT 2014


No, this isn't yet fixed. I looked at this a little more last week and the
comments. The root cause looks like the fix on

https://jira.sakaiproject.org/browse/SAK-24432

Where the issue was that no emails were going out before when they should
have. The fix on SAK-24432 fixed for drop box email notifications going out
and respecting preferences but looks like it caused the regressions where
workflows that previously didn't send out any emails are now sending out
emails.

So it seems like the quick fix would be to revert SAK-24432 (revision
132940 in kernel), it sounds like the bigger fix would probably be as
Matthew Buckett suggests, an extra parameter to the API so it knows when to
do notifications but this would take a little more time and not be
something that would go back to 10.0.


On Mon, Aug 25, 2014 at 11:15 AM, Omer A Piperdi <omer at rice.edu> wrote:

>  One of our instructor copied 'Resources' from a site that he had used
> before to a new site and 400 new resources emails was sent out...
>
> Did anyone solve this problem or is this still an issue?
>
> Thanks
> Omer
>
> On 7/22/2014 8:17 AM, Matthew Jones wrote:
>
> Here looks like the ticket that describes what you're talking about
>
>  https://jira.sakaiproject.org/browse/SAK-26000
>    - Sending when restoring (new feature for 10) was fixed in
> https://jira.sakaiproject.org/browse/KNL-1160
>
>  But it looks like the rest of this ticket was a regression against one
> of the 10 qa's that was never fixed.
> https://jira.sakaiproject.org/browse/SAK-25936
>
>
> On Tue, Jul 22, 2014 at 7:05 AM, Roger Brown <roger.brown at uct.ac.za>
> wrote:
>
>>
>> Hi All
>>
>> If you go to Resources and "Copy Content from My Other Sites" an email is
>> generated to users in the maintain role for each item copied.
>>
>> >From the catalina log for http://nightly2.sakaiproject.org:8081 copying
>> resources from one site to another.
>>
>>
>> 2014-07-22 06:49:22,225  INFO Thread-24 org.sakaiproject.email.impl.BasicEmailService - sendToUsers: users: [Sakai Administrator<> joe soap<joe at soap.com> ] headers: [MIME-Version: 1.0, Content-Type: multipart/alternative; boundary="======sakai-multi-part-boundary======", Subject: [ mercury site - New Resource ] twoColumn.xml, From: "10.x on HSQLDB"<no-reply at localhost>, To: "mercury site"<no-reply at localhost>] message:
>> This message is for MIME-compliant mail readers.
>>
>> --======sakai-multi-part-boundary======
>> Content-Type: text/plain
>>
>> A new resource has been added to the "mercury site" site at 10.x on HSQLDB (http://nightly2.sakaiproject.org:8081/portal
>> )
>>
>> Location: site "mercury site" > Resources  > system > twoColumn.xml
>>
>> Description: twoColumn layout file
>>
>>
>> Resource: twoColumn.xml http://nightly2.sakaiproject.org:8081/access/content/group/mercury/system/twoColumn..xml <http://nightly2.sakaiproject.org:8081/access/content/group/mercury/system/twoColumn.xml>
>>
>>
>>
>> ----------------------
>> This automatic notification message was sent by 10.x on HSQLDB (http://nightly2.sakaiproject.org:8081/portal) from the mercury site site.
>> You can modify how you receive notifications at My Workspace > Preferences.
>>
>> --======sakai-multi-part-boundary======
>> Content-Type: text/html
>>
>> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
>>     "http://www.w3.org/TR/html4/loose.dtd">
>> <html>  <head><title>[ mercury site - New Resource ] twoColumn.xml</title></head>  <body><p>A new resource has been added to the "mercury site" site at <a href="http://nightly2.sakaiproject.org:8081/portal">
>>
>> 10.x on HSQLDB</a>
>> </p><p>
>> Location: site "mercury site" > Resources  > system > <a href="http://nightly2..sakaiproject.org:8081/access/content/group/mercury/system/twoColumn.xml <http://nightly2.sakaiproject.org:8081/access/content/group/mercury/system/twoColumn.xml>">twoColumn.xml</a>
>> </p><p>
>> Description: twoColumn layout file
>> </p><p>
>> <hr/><br/>
>> This automatic notification message was sent by 10.x on HSQLDB (<a href="http://nightly2.sakaiproject.org:8081/portal" >http://nightly2.sakaiproject.org:8081/portal</a>) from the mercury site site.<br/>
>> You can modify how you receive notifications at My Workspace > Preferences.</p>  </body></html>
>>
>> --======sakai-multi-part-boundary======--
>>
>>
>> 2014-07-22 06:49:22,410  INFO Thread-25 org.sakaiproject.email.impl.BasicEmailService - sendToUsers: users: [Sakai Administrator<> joe soap<joe at soap.com> ] headers: [MIME-Version: 1.0, Content-Type: multipart/alternative; boundary="======sakai-multi-part-boundary======", Subject: [ mercury site - New Resource ] Simplehtml.jpg, From: "10.x on HSQLDB"<no-reply at localhost>, To: "mercury site"<no-reply at localhost>] message:
>> This message is for MIME-compliant mail readers.
>>
>> --======sakai-multi-part-boundary======
>> Content-Type: text/plain
>>
>> A new resource has been added to the "mercury site" site at 10.x on HSQLDB (http://nightly2.sakaiproject.org:8081/portal)
>>
>> Location: site "mercury site" > Resources  > system > Simplehtml.jpg
>>
>> Description: simpleRichText layout preview
>>
>> etc
>> etc
>> etc
>>
>> We are definitely seeing this in production deployment of sakai 10.
>>
>> I think this must be a bug because I can't see a configuration item for
>> automatically sending email on the addition of COPIED content. No email
>> sent out on the upload of a new resource.
>>
>> If it is configurable please let me know where the options is, else I'll
>> open a JIRA.
>>
>> Cheers
>>
>> Roger
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Roger Brown
>> Learning Technologies Operations Manager
>> Centre for Innovation in Learning and Teaching (formerly CET and HAEDSU)
>> 7.58 PD Hahn Building Upper Campus
>> University of Cape Town
>> Email/IM/XMPP roger.brown at uct.ac.za
>> Skype rjg.brown
>> Tel:+27(21) 650 4425 <%2B27%2821%29%20650%204425>
>>  ------------------------------
>> UNIVERSITY OF CAPE TOWN
>>
>> This e-mail is subject to the UCT ICT policies and e-mail disclaimer
>> published on our website at
>> http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27
>> 21 650 9111. This e-mail is intended only for the person(s) to whom it
>> is addressed. If the e-mail has reached you in error, please notify the
>> author. If you are not the intended recipient of the e-mail you may not
>> use, disclose, copy, redirect or print the content. If this e-mail is not
>> related to the business of UCT it is sent by the sender in the sender's
>> individual capacity.
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>  !DSPAM:2294,53ce649f47138327110944!
>
> _______________________________________________
> sakai-dev mailing listsakai-dev at collab.sakaiproject.orghttp://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
>  with a subject of "unsubscribe"
>
> !DSPAM:2294,53ce649f47138327110944!
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140825/0c45f47a/attachment.html 


More information about the sakai-dev mailing list