Details
-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.2.2
-
Fix Version/s: 2.3.0
-
Component/s: Announcements
-
Labels:None
Description
This behavior was introduced by a fix that may have exceeded the original issue.
It is logical that a recipient may want to reply to the person who triggered an announcement/notification for some reason. This is not currently possible, but was before the fix was made.
Stephen Marquard has an idea about resolving this. It is included here:
Date: Wed, 11 Jan 2006 12:35:55 +0200
From: Stephen Marquard <marquard@ched.uct.ac.za>
To: Seth Theriault <slt@columbia.edu>
Subject: Re: Notification email changes
[...]
My suggestion for resolving this is a sakai.properties option which you can set to enable sending notifications from user addresses if available.
If not set, it defaults to current behaviour. If set, notifications will use the full name and email address of the user triggering the notification if
available, otherwise it will use the user's full name but no-reply, e.g.
No sakai.properties option set:
From: "Sakai Service Name" <no-reply@some.domain>
else if sakai.properties set:
If user has an email address configured:
From: "Stephen Marquard" <smarquard@some.domain>
else
From: "Stephen Marquard" <no-reply@some.domain>
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Subversion
we've had a couple of complaints about this from users since the fix for SAK-2035 was put in place. Essentially the user can no longer tell who sent the announcement or updated a resource and this information is often times helpful when trying to follow up. Even if it's not listed in the From: field, the sender's name should be listed somewhere within the message.
Is it possible to get this fixed for 2.1.2 ?
So what actually happened to this in 2.3 if anything? The behaviour seems unchanged, viz.:
-------- Original Message --------
Subject: [ Vula Dev - New Resource ] tool-oddity.jpg
Date: Tue, 21 Nov 2006 16:48:21 +0200 (SAST)
From: Vula<no-reply@vula.uct.ac.za>
To: Vula Dev<no-reply@vula.uct.ac.za>
A new resource has been added to the "Vula Dev" site at Vula (https://vula.uct.ac.za/portal)
Location: site "Vula Dev" > Resources > tool-oddity.jpg
Description: Test notification
Resource: tool-oddity.jpg https://vula.uct.ac.za/access/content/group/d02f250e-be2d-4b72-009a-161d66ed6df9/tool-oddity.jpg
----------------------
This automatic notification message was sent by Vula (https://vula.uct.ac.za/portal) from the Vula Dev site.
You can modify how you receive notifications at My Workspace > Preferences.
Thanks to Seth for sleuthing. Replyable notifications can be configured in sakai.properties like this:
emailFromReplyable@org.sakaiproject.event.api.NotificationService=true
A replyable notification looks like:
-------- Original Message --------
Subject: [ Vula Dev - New Resource ] tues-test
Date: Wed, 22 Nov 2006 10:20:40 +0200 (SAST)
From: Stephen Marquard <stephen.marquard@uct.ac.za>
To: Vula Dev<no-reply@sakai.cet.uct.ac.za>
A new resource has been added to the "Vula Dev" site at Vula (https://sakai.cet.uct.ac.za/portal)
Location: site "Vula Dev" > Resources > tues-test
Description: testing notifications that are replyable
Resource: tues-test https://sakai.cet.uct.ac.za/access/content/group/d02f250e-be2d-4b72-009a-161d66ed6df9/tues-test
----------------------
This automatic notification message was sent by Vula (https://sakai.cet.uct.ac.za/portal) from the Vula Dev site.
You can modify how you receive notifications at My Workspace > Preferences.
Seth, it sounds like this Feature Request ending up getting addressed somewhere along the way. Is that right?
A related feature request: replying to no-reply@domain.edu silently fails.
Recently, from an instructor: "My students keep telling me they try to use reply to send me messages. (Alas.)"
Seems like a philosophical question, whether replying to a no-reply address should be rewarded with a bounce message. Maybe a little tough love is in order here. In the way-back world, did we fill the reply-to address with email address of the person who posted the announcement? Maybe this is the feature being requested... the ability to set the announcement to
Allow email reply?
No-reply
Reply to me
If-n Message Center is active, I suppose the reply could go into the sender's private message box. And then there's the whole thread about a single stage for messaging. How might this seemingly straightforward feature request relate to that?
Documenting current behaviour: if you additionally set in sakai.properties
emailToReplyable@org.sakaiproject.event.api.NotificationService=true
then you get results like this:
------ Original Message ------
Subject: [ Vula Dev - Announcement ] testing notifications
Date: Mon, 27 Nov 2006 19:19:17 +0200 (SAST)
From: Stephen Marquard <stephen.marquard@uct.ac.za>
To: Vula Dev <dev@sakai.cet.uct.ac.za>
An announcement has been added in the "Vula Dev" site at Vula
(https://sakai.cet.uct.ac.za/portal)
Subject: testing notifications
From: Stephen Marquard
Date: 27-Nov-2006 19:19
Message:
notification test
--------------------
This automatic notification message was sent by Vula
(https://sakai.cet.uct.ac.za/portal) from the Vula Dev site.
You can modify how you receive notifications at My Workspace > Preferences. 19:20
if you have no alias you get the no-reply addr, viz.: 19:21
If the site does not have an alias, you get:
------ Original Message ------
Subject: [ Blogger - Announcement ] testing notices in non-archive site
Date: Mon, 27 Nov 2006 19:21:09 +0200 (SAST)
From: Stephen Marquard <stephen.marquard@uct.ac.za>
To: Blogger <no-reply@sakai.cet.uct.ac.za>
An announcement has been added in the "Blogger" site at Vula
(https://sakai.cet.uct.ac.za/portal)
Subject: testing notices in non-archive site
From: Stephen Marquard
Date: 27-Nov-2006 19:21
Message:
test
--------------------
This automatic notification message was sent by Vula
(https://sakai.cet.uct.ac.za/portal) from the Blogger site.
You can modify how you receive notifications at My Workspace > Preferences.
SAK-2035is the original issue