[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 122818] New: IMAP BAD responses not properly handled
From:       Casey Allen Shobe <cshobe () osss ! net>
Date:       2006-02-27 23:10:58
Message-ID: 20060228001055.122818.cshobe () osss ! net
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=122818         
           Summary: IMAP BAD responses not properly handled
           Product: kmail
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kmail-devel kde org
        ReportedBy: cshobe osss net


Version:            (using KDE KDE 3.5.1)
Installed from:    Compiled From Sources
Compiler:          gcc 3.4.4 
OS:                Linux

3 CAPABILITY 
* CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE \
CHILDREN NAMESPACE LOGIN-REFERRALS STARTTLS AUTH=PLAIN AUTH=DIGEST-MD5 AUTH=GSSAPI  3 \
OK Capability completed.  4 NAMESPACE 
4 BAD Error in IMAP command received by server. 
5 LIST "" "" 
5 BAD Error in IMAP command received by server. 

In this example, we see that kmail receives a bad response to it's namespace inquiry \
(which means that the IMAP protocol got violated).  "No matter!", it decides, and \
keeps on going.  Worst, after blatently ignoring the errors received, it then lies to \
the user, saying something clever like "The server imap.sk8rland.com replied: \
SASL(-4): no mechanism available: No worthy mechs found.  Blame them not me!!  OMG!" \
_______________________________________________ KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel


[prev in list] [next in list] [prev in thread] [next in thread]