Version:           1.9.7 (using KDE 3.5.7, Mandriva Linux release 2007.1 (Official) for x86_64)
Compiler:          Target: x86_64-mandriva-linux-gnu
OS:                Linux (x86_64) release 2.6.22-3mde

Time to time kmail doesnt display some new messages, it shows the subject, date and the sender but nothing in the body message and even after clicking in the message continues appearing as unread.

To be able to read/see that message, i have to move it to another folder, then when clicking in the message it displays message body.

Im pasting the source code of one of that messages:


Delivered-To: foo@foo.com
Received: by 10.114.193.9 with SMTP id q9cs446531waf;
        Thu, 2 Aug 2007 06:50:26 -0700 (PDT)
Received: by 10.90.33.16 with SMTP id g16mr1778237agg.1186062623595;
        Thu, 02 Aug 2007 06:50:23 -0700 (PDT)
Return-Path: <madwifi-devel-bounces@lists.sourceforge.net>
Received: from lists-outbound.sourceforge.net (lists-outbound.sourceforge.net [66.35.250.225])
        by mx.google.com with ESMTP id 8si7572442nzn.2007.08.02.06.50.09;
        Thu, 02 Aug 2007 06:50:23 -0700 (PDT)
Received-SPF: pass (google.com: domain of madwifi-devel-bounces@lists.sourceforge.net designates 66.35.250.225 as permitted sender)
Received: from sc8-sf-list1-new.sourceforge.net (sc8-sf-list1-new-b.sourceforge.net [10.3.1.93])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 4585A127D3; Thu,  2 Aug 2007 06:50:08 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)
	id 1IGasd-0006jh-96
	for madwifi-devel@lists.sourceforge.net; Thu, 02 Aug 2007 06:38:20 -0700
Received: from web35314.mail.mud.yahoo.com ([66.163.179.108])
	by mail.sourceforge.net with smtp (Exim 4.44) id 1IGasZ-0002zp-Jy
	for madwifi-devel@lists.sourceforge.net; Thu, 02 Aug 2007 06:38:17 -0700
Received: (qmail 84118 invoked by uid 60001); 2 Aug 2007 13:38:09 -0000
X-YMail-OSG: gmBTWDUVM1mnLpxlwQOS_Jrtc6qHGKsVABCsTk7zSNgw8uKV2XYDeGenHEPl8Bm014wJDmDncJQubROShDN0x9cFaP_Z63lhVhj2eJi.XbNq_U9Wh4xe1v78gZmsFQ--
Received: from [124.30.157.2] by web35314.mail.mud.yahoo.com via HTTP;
	Thu, 02 Aug 2007 06:38:08 PDT
Date: Thu, 2 Aug 2007 06:38:08 -0700 (PDT)
From: jagadish nadimpalli <jagadish_nadimpalli@yahoo.com>
To: madwifi-devel@lists.sourceforge.net
MIME-Version: 1.0
Message-ID: <982091.57697.qm@web35314.mail.mud.yahoo.com>
X-Spam-Score: 2.7 (++)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	Report problems to
	http://sf.net/tracker/?func=add&group_id=1&atid=200001
	2.2 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received'
	headers
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.5 HTML_20_30             BODY: Message is 20% to 30% HTML
Subject: [Madwifi-devel] Is this correct "channel switching logic" in
	madwifi-0.9.3?
X-BeenThere: madwifi-devel@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: <madwifi-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/madwifi-devel>, 
	<mailto:madwifi-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=madwifi-devel>
List-Post: <mailto:madwifi-devel@lists.sourceforge.net>
List-Help: <mailto:madwifi-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/madwifi-devel>, 
	<mailto:madwifi-devel-request@lists.sourceforge.net?subject=subscribe>
Content-Type: multipart/mixed;
  boundary="===============1670617638=="
Sender: madwifi-devel-bounces@lists.sourceforge.net
Errors-To: madwifi-devel-bounces@lists.sourceforge.net
Status: RO
X-Status: RC
X-KMail-EncryptionState: N
X-KMail-SignatureState: N
X-KMail-MDN-Sent:  

--===============1670617638==
Content-Type: multipart/alternative; boundary="0-1279038925-1186061888=:57697"
Content-Transfer-Encoding: 8bit

--0-1279038925-1186061888=:57697
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,

According to my understanding, min dwell time and max dwell time implementation in madwifi source code (version 0.9.3) are,

During scanning, after sending probe request on a channel,
 
1) If there is no response on that channel, wireless station waits upto max dwell time and switches to the next channel.

2) If station gets response before min dwell time and don't get any responses between min dwell time and max dwell time, station switches to the next channel after max dwell time.

3) If station gets response after min dwell time,  it switches to next channel immediately. It does not wait upto max dwell time.

Is this the correct behavior? What is the reason for chosing this logic.

thanks,
Jagadish

       
---------------------------------
Got a little couch potato? 
Check out fun summer activities for kids.
--0-1279038925-1186061888=:57697
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,<br><br>According to my understanding, min dwell time and max dwell time implementation in madwifi source code (version 0.9.3) are,<br><br>During scanning, after sending probe request on a channel,<br>&nbsp;<br>1) If there is no response on that channel, wireless station waits upto max dwell time and switches to the next channel.<br><br>2) If station gets response before min dwell time and don't get any responses between min dwell time and max dwell time, station switches to the next channel after max dwell time.<br><br>3) If station gets response after min dwell time,&nbsp; it switches to next channel immediately. It does not wait upto max dwell time.<br><br>Is this the correct behavior? What is the reason for chosing this logic.<br><br>thanks,<br>Jagadish<br><p>&#32;
      <hr size=1>Got a little couch potato? <br>
Check out fun <a href="http://us.rd.yahoo.com/evt=48248/*http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz">summer activities for kids.</a>
--0-1279038925-1186061888=:57697--


--===============1670617638==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
--===============1670617638==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Madwifi-devel mailing list
Madwifi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/madwifi-devel

--===============1670617638==--