Hi all Still battling with the basics.
Do my posts appear with =20 line ends (can't remember if these represent CR or LF)? Apparently they do for some list readers.
I am using Kmail 1.2 (KDE 2.1.1, mandrake 8.0).
A general question: what is the recommended char set to use?
And a KDE question - char sets seem to be set both under Settings>Configuration>Composer>Default Charset (main window) and under Options>Set Encoding in the composer window. How do these settings inter-relate?
Finally, I have just noticed that word-wrap was set to 78. I have reset this to 68 and would appreciate any comments about whether this has improved things in any way.
cheers Syd
On Friday 12 October 2001 2:32 am, Syd Hancock wrote:
Hi all Still battling with the basics.
Do my posts appear with =20 line ends (can't remember if these represent CR or LF)? Apparently they do for some list readers.
I am using Kmail 1.2 (KDE 2.1.1, mandrake 8.0).
A general question: what is the recommended char set to use?
And a KDE question - char sets seem to be set both under Settings>Configuration>Composer>Default Charset (main window) and under Options>Set Encoding in the composer window. How do these settings inter-relate?
Finally, I have just noticed that word-wrap was set to 78. I have reset this to 68 and would appreciate any comments about whether this has improved things in any way.
cheers Syd
No =20 line ends here (using kmail 1.3.1 under kde 2.2.1). Wrap at 68 is also okay.
Cheers, BJ
Is kmail stable and robust enough to use? The last time I tried it was very buggy and often duplicated all the emails in the folder you where viewing, either that or deleted files without warning.
that critisim aside it did have a lovely GUI, and one of the few email clients I have seen that had good treading support. At the moment I use XFMail as it is has never lost or duplicated emails with out being told to do so. It is but ugly though. I also use pine to compose emails on the terminal and sometimes even mail
Regards
Owen
On 11-Oct-01 John Woodard wrote:
On Friday 12 October 2001 2:32 am, Syd Hancock wrote:
Hi all Still battling with the basics.
Do my posts appear with =20 line ends (can't remember if these represent CR or LF)? Apparently they do for some list readers.
I am using Kmail 1.2 (KDE 2.1.1, mandrake 8.0).
A general question: what is the recommended char set to use?
And a KDE question - char sets seem to be set both under Settings>Configuration>Composer>Default Charset (main window) and under Options>Set Encoding in the composer window. How do these settings inter-relate?
Finally, I have just noticed that word-wrap was set to 78. I have reset this to 68 and would appreciate any comments about whether this has improved things in any way.
cheers Syd
No =20 line ends here (using kmail 1.3.1 under kde 2.2.1). Wrap at 68 is also okay.
Cheers, BJ
main@lists.alug.org.uk http://www.anglian.lug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
Date: 11-Oct-01 Time: 23:33:01
Owen,
I've been using Kmail 1.2 for a few weeks and have had no problems so far. Having said that, I have not built up a large message base or long folder list. It might be more unstable with more to keep track of. Or maybe it has simply been improved?
Syd
On Thursday 11 October 2001 18:37, oms101@freeuk.com wrote:
Is kmail stable and robust enough to use? The last time I tried it was very buggy and often duplicated all the emails in the folder you where viewing, either that or deleted files without warning.
On Fri, 12 Oct 2001 02:32:18 Syd Hancock wrote:
Hi all Still battling with the basics.
Do my posts appear with =20 line ends (can't remember if these represent CR or LF)? Apparently they do for some list readers.
Neither - =20 actually stands for a space character in the encoding scheme called quoted-printable and is normally seen when a paragraph has been wrapped automatically my the mail software.
The way these get introduced is like this:
Take a paragraph with spaces between the words and then insert newline characters to word wrap at a specified width. If you insert the newline characters rather than replacing one of the spaces with a newline then it remains to decide what happens to the space. Normally the newline will be inserted just after the space, so the first line with finish with a space rather than the second line start with one.
Now, when the mail software (MUA to be specific) goes to send the messages it realises that SMTP makes no guarantee to preserve trailing spaces on lines so in order to preserve them the mail software has to encode the message and chooses the quoted-printable encoding in which characters that need protection are converted into a equals sign followed by the two hex digits of the character's code, so =20 represents the character 20 hex (32 decimal) which is space.
When the mail is received the mail reader program should see that the message is encoded and reverse the coding before displaying the message to the user. If this does not happen it can be for a number of reasons:
1. The receiving mail program doesn't understand the MIME header which gives the encoding type or doesn't implement the decoder for quoted printable.
2. The mail sending program failed to include missed the MIME header which gives the encoding type, or got the syntax wrong.
3. A program along the route, whether a simple mail transfer agent (MTA) or a mailing list manager had dropped the header without itself undoing the coding.
The test, then, is to send messages to some test addresses and then read them with a mail reader that can confirn if the header concerned is still there. IIRC the header you are looking for is Content-Transfer-Encoding or some similar name.
As for the line length to begin with, 78 is fine for an original message but gives no scope to indent that message when someone wants to reply to it - 65 to 70 is a better choice.
Steve.
Steve, As always, a clear, detailed and helpful response (in which of course you are not alone).
I will check a few message headers to see what character sets others are using - thanks for the tip.
All: I assume then that my messages display correctly since there has not been a flood of complaints? <g>
Best wishes Syd
-
John Woodard -
oms101＠freeuk.com -
Steve Fosdick -
Syd Hancock