Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 420 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  2237   Thu May 31 23:46:31 2007 Entry Mark Bergmanmark.bergman@uphs.upenn.eduQuestionLinuxV2.6.5config settings to ensure replies to author, thread contributors, admin?
I'm having some difficulty configuring elog to ensure that the original author of an entry, any contributors to the thread, and a desginated administrator get e-mail notification for any change to the thread.

Here's a subset of the current elogd.cfg:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status, CC E-mail To
Display Email recipients = 1
Email All = $CC E-mail To
Email All = mark.bergman@uphs.upenn.edu
Email Format = 47
Suppress default = 0
Type CC E-mail To = museremail

The "Suppress default = 0" setting is used because many people mistakenly subscribe for automatic e-mail notification of all our logbooks when they self-register. I was hoping that the "Email All" directives would override the suppression of default mail.

This configuration works partially...in that if a user specifically selects addresses in the "CC E-mail To" field, those people do get mail.

The documentation states that there can be multiple "Email All" directives, so I thought they would be additive--causing the admin address and the author to always get mail.

Is there a setting to ensure that the original author of the thread is always notified upon any change?


Thanks,

Mark
  2238   Fri Jun 1 08:40:13 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV2.6.5Re: config settings to ensure replies to author, thread contributors, admin?

Mark Bergman wrote:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status, CC E-mail To
Display Email recipients = 1
Email All = $CC E-mail To
Email All = mark.bergman@uphs.upenn.edu
Email Format = 47
Suppress default = 0
Type CC E-mail To = museremail

The documentation states that there can be multiple "Email All" directives, so I thought they would be additive--causing the admin address and the author to always get mail.


There can be multiple "Email All" directives, but they have to be on one line, like
Email All = $CC E-mail To, mark.bergman@uphs.upenn.edu


Mark Bergman wrote:

Is there a setting to ensure that the original author of the thread is always notified upon any change?


You can do something like:
Attributes = ..., Author Email
Preset Author Email = $user_email
Email All = $Author Email, $CC E-mail to, mark.bergman@uphs.upenn.edu
...

An alternative (and that's what I usually do) is to keep "Suppress email to users = 0" and tell the users to remove their subscription if they don't like it. Note that you also can edit the password file manually (it's a XML file), and remove all subscriptions easily with an editor. Note that you have to do that when elogd is stopped, then edit the file, then restart elgod.

- Stefan
  2239   Fri Jun 1 08:43:23 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV2.6.5-186Re: how to supress checkboxes of all logbooks at registration?

Mark Bergman wrote:
Is there a way to suppress the listing of all logbooks on the New User Registration page? We've got 100 logbooks (one for each server, cluster node, or major software package). The long list makes it difficult for users to find the bottom of the registration page, and no user needs to subscribe for automatic e-mail notification for every logbook.


No, this is currently not possible. But I wonder why you have so many logbooks. Instead of having an individual logbook for every server, you could have the server name as an attribute of a single logbook:
Attributes = Author, ..., Server
Options Server = server1, server2, ...
Quick filter = Server
...

Using the quick filter, you can select the subset of logbook entries belonging to one server very easily. In general it will make your life much easier if you have less logbooks.

- Stefan
  2261   Wed Jun 27 22:01:56 2007 Question JJ Sheppardjsheppard@tracstar.netQuestionLinux2.6.5Error sending Email via "XXX.XXX.XXX.XXX"
I read most of the posts and used the -v to see whats happening, all i get is this. It hangs at the "250 HELP" line for about 3 secs then moves on to what is displayed. From the posts it looks like there should be alot more info to see. Any idea on how to get it to display right?

I have telneted into the mail server and tested it, so i know its working that way.

-----------------------------11323166884439--

Email "Case Holder" JJ to jsheppard@XXXX.net

timezone: 18000, offset: -14400

Email from advservices@XXXX.net to jsheppard@XXXX.net, SMTP host XXX.XXX.XXX.XXX:
220 Welcome to the @Mail v4.4 SMTP Server ( Exim )
EHLO server.XXXX.net
250-MX1.SPIDERHOST.COM Hello server.XXXX.net [XXX.XXX.XX.XX]
250-SIZE 10485760
250-PIPELINING
250-AUTH LOGIN
250 HELP
==== Return ================================
HTTP/1.1 302 Found
Server: ELOG HTTP 2.6.5-1844
Connection: Keep-Alive
Keep-Alive: timeout=60, max=10
Location: http://XXX.XXX.XXX.XXX:8080/2WaySupport/1?error=Error+sending+Email+via+<i>"XXX.XXX.XXX.XXX"</i>
Content-Length: 20
  2266   Thu Jun 28 17:12:11 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.5Re: Error sending Email via "XXX.XXX.XXX.XXX"

JJ Sheppard wrote:
220 Welcome to the @Mail v4.4 SMTP Server ( Exim )
EHLO server.XXXX.net
250-MX1.SPIDERHOST.COM Hello server.XXXX.net [XXX.XXX.XX.XX]
250-SIZE 10485760
250-PIPELINING
250-AUTH LOGIN
250 HELP


The problem there is that your SMPT server does not reply with
250 OK

which my server does. So elogd was waiting 3 seconds for "OK", and then aborted. I change the code (now in SVN revision 1871) to look for "250 " (with one blank at the end). You have to update from SVN, recompile and try again. Anyhow elogd only supports plain login authentication ("AUTH LOGIN"), which not all SMPT servers accept. You have to see.
  2274   Fri Jun 29 16:14:16 2007 Reply JJ Sheppardjsheppard@tracstar.netQuestionLinux2.6.5Re: Error sending Email via "XXX.XXX.XXX.XXX"

Stefan Ritt wrote:

JJ Sheppard wrote:
220 Welcome to the @Mail v4.4 SMTP Server ( Exim )
EHLO server.XXXX.net
250-MX1.SPIDERHOST.COM Hello server.XXXX.net [XXX.XXX.XX.XX]
250-SIZE 10485760
250-PIPELINING
250-AUTH LOGIN
250 HELP


The problem there is that your SMPT server does not reply with
250 OK

which my server does. So elogd was waiting 3 seconds for "OK", and then aborted. I change the code (now in SVN revision 1871) to look for "250 " (with one blank at the end). You have to update from SVN, recompile and try again. Anyhow elogd only supports plain login authentication ("AUTH LOGIN"), which not all SMPT servers accept. You have to see.


This is what I get now, Is this the Auth Login problem you were speaking of?

Email from elog@XXXXX.net to jsheppard@XXXXX.net, SMTP host XXX.XXX.XXX.XXX:
220-server.XXXXXX.net ESMTP Exim 4.66 #1 Fri, 29 Jun 2007 10:03:22 -0400
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
EHLO server.tracstar.net
250-server.tracstar.net Hello server.XXXXXX.net [XXX.XXX.XXX.XXX]
250-SIZE 52428800
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
AUTH LOGIN
Username:
XXXXXXXX
Password:
XXXXXXXX
535 Incorrect authentication data
==== Return ================================
HTTP/1.1 302 Found
  2275   Fri Jun 29 16:16:58 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.5Re: Error sending Email via "XXX.XXX.XXX.XXX"

JJ Sheppard wrote:
This is what I get now, Is this the Auth Login problem you were speaking of?

Email from elog@XXXXX.net to jsheppard@XXXXX.net, SMTP host XXX.XXX.XXX.XXX:
220-server.XXXXXX.net ESMTP Exim 4.66 #1 Fri, 29 Jun 2007 10:03:22 -0400
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
EHLO server.tracstar.net
250-server.tracstar.net Hello server.XXXXXX.net [XXX.XXX.XXX.XXX]
250-SIZE 52428800
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
AUTH LOGIN
Username:
XXXXXXXX
Password:
XXXXXXXX
535 Incorrect authentication data


No. It looks like PLAIN LOGIN is supported, but your username/password is wrong. Ask your SMPT system administrator.
  2276   Fri Jun 29 16:30:46 2007 Reply JJ Sheppardjsheppard@tracstar.netQuestionLinux2.6.5Re: Error sending Email via "XXX.XXX.XXX.XXX"

Stefan Ritt wrote:

JJ Sheppard wrote:
This is what I get now, Is this the Auth Login problem you were speaking of?

Email from elog@XXXXX.net to jsheppard@XXXXX.net, SMTP host XXX.XXX.XXX.XXX:
220-server.XXXXXX.net ESMTP Exim 4.66 #1 Fri, 29 Jun 2007 10:03:22 -0400
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
EHLO server.tracstar.net
250-server.tracstar.net Hello server.XXXXXX.net [XXX.XXX.XXX.XXX]
250-SIZE 52428800
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
AUTH LOGIN
Username:
XXXXXXXX
Password:
XXXXXXXX
535 Incorrect authentication data


No. It looks like PLAIN LOGIN is supported, but your username/password is wrong. Ask your SMPT system administrator.


I dubbed checked it and ran the -t command to make sure it was the right password. Any thing else I can try?

This is whats in the global
SMTP host = XXX.XX.XX.XX
SMTP username = advservices@XXXXX.XXX
SMTP Password = dDE5ODQ=
Use Email From = advservices@XXXX.XXX

and i still get this
250 HELP
AUTH LOGIN
Username:
XXXXX
Password:
XXXXX
535 Incorrect authentication data
ELOG V3.1.5-3fb85fa6