Version: 1.9.6 (using KDE KDE 3.5.6) Installed from: SuSE RPMs OS: Linux Cited later [1] is the text area of a typical bounced majordomo message, which needs to be forwarded inline, with a password attached, to have it published on a majordomo mailing list. However, when selecting forward inline, the text area of the new window is empty while the original message appears as an attached file. This happens only with bounced majordomo message. Forwarding inline works nicely with other emails. In KMail 1.9.5, forwarding a bounced majordomo message resulted in having the message attached _and_ inside the text area, so I suppose this new behaviour is the result of some fix. Guido [1] >From xxx@xxx Mon Feb 5 17:54:45 2007 Return-Path: xxx@xxx Delivered-To: xxx@xxx Received: from xxx Received: xxx Received: xxx Content-Type: multipart/mixed; boundary="========GMX8402117069448339004" Date: Mon, 05 Feb 2007 17:54:43 +0100 From: xxx In-Reply-To: xxx Message-ID: xxx MIME-Version: 1.0 References: xxx Subject: Re: xxx To: xxx X-Authenticated: #6381694 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 --========GMX8402117069448339004 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Hallo Guido, [snip] --========GMX8402117069448339004--
Here is further info on the problem I have reported above. It seems that "fwd inline" does work when the bounced majordomo message is part of a thread containing two messages, but not always. You will like the details ;): 1. If not part of a thread, bounced majordomo message doesn't appear inline when forwarded inline. 2. If first message of a thread containig two messages, then bounced majordomo message 2.1 _does_ appear inline only if thread is closed, 2.2 does _not_ appear inline if thread is open. Then, however, the second message appears inline when forwarded inline. 3. If first message of a thread containing several messages, then bounced majordomo message does always appear inline.
Sorry, I need to correct a detail of my previous posting here. It applies to case 2.1 only: 2. If first message of a thread containig two messages, then bounced majordomo message 2.1 _does_ appear inline - together with the second message(!) - only if thread is closed, 2.2 does _not_ appear inline if thread is open. Then, however, the second message appears inline when forwarded inline. Could this be related to some faulty behaviour of multiparted forwarding of a thread? It looks as if case 2.1 is an "inline" version of the option "forward as mime catalogue" (in my German GUI: Weiterleiten als MIME Katalog)
See also bug 146921, that could be the same.
Probably the same. Considering fixed as long as no one confirms the opposite.