ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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? |
202
|
Fri Jan 31 20:47:51 2003 |
| Matthew | greggmc@yahoo.com | Info | | | Re: Write only | Does this truly disable the edit command or just hide it?
> > I'm interested using elog for a lab notebook. Once entries have been
> > entered they cannot be changed/edited.
> > Is it possible for elog to be setup to support something like this? A write
> > only mode?
>
> What you need is an entry in the elogd.cfg file:
>
> Manu commands = Back, New, Reply, Find, Config, Logout, Help
>
> As you see, the "Edit" and "Delete" commands are missing here and therefore
> do not get displayed. So you can enter a message with "New", but you cannot
> change it afterwards. |
68812
|
Fri Jun 1 17:08:48 2018 |
| Giuseppe Cucinotta | giuseppe.cucinotta@unifi.it | Info | Linux | 3.1.1 | text area height | Hi,
I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum height of the text box fixed (for instance 500px) is by far more useful of viewing the attachment box (we know it is down scrolling the page :) ). We know it is possible to resize the text box using the mouse but doing this every time one creates a new entry can be annoying. Setting a default minimum size would be more confortable. Is it possible to do this?
Thank you
Beppe |
68815
|
Tue Jun 5 15:06:18 2018 |
| Giuseppe Cucinotta | giuseppe.cucinotta@unifi.it | Info | Linux | 3.1.1 | Re: text area height | I tried with Message Height = 100 inside the conifguration of my logbook, but nothing changed as you can see in the first picture...
What I'm looking for is a way, if possible, to start by default with a wider message box, someting like fig2. For our purpose, using wide tables, it would be very useful to have a wider message box in order to have a full look to the message content, and also having it by default without modifying it by hand with the mouse every time we submit something to elog.
Beppe
Stefan Ritt wrote: |
Have you tried
Message height = ...
unit is number of text lines.
Stefan
Giuseppe Cucinotta wrote: |
Hi,
I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum height of the text box fixed (for instance 500px) is by far more useful of viewing the attachment box (we know it is down scrolling the page :) ). We know it is possible to resize the text box using the mouse but doing this every time one creates a new entry can be annoying. Setting a default minimum size would be more confortable. Is it possible to do this?
Thank you
Beppe
|
|
|
Attachment 1: fig1.png
|
|
Attachment 2: fig2.png
|
|
67479
|
Fri Apr 26 18:39:11 2013 |
| Gian Henriques | gianlhsdm@gmail.com | Info | Windows | 292-2 | Blockying user access | How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc.
I want know too, how can I erase configuration of SMTP? I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host. |
67496
|
Wed May 8 19:17:09 2013 |
| Gian Henriques | gianlhsdm@gmail.com | Info | Windows | 292-2 | Re: Blockying user access |
Garret Delaronde wrote: |
Gian Henriques wrote: |
How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc.
I want know too, how can I erase configuration of SMTP? I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host.
|
Hello, you can use the "Deny" flag in the config file for each logbook.
Deny <function> = <user>
Example: Deny Edit = Gian
simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.
Hope that helps.
Elog Syntax guide is helpful for this stuff too.
|
Thanks for help. It work's.
But I want to know if I can block a logbook from a user. For example I have a logbook named "Store". I want only users of the vendors have access to this log. How can I do it?
I didn't find this in manual. |
67497
|
Wed May 8 23:15:34 2013 |
| Gian Henriques | gianlhsdm@gmail.com | Info | Windows | 292-2 | Re: Blockying user access |
Gian Henriques wrote: |
Garret Delaronde wrote: |
Gian Henriques wrote: |
How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc.
I want know too, how can I erase configuration of SMTP? I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host.
|
Hello, you can use the "Deny" flag in the config file for each logbook.
Deny <function> = <user>
Example: Deny Edit = Gian
simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.
Hope that helps.
Elog Syntax guide is helpful for this stuff too.
|
Thanks for help. It work's.
But I want to know if I can block a logbook from a user. For example I have a logbook named "Store". I want only users of the vendors have access to this log. How can I do it?
I didn't find this in manual.
|
The only way I find for this trouble is using the "Login user". But we have something best? |
|