| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1375
|
Thu Aug 4 22:59:12 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0b3 | Re: Email subject garbaged when set? |
| 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. All subjects I receive look fine in Outlook and Thunderbird, but not under Pine, which apparently does not implement the RFC correctly. One could of course put a switch into elog to encode it or not. But as soon as you want to send some non-ASCII characters (like the Norwegian as described in the thread mentioned above) you have a problem. Maybe you can configure your email client correctly to interprete the encoded subject? |
|
1376
|
Fri Aug 5 01:13:13 2005 |
| Chris Green | greenc@fnal.gov | 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. All subjects I receive look fine in Outlook and Thunderbird, but not under Pine, which apparently does not implement the RFC correctly. One could of course put a switch into elog to encode it or not. But as soon as you want to send some non-ASCII characters (like the Norwegian as described in the thread mentioned above) you have a problem. Maybe you can configure your email client correctly to interprete the encoded subject? |
Apparently the pine people think they're implementing it correctly. Indeed the default subject, "[ISO-8859-1] New ELOG entry" appears just fine. The one for membership confirmation, and anything set in Use Email Subject, however, is borked as above. Maybe the pine bug is something that can be worked around with something simple (like spaces after the ISO spec, or something? Some things work just fine, as I said.
Thanks,
Chris. |
|
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.
|
|
1386
|
Fri Aug 5 12:37:42 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0b3 | Re: 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  , 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 |
 | Chris Green | greenc@fnal.gov | Question | Linux | 2.6.0b4 | How 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 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0b4 | Re: 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 |
|
1477
|
Mon Oct 24 12:00:51 2005 |
 | mark james | mark_james@inmarsat.com | Question | Windows | 2.6.0b5 | Quicklink does not work for one field | I am not so bold as to log this as a bug but one of my Quicklink fields just do not work. It is the "Spacecraft" field. When I select any 'Spacecraft' quicklink, the no. of records stays exactly the same (i.e. no. in full recordset). If I select F1, then I see F1 highlight in yellow in the string "4F1". But strangely the "F1" entries are not highlight. Very strange.
My config file below (admin username removed).
=========================================================================
Theme = default
Comment = Inmarsat SCD Analyst Log book
Attributes = Record Date, Spacecraft, Author, SubSystem, Title
MOptions Spacecraft = F1, F2, F3, F4, G1, G2, G3, G4, G5, 4F1, 4F2, 4F3
Options Author = John MacDougall, John Turton, Joe Fowler, Mark Davidson, Mark James
Options SubSystem = Thermal, Propulsion, Power, AOCS/ADCS, Payload, TTC, Other/None
Required Attributes = Record Date, Spacecraft, Author, SubSystem, Title
Type Record Date = datetime
Time format = %A, %d %B, %Y, %H:%M
Date format = %A, %d %B, %Y
Filter Menu text = scripts/calendar_filter/calendar_filter.html
Preset Record date = $date, $time
List Display = Record date, Spacecraft, Author, SubSystem, Title
Start page = ?rsort=Record date
Entries per page = 100
Message Height = 15
Page Title = ELOG - $title
Reverse sort = 1
Quick filter = Date, Spacecraft, SubSystem, Author
message comment = "Please make your log entry in the box BELOW."
Attachment Comment = "Please upload your attachment in the box BELOW."
Menu commands = List, New, Edit, Delete, Reply, Find, Help, Download, Last Day, Copy to
Password file = pwfile
Self register = 0
Subst Author = $long_name from $remote_host
Subst Email = $user_email
Suppress default = 1
Use Lock = 1
RSS Title = $Title, by $author on $Record Date
Guest menu commands = Find, Last 10, Login, Help
Guest Find Menu commands = Find, Last 10, Login, Help
=================================================================== |
|
1600
|
Wed Jan 18 12:15:17 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | 2.6.0b5 | Re: Quicklink does not work for one field |
| mark james wrote: | | I am not so bold as to log this as a bug but one of my Quicklink fields just do not work. |
Sorry my late reply, but now I have fixed this problem. The update is under SVN and will be contained in the next release. |
|