From: Wm M. <mus...@cs...> - 2013-01-22 18:42:46
|
On Mon, January 21, 2013 03:59, Juergen Nickelsen wrote: > On 19.01.2013 04:08, Paul Lesniewski wrote: > >>>> Now I wonder -- do other people feel the need for such a >>>> functionality? > [...] >> This is supported in SquirrelMail natively via $motd in the >> configuration file or option 7 in the configuration tool. You may use >> any HTML you desire (for background color, blinking whirling text, >> whatever). Other plugins can also control it - see the Check Quota >> plugin for an example. If you want to control it using a file instead >> of a setting, a plugin can do that or it might be worthwhile to >> consider submitting a patch for the core. > > In my eyes controlling that message display through a file has > significant benefits: > > (a) It is easier to use for people who are not familiar with > SquirrelMail. I can document it easily with "put a file here with this > name" for others to use, but I (and they) might not be comfortable with > them fiddling with the configuration. > > (b) It is easier to control by external automated means, for instance by > an at(1) job. > > And then there is one thing -- I just tried it, and while it is > certainly a good thing, it is only shown, like the comment string says, > "immediately after a user logs in." > > This is not quite what I want. We have lots of users with long-running > SquirrelMail sessions, and we need to notify those, too. With the > automatic reload of the folder frame, the message even shows up > automatically when the file is placed there, and it disappears > automatically when the file is removed. I like that a lot. > > This is not to say that the motd is a bad idea, only that *I* have the > need for something else. As there has been some interest for my > solution, I do intend to separate it into an own plugin soonish. > > Regards, Juergen. > I thought of motd as well, but I agree that it only helps if you don't need to notify people of events which will happen a couple of days in the future. Not RIGHT NOW!! I was going to recommend that you still look at putting it in via config.pl, but I though better of it. I can see where a user would access the file but you wouldn't want them anywhere near config.pl or the files in modifies. I wonder if giving a designated user the ability to modify it via SM Options might make sense. ------- William R. Mussatto, Senior Systems Engineer http://www.csz.com Ph. 909-920-9154 ext 101 Direct: 909-962-8547 ______________________________________________________________________ CONFIDENTIALITY NOTICE: This communication, including attachments, is for the exclusive use of the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged information. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this by mistake, please contact the sender immediately. |