Bug 49871

Summary: why not have an IMAP precommand?
Product: [Frameworks and Libraries] Akonadi Reporter: Michael Lachmann <dirk>
Component: IMAP resourceAssignee: Christian Mollekopf <chrigi_1>
Status: CONFIRMED ---    
Severity: wishlist CC: bugs.kde.org, luigi.toscano, montel, pancho.s, pim-bugs-null, rjwysocki, vkrause
Priority: NOR    
Version First Reported In: GIT (master)   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Michael Lachmann 2002-10-29 13:15:59 UTC 
Version:            (using KDE KDE 3.0.8)
Installed from:    Unlisted Binary Package
OS:          LinuxLinux

Why not have an IMAP precommand? One can specify a precommand for POP but not for IMAP.
I would like this, because I am connecting to a server that only allows plain-text login. To overcome this problem, I ssh and forward the IMAP port to my local machine.

The precommand should be executed every time the IMAP channel is re-opened.
Comment 1 Ferdinand Gassauer 2003-09-10 05:56:53 UTC 
I vote for this one too. 
ferdinand
Comment 2 Diego Cerdan Puyol 2004-11-07 18:24:42 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 3 Myriam Schweingruber 2012-08-18 08:49:48 UTC 
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented.
Thank you for your understanding.
Comment 4 Luigi Toscano 2012-08-19 01:07:56 UTC 
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.
Comment 5 Bernd Oliver Sünderhauf 2012-11-24 07:51:54 UTC 
IMAP precommand still not avaolable in kmail2. Component "general".
Comment 6 Luigi Toscano 2012-11-24 16:21:56 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 7 Kevin Ottens 2013-11-16 07:29:33 UTC 
The IMAP resource has a new maintainer, reassigning to him.
Comment 8 Daniel Vrátil 2018-08-27 22:34:17 UTC 
*** Bug 314945 has been marked as a duplicate of this bug. ***