ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1206
|
Tue Jun 21 19:24:58 2005 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | Linux | 2.5.9 | Re: elog crashes when admin tries to register new users |
Quote: |
Thanks for that info. It helped me debugging things. The problem is that the "activation" URL does not contain a logbook if there is a global password file. I have never tried that so of course it crashes 
I tried to fix this and committed the changes to CVS. Can you try with that version? |
Not really, unless you have a fixed 2.5.9 version. Version 2.6 has
way too many new features, which I don't want at the moment. Or is
there a config option to get the old behavior?
I also saw that the format of the email notification has changed. As
I have scripts (bash, akw, procmail) that depend on this format I
would need much more time than I currently have to actually test
everything.
Maybe you should consider supporting two branches, say 'stable' (2.5.9
currently) and 'experimental' (2.6 currently)? For 'stable' only
severe bugs and security issues are fixed and in 'experimental' new
features are introduced. What do you say?
For me the risk of upgrading to 2.6 now seems to high, as many people
depend on the logbook. |
1207
|
Tue Jun 21 19:38:06 2005 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | Linux | 2.5.9 | email flagged as spam |
Heiko Scheit wrote: |
I also saw that the format of the email notification has changed. As
I have scripts (bash, akw, procmail) that depend on this format I
would need much more time than I currently have to actually test
everything. |
By the way, the emails I get from the forum are now all flagged as
spam. SpamAssassin is used and Spam-score header is
X-Spam-Score: 4.875 (****) ADDRESS_IN_SUBJECT, BAYES_00,HTML_40_50,
HTML_IMAGE_ONLY_24, HTML_MESSAGE, MIME_HEADER_CTYPE_ONLY,
MIME_HTML_ONLY, MSGID_FROM_MTA_HEADER, MSGID_FROM_MTA_ID,
NO_REAL_NAME, SPF_FAIL, SPF_HELO_PASS, TO_MALFORMED
Maybe you can see what the problem is. |
1259
|
Mon Jul 11 19:04:38 2005 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug fix | Linux | 2.5.9 | elog utility for submission used wrong 'Host:' in POST header | The 'elog' utility for commandline submission used wrong 'Host:' in POST header.
The host listed after 'Host:' should be the host where the server runs, not the
localhost (see patch below).
$ diff -u elog.c_20050711 elog.c
--- elog.c_20050711 Mon Jul 11 18:54:20 2005
+++ elog.c Mon Jul 11 18:55:31 2005
@@ -421,7 +421,7 @@
sprintf(request + strlen(request), "%s/%d?cmd=download", experiment, message_id);
strcat(request, " HTTP/1.0\r\n");
- sprintf(request + strlen(request), "Host: %s\r\n", host_name);
+ sprintf(request + strlen(request), "Host: %s\r\n", host);
sprintf(request + strlen(request), "User-Agent: ELOG\r\n");
first = 1;
@@ -872,7 +872,7 @@
strcat(request, " HTTP/1.0\r\n");
sprintf(request + strlen(request), "Content-Type: multipart/form-data; boundary=%s\r\n", boundary);
- sprintf(request + strlen(request), "Host: %s\r\n", host_name);
+ sprintf(request + strlen(request), "Host: %s\r\n", host);
sprintf(request + strlen(request), "User-Agent: ELOG\r\n");
sprintf(request + strlen(request), "Content-Length: %d\r\n", content_length); |
1384
|
Fri Aug 5 11:18:08 2005 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Question | Linux | 2.6.0b3 | Re: 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 
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.
|
1399
|
Fri Aug 26 13:08:10 2005 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Request | | | something for the wishlist: 'Recent Changes' | Something for the wishlist:
A 'Recent Changes'-link (option) that lists entries that were changed
recently, where 'recent' can be changed from 1,2,3...(some maximum)
days. |
69341
|
Fri Apr 9 16:48:54 2021 |
| Gys Wuyts | gys.wuyts@gmail.com | Question | Windows | 3.1.4 (latest) | auto pre-fill fields issue | Hello,
what are the pre-requisites to automatically fill the Author and Author Email fields. The documented method:
Subst Author = $long_name from $remote_host
Subst Email = $user_email
in the elogd.cfg file does not seem to work.
(I see it works here on this platform)
Tnks
G |
69343
|
Sat Apr 10 20:58:35 2021 |
| Gys Wuyts | gys.wuyts@gmail.com | Question | Windows | 3.1.4 (latest) | Re: auto pre-fill fields issue | Thank you but that is already in place. I have the same issue on both Windows 10 and Windows Server 2016 and 2019.
tnks
g
Stefan Ritt wrote: |
You need user-level access control, using
Password file = ...
Stefan
Gys Wuyts wrote: |
Hello,
what are the pre-requisites to automatically fill the Author and Author Email fields. The documented method:
Subst Author = $long_name from $remote_host
Subst Email = $user_email
in the elogd.cfg file does not seem to work.
(I see it works here on this platform)
Tnks
G
|
|
|
69345
|
Mon Apr 12 13:32:53 2021 |
| Gys Wuyts | gys.wuyts@gmail.com | Question | Windows | 3.1.4 (latest) | Re: auto pre-fill fields issue | [global]
port = 8080
ssl = 0
Password file = passwords.txt
Admin user = user1
SMTP host = smtp. mail.com
SMTP port = 25
SMTP username = user1@mail.com
SMTP Password = GIwbx7UbmkWs5J0P8lVztX7Anje0/21BU/Tmk0aPm.
Logfile = ELog_log.txt
Logging level = 3
[Server]
Logbook dir = Server
Theme = default
Comment = Server Change Log
Attributes = Author, Email, Type, Category, Subject
Subst Author = $long_name from $remote_host
Subst Email = $user_email
Options Type = SRV 1, SRV 2, SRV Sup, BMS content, BMS setpoints, BMS new
Options Category = Config, User, Access, Connection, Change, New, Delete
Extendable Options =
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Andreas Luedeke wrote: |
If you would post a minimal config file where the problem occurs, then we could look what the problem is.
Gys Wuyts wrote: |
Thank you but that is already in place. I have the same issue on both Windows 10 and Windows Server 2016 and 2019.
tnks
g
Stefan Ritt wrote: |
You need user-level access control, using
Password file = ...
Stefan
Gys Wuyts wrote: |
Hello,
what are the pre-requisites to automatically fill the Author and Author Email fields. The documented method:
Subst Author = $long_name from $remote_host
Subst Email = $user_email
in the elogd.cfg file does not seem to work.
(I see it works here on this platform)
Tnks
G
|
|
|
|
|
|