Re: more fun with SMTP and authentication...., posted by Stefan Ritt on Tue Jan 27 09:03:22 2009
|
> For authentication via the Windows IIS I have "basic authentication" with no TLS encryption required - I'm
> not sure if that meets the provider's "SMTP authentication" requirement. When I was using the previous version
> of ELOG (sorry, I did not note the version number) the username was encrypted along with the password. With
> the 2168 build, the password is still encrypted but the usernamer is not; should the password be in "plain
> text" as well?
I changed only the screen output. The username is printed not not encrypted, to be able to check it by eye. The
username sent over the network is and was always encrypted.
The only clue I have is to compare the network traffic you get with an email client (outlook, thunderbird ??)
with the network traffic you get from elogd. To monitor the traffic, I use normally WireShark (formerly Ethereal,
www.wireshark.org). You have to filter for "tcp.port == 25" which is SMTP, then capture your traffic, right-
click on it and select "Follow TCP stream". The result you see in the attachment. The strings produced by elogd
are pink, the strings from the SMTP server are blue. In my case I don't have authentication (our SMTP server does
not support this). In you case, you have to compare the traffic from a functioning email client with elogd. |
Re: Error Message in HTML or Java Script alert, posted by Carsten Elftmann on Tue Jan 27 12:30:26 2009
|
Stefan Ritt wrote: |
Carsten Elftmann wrote: |
I have there a problem with the error message at required attributes.
I have two logbooks with identical settings,
in one the errror message appears as Javascript Alert,
in the other one as html-page, and after using the back button the entered text disapear.
Same I have in this forum.
|
Can you describe what you exactly enter in this forum to produce the error so that I can reproduce it?
|
I could not produce this error here again, so I work on that:
There was a attribute with Type = Date, Preset = $Date.
This added following js code
for (var i=0 ; i<document.form1.y0.value.length ; i++) if ((document.form1.y0.value.charAt(i) < "0" || document.form1.y0.value.charAt(i) > "9")) { break }
This cause in following error
Fehler: document.form1.y0 is undefined Quelldatei: http://elog1.bkitech.de/Test-Maengelbericht/?cmd=Neu Zeile: 16
After that error none js will be executed.
After remarking the Type line, all work well.
|
Is it possible to generate an ID with a particular format ?, posted by Franck C on Tue Jan 27 15:55:38 2009
|
Hi,
I want to know if it is possible to display an ID with this format: YYYY-XXXX where YYYY is the current year and XXXX a sequential number from 0001 to 9999 ?
ID Display = 2009$message id
could be fine but the year is hard coded and there are no 0 before the number.
Can you help me ?
Thanks a lot  |
Re: Is it possible to generate an ID with a particular format ?, posted by Stefan Ritt on Tue Jan 27 16:01:09 2009
|
Franck C wrote: |
Hi,
I want to know if it is possible to display an ID with this format: YYYY-XXXX where YYYY is the current year and XXXX a sequential number from 0001 to 9999 ?
ID Display = 2009$message id
could be fine but the year is hard coded and there are no 0 before the number.
Can you help me ?
Thanks a lot 
|
You cannot make this with the ID, but you can create an additional attribute which will show exactly this behavior. Have a look under
subst <attribute> = %Y-####
in the documentation. |
Re: Stack error when email notification is active, posted by Michael Ambrus on Wed Jan 28 14:38:52 2009
|
Stefan Ritt wrote: |
Michael Ambrus wrote: |
Michael Ambrus wrote: |
Stefan Ritt wrote: |
Michael Ambrus wrote: |
Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).
Please let me know if there is anything I can do to help.
-----------------------------2916890032591
Content-Disposition: form-data; name="attfile"; filename=""
Content-Type: application/octet-stream
-----------------------------2916890032591--
timezone: 0, offset: 0
6 [main] elogd 2816 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
Segmentation fault (core dumped)
|
Cygwin is not officially supported. Can you try the Windows binaries?
|
Sorry, I didn't know there were any (I've not used Elog for years and I think Cygwin was the only way back then). Tried them now and they seem to work. At least no stack error is caused. I'm getting some other error, but I think it's the handshake with the SMTP. I'll validate it's OK until tomorrow.
Windows binaries also solved the issue with the "Top grop" in my other bug rapport.
Thanks for the help!
|
Unfortunately can't validate this right now. I'm at a remote network trying to get ELOG on my Windows laptop working with e-mail notifications. Either my normal ISP will not allow the SMTP to accept relaying from external networks, or something else is wrong.
The Windows binary is behaving somewhat differently, it seems to behave like earlier versions. I.e. the error message seen on the browser (Error sending Email via "smtp.xxx.xxx") is very limited. Logging (level 6) will not revile much and -v doesn't output any hints either. Assuming the first possible cause, I registered a account at gmail to try see if their SMTP would allow e-mail relaying. Trying with the Windows binary version I seemingly leads to the same result (i.e. I don't see much and the error seen at the browser is the same). However, when trying to run ELOG on a machine at my home network the message is different:
Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. w40sm7583927ugc.6
The message does not surprise me (from previous experience, TLS was what made made postfix complicated to set up too). But what does surprise me is that the messages differ between the two (ELOG V2.7.5 running on a Linux machine and the Windows binary of the same version). Does Linux/Windows versions differ by conditionals in the code or did I somehow get an older Windows binary?
It would also be helpful knowing if ayone has got ELOG working with smtp.gmail.com.
Regards /Michael
|
The Windows Binaries are not recompiled for each minor modification. You should check the SVN revistion (the number which shows up at the very bottom of the page, which is 2153 in this case). It might well be that the Windows Binaries do not yet contain the modification for extended SMTP error report.
Furthermore, TLS is not supported in elogd, only plain SMTP is possible.
|
Thanks for the info, it saves me some time know this on beforehand.
You're right about the Windows binary, it's a lower SVN revision (2140).
|
Re: Stack error when email notification is active, posted by Michael Ambrus on Wed Jan 28 14:39:56 2009
|
Stefan Ritt wrote: |
Michael Ambrus wrote: |
Michael Ambrus wrote: |
Stefan Ritt wrote: |
Michael Ambrus wrote: |
Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).
Please let me know if there is anything I can do to help.
-----------------------------2916890032591
Content-Disposition: form-data; name="attfile"; filename=""
Content-Type: application/octet-stream
-----------------------------2916890032591--
timezone: 0, offset: 0
6 [main] elogd 2816 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
Segmentation fault (core dumped)
|
Cygwin is not officially supported. Can you try the Windows binaries?
|
Sorry, I didn't know there were any (I've not used Elog for years and I think Cygwin was the only way back then). Tried them now and they seem to work. At least no stack error is caused. I'm getting some other error, but I think it's the handshake with the SMTP. I'll validate it's OK until tomorrow.
Windows binaries also solved the issue with the "Top grop" in my other bug rapport.
Thanks for the help!
|
Unfortunately can't validate this right now. I'm at a remote network trying to get ELOG on my Windows laptop working with e-mail notifications. Either my normal ISP will not allow the SMTP to accept relaying from external networks, or something else is wrong.
The Windows binary is behaving somewhat differently, it seems to behave like earlier versions. I.e. the error message seen on the browser (Error sending Email via "smtp.xxx.xxx") is very limited. Logging (level 6) will not revile much and -v doesn't output any hints either. Assuming the first possible cause, I registered a account at gmail to try see if their SMTP would allow e-mail relaying. Trying with the Windows binary version I seemingly leads to the same result (i.e. I don't see much and the error seen at the browser is the same). However, when trying to run ELOG on a machine at my home network the message is different:
Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. w40sm7583927ugc.6
The message does not surprise me (from previous experience, TLS was what made made postfix complicated to set up too). But what does surprise me is that the messages differ between the two (ELOG V2.7.5 running on a Linux machine and the Windows binary of the same version). Does Linux/Windows versions differ by conditionals in the code or did I somehow get an older Windows binary?
It would also be helpful knowing if ayone has got ELOG working with smtp.gmail.com.
Regards /Michael
|
The Windows Binaries are not recompiled for each minor modification. You should check the SVN revistion (the number which shows up at the very bottom of the page, which is 2153 in this case). It might well be that the Windows Binaries do not yet contain the modification for extended SMTP error report.
Furthermore, TLS is not supported in elogd, only plain SMTP is possible.
|
Thanks for the info, it saves me some time know this on beforehand.
You're right about the Windows binary, it's a lower SVN revision (2140).
|
Incrementation of attribute is not functioning, help needed to fix this., posted by Guido Böing on Wed Jan 28 18:30:03 2009
|
Hello all,
I appear to be doing something wrong or not..
In my configuration I use an incrementation of a certain attribute (Melding)
For some weird reason it won't increment in this place, while it does in another place...
Below is my configuration (at least the part that gives me headaches..)
[Onderhoud Diversen]
Theme = default
Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Preventief, Regulier, Nav Storing, Overig
Options Categorie = SensorProbes, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Afgerond
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Unit-Lokatie, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= DIVOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Display Email recipients = 0
Email All = aapie@sukkeltje.com
Use Email Subject = $Melding, $Onderwerp - $Status
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime
Login user = person1, person2
The goal of this part of the configuration is a way to notify and log maintenance on not specified equipment.
I expect a message-tag with: DIVOH: 280109-0001, where 280109 stands for 28th of January, 2009, the 0001 is the message number of that day.
Now when I enter something in it, submit the message it will display DIV-OH: 280109-0001 as I expect, but...
When I start with a new entry I would expect DIVOH: 280109-0002 as it is the second message.. Well, simply put.. I don't get DIVOH: 280109-0002 but instead I get DIVOH: 280109-0001 again.Below the part that does work correctly:
The following part of my configuration does work..
[Onderhoud Windows]
Theme = default
Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Categorie = Algemeen, Hardware, Software, Netwerk, Telefonie, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Opgelost
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= WSOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime
When I copy this one, adjust it to be the same as the first one, but then without the extra things it doesn't work, and with them, well.. it still won't.. :(
I am at a loss here where the mistake is, can someone shed some light on this? I would appreciate that very much.
Best regards,
Guido
|
Re: Incrementation of attribute is not functioning, help needed to fix this., posted by Stefan Ritt on Mon Feb 2 09:46:24 2009
|
Guido Böing wrote: |
I appear to be doing something wrong or not..
In my configuration I use an incrementation of a certain attribute (Melding)
For some weird reason it won't increment in this place, while it does in another place...
Below is my configuration (at least the part that gives me headaches..)
[Onderhoud Diversen]
Theme = default
Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Preventief, Regulier, Nav Storing, Overig
Options Categorie = SensorProbes, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Afgerond
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Unit-Lokatie, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= DIVOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Display Email recipients = 0
Email All = aapie@sukkeltje.com
Use Email Subject = $Melding, $Onderwerp - $Status
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime
Login user = person1, person2
|
I tried your configuration and got the attribute incrementing correctly:
so I'm a bit at a loss, too. Maybe your browser caches the old page, so try a "Reload" on your browser or clear your cache. Maybe your logbook contains some weird entries which make the incementing break. Try this configuration with an empty logbook. Certainly the configuration options are correct. |
|