ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67705
|
Wed Sep 17 17:45:18 2014 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | V2.9.2-24 | Re: Sort by date prior to 2002 |
Chris Jennings wrote: |
Chris Jennings wrote: |
I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?
Thanks in advance,
Chris
|
Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort.
|
I think I remember that this has been discussed earlier: it is a little bug in elogd.
You can see where it comes from if you type in the little command 'date -d "9-Sep-2001 3:46:40" +%s'
Converted to "seconds of the epoche" (seconds since 1970-01-01 00:00:00 UTC) the date "9-Sep-2001 3:46:40" has one digit more than "9-Sep-2001 3:46:39".
Since elog makes a string comparison, suddenly 1'000'000'000 is less than 999'999'999; therefore the wrong sorting.
Workaround: you can modify your old entries and add a leading zero to all entries where your specific date field starts with a '9'.
Stefan: you should fix it at least well before 20-Nov-2286 18:46:40, when the same bug strikes again!  |
67706
|
Mon Sep 22 14:39:10 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | All | V2.9.2-24 | Re: Sort by date prior to 2002 |
Andreas Luedeke wrote: |
Chris Jennings wrote: |
Chris Jennings wrote: |
I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?
Thanks in advance,
Chris
|
Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort.
|
I think I remember that this has been discussed earlier: it is a little bug in elogd.
You can see where it comes from if you type in the little command 'date -d "9-Sep-2001 3:46:40" +%s'
Converted to "seconds of the epoche" (seconds since 1970-01-01 00:00:00 UTC) the date "9-Sep-2001 3:46:40" has one digit more than "9-Sep-2001 3:46:39".
Since elog makes a string comparison, suddenly 1'000'000'000 is less than 999'999'999; therefore the wrong sorting.
Workaround: you can modify your old entries and add a leading zero to all entries where your specific date field starts with a '9'.
Stefan: you should fix it at least well before 20-Nov-2286 18:46:40, when the same bug strikes again! 
|
Ok, well before 2286 approaches I fixed that bug and committed it to the GIT repository (master branch).
/Stefan |
67716
|
Fri Nov 21 12:38:07 2014 |
| harish amin | harish.amin@holiday.co.om | Info | Windows | 2.8 | 5.5.4 cannot decode AUTH parameter | Dear Team,
I am having a log book and would like to activate the email notification. I have made the changes as per the guidelines but I am getting the error message while submitting the entry - Error sending Email via "smtp.omantel.net.om": 5.5.4 cannot decode AUTH parameter
The details are as below : (Please note I have replaced the password with the * marks)
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} NEW entry #0
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} Email from <harish.amin@holiday.co.om> to harish.amin@holiday.co.om, SMTP host smtp.omantel.net.om
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} 220 fmgw1.omantel.net.om ESMTP Smtpd; Fri, 21 Nov 2014 15:32:52 +0400
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT}
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} EHLO localhost
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-fmgw1.omantel.net.om Hello [188.66.222.72], pleased to meet you
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-ENHANCEDSTATUSCODES
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-PIPELINING
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-8BITMIME
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-SIZE 32235520
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DSN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-AUTH LOGIN PLAIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-STARTTLS
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DELIVERBY
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250 HELP
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} AUTH LOGIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Username
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} harish.amin@holiday.co.om
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Password
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} ******
21-Nov-2014 16:58:30 [harish@127.0.0.1] {SCREENING VISIT} 501 5.5.4 cannot decode AUTH parameter ******
Please help me to resolve this issue.
Thank you
Harish Amin |
67717
|
Fri Nov 21 16:09:37 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | 2.8 | Re: 5.5.4 cannot decode AUTH parameter |
harish amin wrote: |
Dear Team,
I am having a log book and would like to activate the email notification. I have made the changes as per the guidelines but I am getting the error message while submitting the entry - Error sending Email via "smtp.omantel.net.om": 5.5.4 cannot decode AUTH parameter
The details are as below : (Please note I have replaced the password with the * marks)
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} NEW entry #0
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} Email from <harish.amin@holiday.co.om> to harish.amin@holiday.co.om, SMTP host smtp.omantel.net.om
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} 220 fmgw1.omantel.net.om ESMTP Smtpd; Fri, 21 Nov 2014 15:32:52 +0400
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT}
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} EHLO localhost
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-fmgw1.omantel.net.om Hello [188.66.222.72], pleased to meet you
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-ENHANCEDSTATUSCODES
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-PIPELINING
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-8BITMIME
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-SIZE 32235520
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DSN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-AUTH LOGIN PLAIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-STARTTLS
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DELIVERBY
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250 HELP
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} AUTH LOGIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Username
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} harish.amin@holiday.co.om
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Password
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} ******
21-Nov-2014 16:58:30 [harish@127.0.0.1] {SCREENING VISIT} 501 5.5.4 cannot decode AUTH parameter ******
Please help me to resolve this issue.
Thank you
Harish Amin
|
For the login to your email sever, the password is encoded in base64 form (actually not really secure). Somehow your server does not support this. Unfortunately I cannot test this without access to your server. But you can try yourself by doing a telnet to your mail server like:
$ telnet <server.domanin> 25
...
$ AUTH PLAIN
With the "plain" method, you should be able to enter your password in plain text (not base64 encoded), and see if that works. If you are successful, I can add this option to elog.
Best,
Stefan |
67718
|
Fri Nov 21 17:00:09 2014 |
| harish amin | harish.amin@holiday.co.om | Info | Windows | 2.8 | Re: 5.5.4 cannot decode AUTH parameter |
Stefan Ritt wrote: |
harish amin wrote: |
Dear Team,
I am having a log book and would like to activate the email notification. I have made the changes as per the guidelines but I am getting the error message while submitting the entry - Error sending Email via "smtp.omantel.net.om": 5.5.4 cannot decode AUTH parameter
The details are as below : (Please note I have replaced the password with the * marks)
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} NEW entry #0
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} Email from <harish.amin@holiday.co.om> to harish.amin@holiday.co.om, SMTP host smtp.omantel.net.om
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} 220 fmgw1.omantel.net.om ESMTP Smtpd; Fri, 21 Nov 2014 15:32:52 +0400
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT}
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} EHLO localhost
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-fmgw1.omantel.net.om Hello [188.66.222.72], pleased to meet you
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-ENHANCEDSTATUSCODES
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-PIPELINING
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-8BITMIME
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-SIZE 32235520
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DSN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-AUTH LOGIN PLAIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-STARTTLS
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DELIVERBY
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250 HELP
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} AUTH LOGIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Username
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} harish.amin@holiday.co.om
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Password
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} ******
21-Nov-2014 16:58:30 [harish@127.0.0.1] {SCREENING VISIT} 501 5.5.4 cannot decode AUTH parameter ******
Please help me to resolve this issue.
Thank you
Harish Amin
|
For the login to your email sever, the password is encoded in base64 form (actually not really secure). Somehow your server does not support this. Unfortunately I cannot test this without access to your server. But you can try yourself by doing a telnet to your mail server like:
$ telnet <server.domanin> 25
...
$ AUTH PLAIN
With the "plain" method, you should be able to enter your password in plain text (not base64 encoded), and see if that works. If you are successful, I can add this option to elog.
Best,
Stefan
|
Dear Stefan
Thank you for your reply. Please check is my entry correct?
port = 8080
Admin user = harish
url = http://localhost:8080
;Find Menu commands = Logout, New, Find, Select, Config, Last day, Last 10, Help
;Guest Menu commands = Login, Back, Find, Last day, Last 10, Help, Logout
;Guest Find Menu commands = Login, Back, Find, Last day, Last 10, Help
SMTP host = smtp.omantel.net.om
SMTP port = 25
$telnet smtp.omantel.net.om 25
$AUTH PLAIN
SMTP username = harish.amin@holiday.co.om
SMTP Password = ********
Subst Email = $user_email
Logfile = errorh.log
Email Encoding = 4
Entries per page = 50
;Logfile = harish.log
;Logging level = 2 |
67719
|
Sat Nov 22 14:50:35 2014 |
| harish amin | harish.amin@holiday.co.om | Info | Windows | 2.8 | Re: 5.5.4 cannot decode AUTH parameter |
harish amin wrote: |
Stefan Ritt wrote: |
harish amin wrote: |
Dear Team,
I am having a log book and would like to activate the email notification. I have made the changes as per the guidelines but I am getting the error message while submitting the entry - Error sending Email via "smtp.omantel.net.om": 5.5.4 cannot decode AUTH parameter
The details are as below : (Please note I have replaced the password with the * marks)
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} NEW entry #0
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} Email from <harish.amin@holiday.co.om> to harish.amin@holiday.co.om, SMTP host smtp.omantel.net.om
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} 220 fmgw1.omantel.net.om ESMTP Smtpd; Fri, 21 Nov 2014 15:32:52 +0400
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT}
21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} EHLO localhost
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-fmgw1.omantel.net.om Hello [188.66.222.72], pleased to meet you
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-ENHANCEDSTATUSCODES
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-PIPELINING
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-8BITMIME
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-SIZE 32235520
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DSN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-AUTH LOGIN PLAIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-STARTTLS
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DELIVERBY
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250 HELP
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} AUTH LOGIN
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Username
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} harish.amin@holiday.co.om
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Password
21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} ******
21-Nov-2014 16:58:30 [harish@127.0.0.1] {SCREENING VISIT} 501 5.5.4 cannot decode AUTH parameter ******
Please help me to resolve this issue.
Thank you
Harish Amin
|
For the login to your email sever, the password is encoded in base64 form (actually not really secure). Somehow your server does not support this. Unfortunately I cannot test this without access to your server. But you can try yourself by doing a telnet to your mail server like:
$ telnet <server.domanin> 25
...
$ AUTH PLAIN
With the "plain" method, you should be able to enter your password in plain text (not base64 encoded), and see if that works. If you are successful, I can add this option to elog.
Best,
Stefan
|
Dear Stefan
Thank you for your reply. Please check is my entry correct?
port = 8080
Admin user = harish
url = http://localhost:8080
;Find Menu commands = Logout, New, Find, Select, Config, Last day, Last 10, Help
;Guest Menu commands = Login, Back, Find, Last day, Last 10, Help, Logout
;Guest Find Menu commands = Login, Back, Find, Last day, Last 10, Help
SMTP host = smtp.omantel.net.om
SMTP port = 25
$telnet smtp.omantel.net.om 25
$AUTH PLAIN
SMTP username = harish.amin@holiday.co.om
SMTP Password = ********
Subst Email = $user_email
Logfile = errorh.log
Email Encoding = 4
Entries per page = 50
;Logfile = harish.log
;Logging level = 2
|
Dear Stefen,
Please help me & reply on my request. Is my global config correct? |
67720
|
Sat Nov 22 16:05:34 2014 |
| Yoshio Imai | $user_email | Info | Windows | 2.8 | Re: 5.5.4 cannot decode AUTH parameter |
harish amin wrote: | Dear Stefen,
Please help me & reply on my request. Is my global config correct? |
I am afraid you misunderstood Stefan. The lines he suggested to you are not something to put into your config file, but something you have to type on the command prompt in order to communicate directly with the mail server (i.e. completely independent from elog). You may have to ensure that the necessary communication program is installed on your computer.
Regards
Yoshio |
67837
|
Wed Mar 25 10:36:15 2015 |
| Tim Schel | tim.schelfhout@fixbrussel.be | Info | Linux | Windows | 3.00 | test | zezerze |
|