Re: Email boolean , posted by Finn Junker on Thu Oct 10 09:27:42 2019
|
> > > Hello Elog forum
> > >
> > > Is it possible to email boolean statements, like if a checkbox is checked to email certain people?
> > >
> > > My Configuration looks like this but dosn't work:
> > >
> > > Attributes = Bruger, Station, Emne, Status, PM5
> > > Options PM5 = boolean
> > > Email PM5 = fj@tvis.net
> > >
> > > Kind Regards
> > >
> > > Finn
> >
> > I still don't have a solution to the above, but this works:
> >
> > Attributes = Bruger, Station, Emne, Status, PM5
> > ROptions PM5 = Ja
> > Email PM5 Ja = th@tvis.net, fj@tvis.net
> >
> > Kind Regards
> >
> > Finn
>
> You were so close: boolean has the two values "0" (unchecked) and "1" (checked).
>
> Attributes = Bruger, Station, Emne, Status, PM5
> Options PM5 = boolean
> Email PM5 1 = fj@tvis.net
>
> That does work, I've tested it.
Of course :-)
Thank you Andreas
Kind Regards Finn |
|
Re: Email based on not attribute value, posted by Stefan Ritt on Wed Jan 18 12:49:39 2006
|
| Chris Warner wrote: | | For instance, I have a server logbook that several people are able to write to. There is one person that is ultimately responsible for this server. I would like to generate an email any time that someone other than the System Administrator creates a new entry. |
No, but there is a trick you can use. Put following into your config file:
Attributes = Author, ...
Preset Author = $long_name
Locked Attributes = Author
Options Author = Admin{1}, other{2}
{1}Suppress default = 1
Replace "Admin" with the name of the administrator. The "Author" field gets automatically set to the author name, and it's locked, so there will no be drop-down box which lets you select between "Admin" and "other". Now if the author is equal to "Admin", the condition {1} becomes true, and the "Supress default is executed. This check the "suppress email notificatio" box at the bottom, so normally no email gets sent from the administrator. |
|
Re: Email authentication with SSL/TLS, posted by Stefan Ritt on Fri Mar 6 21:51:48 2009
|
| Val Schmidt wrote: |
|
Hi,
I'm curious is it possible to send email notificaitons from elog through an smtp server that requires SSL/TLS authentication? I think it's not but I thought I'd ask.
-Val
|
This is currently not implemented and will probably not implemented in the next time, but it's on my (very long) to-do list. |
|
Re: Email Notification: Clarification on Attribute - can value be a string?, posted by Stefan Ritt on Fri Oct 26 11:18:59 2007
|
If you read
http://midas.psi.ch/elog/config.html#email
you will see the sentence:
If either the attribute or the value contains one or more blanks the string must be enclosed with quotation marks, as in:
* Email Type "Normal routine" = ...
so in your case you should write
Email Report "Shift Summary" = ... |
|
Re: Email Notification and Icons, posted by Stefan Ritt on Mon Sep 19 20:39:17 2005
|
| Mario Apodaca wrote: | | 1) When sending out email notifications, is there a way to surpress the entries that have been left on the logbook? I want to be notified that someone has posted, but not receive the posting in the email. |
You specify what is sent by email notification with the Email format = <n> option. Adding the right numbers there, you can send only the notification, but not the contents or attachments. An alternative is to use the RSS functionality in Elog. With an RSS reader, you only see the subject, and can download the whole body upon request.
| Mario Apodaca wrote: | | 2) Is there a way to set icons to users, so that each user has a defined icon? I set up a new attribute called: Author Icon and then tried using conditional attributes to have an icon set to a specific user. When I tested by posting, in the Author Icon section I didn't have an icon, instead a text box appeared with the name of the icon. |
No, this is not possible without modification of elog. In principle you can tell elog that a certain attribute is an icon by using the "Ioptions author icon = icon1.gif, icon2.gif"), but then you get a list if possible icons each time from which you have to select. Not very convenient. The concept of an Avatar is not preent in elog, you bette choose a bulletin board system for that. |
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 08:50:16 2017
|
Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?
| Phil Rubin wrote: |
|
Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) . Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this. Can you see what it is? Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?
[global]
.
Suppress Email to users = 1
.
[Notebook]
.
Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...
.
{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...
{3} Email Category TDAQ =
.
Use Email Subject = Elog Notice: $subject
Command: /usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
|
|
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Phil Rubin on Wed Jul 19 08:59:52 2017
|
Thank you for responding.
I thought I provided the command at the end of the note:
/usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text. The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.
For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.
Sorry for forgetting these details: bash shell; linus version 2.6.32-696.el6.x86_64
| Andreas Luedeke wrote: |
|
Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?
| Phil Rubin wrote: |
|
Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) . Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this. Can you see what it is? Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?
[global]
.
Suppress Email to users = 1
.
[Notebook]
.
Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...
.
{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...
{3} Email Category TDAQ =
.
Use Email Subject = Elog Notice: $subject
Command: /usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
|
|
|
|
Re: Email Notification (Not) Initiated by elog Client Utility, posted by Andreas Luedeke on Wed Jul 19 10:14:44 2017
|
If that is your command then it is obvious why no email is send:
you do set "Type=Type", but only for "Type=Problem(s)" and "Category=TDAQ" you would send an email.
Instead of writing "-h host" you should as well define the actual hostname, like "-h midas.psi.ch", likewise for all other parameter.
| Phil Rubin wrote: |
|
Thank you for responding.
I thought I provided the command at the end of the note:
/usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
This results in an entry being appropriately logged in Notebook with the correct author, type, category, subject, and text. The only problem is that, when the type is such that email notification should be sent to the list associated with category, it is not sent.
For the record, I reconfigured elogd.conf so that parentheses are no longer there, but this made no difference, so this isn't the problem.
Sorry for forgetting these details: bash shell; linus version 2.6.32-696.el6.x86_64
| Andreas Luedeke wrote: |
|
Yes, parentheses in field content might be difficult to pass from a shell command. You did not even mention which Linux shell you are using and you did not show the actual elog command. Maybe you want to add that information?
| Phil Rubin wrote: |
|
Our configuration sends out e-mail notifications based on a hierarchy of attributes, and works fine with WEB submissions, but not with client utility submissions (no notifications are sent; the log doesn't show it even trying to send any: 14-Jul-2017 18:36:01 [rubinp@nn.nn.nn.nn] {Notebook} NEW entry #0) . Since notification is the default (suppression requires -x), I presume there is something wrong with the way we're going about this. Can you see what it is? Could it be the parentheses in the type Problem(s), which have to be sent at the shell in the client command as Type=Problem\(s\)?
[global]
.
Suppress Email to users = 1
.
[Notebook]
.
Attributes = Author, Type, Category, Subject
Options Type = Routine{1}, Problem(s){2}, Other{3}
Options Category = ... TDAQ ...
.
{1} Email Category TDAQ =
{2} Email Category TDAQ = user1@aa.bb, user2@cc.dd,...
{3} Email Category TDAQ =
.
Use Email Subject = Elog Notice: $subject
Command: /usr/local/bin/elog -h host -p port -l Notebook -u user passwd -a Author="Author" -a Type=Type -a Category=Category -a Subject="subject" "text"
|
|
|
|
|