| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
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. |
|
1311
|
Mon Jul 25 19:24:47 2005 |
 | Chris Green | greenc@fnal.gov | Question | Linux | 2.6.0b | Literal comma in elogd.conf entries where "," is an item separator? | Hi,
Could you tell me if there is a way to escape characters in elogd.conf? Particularly, I want to have a drop-down "Keyword" attribute where one of the options is "Spelling, grammar and typos.". This invariably gets split into "Spelling" and "grammar and typos". I've tried "\,", ",,", "%," and "%27", to no avail.
Can I get there from here, or do I have to go someplace else?
Thanks,
Chris. |
|
1313
|
Mon Jul 25 20:25:26 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0b | Re: Literal comma in elogd.conf entries where "," is an item separator? |
| Chris Green wrote: | | Could you tell me if there is a way to escape characters in elogd.conf? Particularly, I want to have a drop-down "Keyword" attribute where one of the options is "Spelling, grammar and typos.". This invariably gets split into "Spelling" and "grammar and typos". I've tried "\,", ",,", "%," and "%27", to no avail. |
Just put it in quotations, like
Options Keyword = "Spelling, grammar and typos", Other
that will do the job. |
|
1315
|
Mon Jul 25 21:41:00 2005 |
| Chris Green | greenc@fnal.gov | Question | Linux | 2.6.0b | Re: Literal comma in elogd.conf entries where "," is an item separator? | Sorry for being dense. Thanks for this,
Chris. |
|
1318
|
Mon Jul 25 23:39:16 2005 |
 | Chris Green | greenc@fnal.gov | Question | Linux | 2.6.0b | Can't set Author attribute properly in reply? | Hi,
I have two problems:
1) With the configuration below, I can't set the Author attribute to be the author of the reply. As written, it gives the Author field as blank. If the Remove on Reply line is removed, it is set to the parent's author. What am I doing wrong?
2) With the Page Title line set as shown, $logbook gets expanded as "Charged+Current+Pi+Plus". If the line is left blank, the correct "Charged Current Pi Plus" gets put in the title line.
Thanks for any help,
Chris.
[global]
Top Group MiniBooNE Papers = Charged Current Pi Plus, Neutral Current Coherent Pions
<snip>
[global MiniBooNE Papers]
Password file = papers.pwd
Self register = 3
Menu commands = List, New, Last day, Download, Reply, Duplicate, Find, Config, Delete, Help
Admin user = admin1, admin2
Allow Delete = admin1, admin2
Restrict edit time = 0
Attributes = Author, Subject, Keywords
MOptions Keywords = Structure, Physics, "Spelling, grammar and typos.", Plots
Required Attributes = Subject, Keywords
Subst on reply subject = Re: $subject
Thread display = $subject, posted by $author on $Entry
Remove on reply = Author
Preset Author = $long_name
Locked Attributes = Author
Omit Email To = 1
Reverse sort = 1
Page Title = MiniBooNE papers comments page: $logbook
[Charged Current Pi Plus]
Comment = Charged current pi plus paper.
Theme = default
[Neutral Current Coherent Pions] |
|
1321
|
Tue Jul 26 10:00:34 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Question | Linux | 2.6.0b | Re: Can't set Author attribute properly in reply? |
| Chris Green wrote: | Hi,
I have two problems:
1) With the configuration below, I can't set the Author attribute to be the author of the reply. As written, it gives the Author field as blank. If the Remove on Reply line is removed, it is set to the parent's author. What am I doing wrong?
|
Subst on reply Author = $long_name |
|