Forum .LRN Q&A: Question for UAB: .LRN: The following email was just sent from ...

.LRN has this code in dotlrn/www/admin/password-update-2.tcl, which sends first an email to the user with login info, then sends the same email to the admin user, with the subject "The following email was just sent from %system_name%".

Question to UAB: Is this email useful to you?

It's a bite annoying to a number of us (I get them every time someone does particular stuff with the test servers), but if you need it, we can find other solutions to that annoyance.

/Lars

Ok, we will think about it. My first comment is: As long as these system notifications to the end-user are still diffcult to understand and may get lost, it is safer to have somebody get a copy. See for instance this bug https://openacs.org/bugtracker/openacs/bug?bug%5fnumber=1768 regarding ext auth awareness of a similar message.

In the medium future, a distinction is desirable between routine user adminstration, and (potentially dangerous) system / security admistration. See also
https://openacs.org/bugtracker/openacs/bug?bug%5fnumber=1758

Yes, I find them annoying, but i "like" them because they confirm for me that the email was sent out.  This way, if someone calls and says "i didn't get the email" i can say, yes you did, etc.  Not that i really get to say that but at least i know it got sent - i'm just a doubting thomasina.  Actually, there are two other instances where i receive "unwanted" email: 1) when i create a single user account and when i approve users.  The latter email notification was implemented at a time when we were having problems with qmail doing its job.  Would there be an easy to create a site wide admin page with checkboxes for selecting what mail one wants to receive and not receive, so that site wide admins can configure this on their own?
Right, I get a pile of notifications, but I can sort them in my email client and move them into a separate folder. I don't really need them, but they serve as a barometer of use, and since I am dealing with only a few hundred users and am just starting out I am happy when I see them and I think this is because I like fan mail.  Mostly, however, they are a nuisance, and I would like the option of turning these notifications off.  The thing is, as I would customize my implementation, I am having to go looking for the switches to do so, and this is fine insofar as each time I do so I learn something about the system more generally.  But over the long term I would much prefer two levels of sysadmin interface, one with all the switches as they now are, making sense (I would assume) to the people who built the thing, and another for routine administration -- like Nima has made his own, personalized interface, which he refers to has his cockpit.  This would be for stuff for routine administration, such as, a user-friendly interface for things like:

Increase and decrease maximum file size uploads (a patch into aolserver, which presently had to put into my aolserver4 frontend as:

ns_section ns/module/nssock
ns_param maxinput [expr 1024 * 1024 * 10]

Now I mention it: the way to go might be to get Nima's cockpit and make it available to the community.

Ditto that nifty error message setup whereby instead of the flatfile warning you get a form with your warning inserted in one column, then a box asking you to explain what you were doing, then a message suggesting possible fixes.

For example, in dotlrn 2.0.3 my users have to switch their browser to unicode if they want to log on using names with wonderful German umlauts.  I am thinking I may have to clutter up the log in page with a message telling them about this.  But a customized interface would suggest this as a problem.  Of course, this problem might be solved on a deeper level.

So, if you want to give us functionality to switch this notification off, that's just great.  While you are at it, you might build a switching mechanism for other such things!

Thanks!

Bruce