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>
