Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 129 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 128, 129, 130 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  1378   Fri Aug 5 02:14:22 2005 Reply Carl Shireycarl.shirey@pw.utc.comQuestionLinux2.6Re: Login twice

Stefan Ritt wrote:

Carl Shirey wrote:
Yes Here is a copy of the elog.cfg.


I tried with your config file and it worked fine. So can you tell me:

  • At what URL do you access your logbook? Do you just type http://localhost:8080 or anything else
  • Do you use any proxy or stunnel?
  • What is the URL in your browser showing on the first and second login?

You might want to consider to put a 
URL = http://<your host>:8080/
into your config file.


Thanks
Your questions that you ask me help me out.
What I was doing was typing in the URL was http://pdls:8080 and it took me the pass down log. When I went to login into Elog took me back to the log but the URL read http://pdls.pwfl.com:8080 so when I log in the second time I was to be the edit mode. So I guess I should have typing in the URL http://pdls.pwfl.com:8080.

Thanks again for your help
  1384   Fri Aug 5 11:18:08 2005 Reply Heiko Scheith.scheit@mpi-hd.mpg.deQuestionLinux2.6.0b3Re: Email subject garbaged when set?

Stefan Ritt wrote:

Chris Green wrote:
The email I get has:

Subject:
=?ISO-8859-1?B?W0Jvb05FLUVMT0ddIE5ldyBzdWJtaXNzaW9uIHRvIENoYXJnZWQgQ3Vyc
mVudCBQaSBQbHVzIGZyb20gQ2hyaXMgR3JlZW4=?=

... which isn't particularly illuminating.


This is the BASE64 encoding of the subject. It was discussed here and I implemented it according to RFC2047.


Well not quite. According to the RFC the encoded word must not be longer than 75 characters! Indeed
shorter subjects are displayed by pine, but not longer ones as they do not follow RFC2047.
Below is the quote from the RFC.


Stefan Ritt wrote:

All subjects I receive look fine in Outlook and Thunderbird, but not under Pine, which apparently does not implement the RFC correctly.


Actually pine implements it correctly but not elogd Smile

The relevant text from the RFC
   An 'encoded-word' may not be more than 75 characters long, including
   'charset', 'encoding', 'encoded-text', and delimiters.  If it is
   desirable to encode more text than will fit in an 'encoded-word' of
   75 characters, multiple 'encoded-word's (separated by CRLF SPACE) may
   be used.
  1386   Fri Aug 5 12:37:42 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0b3Re: Email subject garbaged when set?

Heiko Scheit wrote:
Well not quite. According to the RFC the encoded word must not be longer than 75 characters! Indeed shorter subjects are displayed by pine, but not longer ones as they do not follow RFC2047.
Below is the quote from the RFC.


You are right Big grin, thanks for this information, I overlooked it.

Now I split a long subject into separate chunks of encoded words, and my pine is happy. Update in CVS.
  1390   Fri Aug 5 16:17:00 2005 Question Chris Greengreenc@fnal.govQuestionLinux2.6.0b4How does RSS interact with password protection?
Can I have an RSS feed to a protected log book? Does it also require authentication, or does it bypass it? If it bypasses it, how do I disable RSS?

Thanks,
Chris.
  1391   Fri Aug 5 16:48:56 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0b4Re: How does RSS interact with password protection?

Chris Green wrote:
Can I have an RSS feed to a protected log book? Does it also require authentication, or does it bypass it? If it bypasses it, how do I disable RSS?

Thanks,
Chris.


I added this topic to the FAQs at http://midas.psi.ch/elog/faq.html#15
  1394   Wed Aug 10 03:18:05 2005 Question Dinesh Bapatdinesh.bapat@gmail.comQuestionWindows2.6beta3Email notification does not work
I have SMTP server that requires authentication

Whenever a new user 'self registers' to E-log, I get an automated email saying so. Hence, the SMTP setting are correct and working.

However, for any entry made to log, no email notification is generated. error '5.5.4 Invalid Address'

suppress notification checkbox is 'unchecked'

Kindly help.
  1395   Wed Aug 10 10:50:55 2005 Question Bertram Metzbmetz@sbs.comQuestionLinux2.6.0-betaLong lines in printout
Hi,

long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer. Does anybody know a solution for this?

Thanks,
Bertram
  1398   Mon Aug 15 12:54:56 2005 Reply Michael Husbynmichaelh@online.noQuestionLinux2.5.9-2Re: Omitting some fields in e-mail
> 
> > I added the option "Email attributes = <list>" for that. So you can specify
> > 
> > Email attributes = UA, Pri, Status, Oppdragsgiver, EpostTil, Tittel
> > 
> > which also sets the order of the attributes. The cange is in CVS.

Hello Stefan,

Tested the 2.6.0-beta4, and it sort of works. config parameter:
Email attributes = Tittel,Status

gives the mail:

Logbook             : work
Tittel              : Test
Status              : Åpen

Logbook URL         : http://xxxxxxxxxxxxxxxx/work/904

---

Is there a way to remove Logbook field (and perhaps Logbook URL if I want?)

Best regards
Michael
Goto page Previous  1, 2, 3 ... 128, 129, 130 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6