Bug 192897

Summary: JJ: Message shown when enabling POP3 pipelining refers to nonexistent feature of kmail
Product: [Unmaintained] kmail Reporter: Szczepan Hołyszewski <rulatir>
Component: pop3Assignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Szczepan Hołyszewski 2009-05-16 17:36:30 UTC 
Version:            (using KDE 4.2.3)
Installed from:    Unspecified Linux

When I try to enable POP3 pipelining in a POP3 account configuration, Advanced tab, this message shows:

"Please note that this feature can cause some POP3 servers that do not support pipelining to send corrupted mail;
this is configurable, though, because some servers support pipelining but do not announce their capabilities. To check whether your POP3 server announces pipelining support use the "Check What the Server Supports" button at the bottom of the dialog;
if your server does not announce it, but you want more speed, then you should do some testing first by sending yourself a batch of mail and downloading it."

The message refers to 'the "Check What the Server Supports" button at the bottom of the dialog', but there is no such button. There is a similar button on the Security tab, but it only checks for security features (encryption, secure authentication) and not for POP3 pipelining support.
Comment 1 Thomas McGuire 2009-05-26 15:49:30 UTC 
Why do you think the "Check What The Server Supports" button does not check for pipelining? Actually it does, but your server didn't announce it, therefore you see the message.
You can double-check that by logging the conversation with wireshark. If you don't see "PIPELINING" as a response to the "CAPA" command, then your server doesn't announce it.

The UI has changed indeed, so the string referring to the button is now outdated.
Comment 2 Thomas McGuire 2009-05-26 15:54:36 UTC 
Confirmed as the string is wrong.
Comment 3 Jaime Torres 2009-07-09 09:14:10 UTC 
@Thomas: What is better, to move the button to the first tab or to change the string to reference the botton in the security tab?
Comment 4 Thomas McGuire 2009-07-09 13:05:22 UTC 
I would just change the string
Comment 5 Jaime Torres 2009-07-09 18:58:09 UTC 
SVN commit 993906 by jtamate:

BUG: 192897

Added "at the bottom of the Security tab in this dialog" to the message.

 M  +1 -1      accountdialog.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=993906