[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 --- Comment #55 from Vincent Fortier <th0...@gmail.com> --- Tried it, would have been to simple :) I removed/recreated the kmail config and also tried the following https://docs.kde.org/trunk5/en/kdepim/kmail/clean-start-after-a-failed-migration.html Also tried streaming notifications vs pool every x.y mins. Still no folders and no luck sadly. Starting kmail from a console gets the following output: $ kmail "KMail Kernel ETM" () "" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" "/subscriber/kmail2_17230_Rt0qZi" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" "/subscriber/kmail2_17230_6rPTQz" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" "/subscriber/kmail2_17230_G17QQ6" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" "/subscriber/kmail2_17230_BzULk8" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" "/subscriber/kmail2_17230_dMPgUN" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" "/subscriber/kmail2_17230_VBMxvj" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" "/subscriber/kmail2_17230_ZB5RQu" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" "/subscriber/kmail2_17230_4JGo60" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" this does not work on a KActionCollection containing actions! done Connected to "Akonadi" , using protocol version 52 Server says: "Not Really IMAP server" Connected to "Akonadi" , using protocol version 52 Server says: "Not Really IMAP server" org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Connected to "Akonadi" , using protocol version 52 Server says: "Not Really IMAP server" Connected to "Akonadi" , using protocol version 52 Server says: "Not Really IMAP server" Connected to "Akonadi" , using protocol version 52 Server says: "Not Really IMAP server" Connected to "Akonadi" , using protocol version 52 Server says: "Not Really IMAP server" org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() Connected to "Akonadi" , using protocol version 52 Server says: "Not Really IMAP server" org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() Connected to "Akonadi" , using protocol version 52 Server says: "Not Really IMAP server" org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() Connected to "Akonadi" , using protocol version 52 Server says: "Not Really IMAP server" Connected to "Akonadi" , using protocol version 52 Server says: "Not Really IMAP server" "/subscriber/kmail2_17230_NLIKyV" connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket" Could not resolve property : linearGradient4538 Could not resolve property : linearGradient4588 Could not resolve property : linearGradient4554 Could not resolve property : linearGradient4572 Could not resolve property : linearGradient4532 Could not resolve property : linearGradient4582 Could not resolve property : linearGradient4566 Could not resolve property : linearGradient4548 Could not resolve property : linearGradient4532 Could not resolve property : linearGradient4582 Could not resolve property : linearGradient4566 Could not resolve property : linearGradient4548 Could not resolve property : linearGradient4532 Could not resolve property : linearGradient4582 Could not resolve property : linearGradient4566 Could not resolve property : linearGradient4548 Could not resolve property : linearGradient4538 Could not resolve property : linearGradient4588 Could not resolve property : linearGradient4554 Could not resolve property : linearGradient4572 Could not resolve property : linearGradient4532 Could not resolve property : linearGradient4582 Could not resolve property : linearGradient4566 Could not resolve property : linearGradient4548 Could not resolve property : linearGradient4532 Could not resolve property : linearGradient4582 Could not resolve property : linearGradient4566 Could not resolve property : linearGradient4548 Could not resolve property : linearGradient4532 Could not resolve property : linearGradient4582 Could not resolve property : linearGradient4566 Could not resolve property : linearGradient4548 Could not resolve property : linearGradient4538 Could not resolve property : linearGradient4588 Could not resolve property : linearGradient4554 Could not resolve property : lin
[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 --- Comment #53 from Vincent Fortier <th0...@gmail.com> --- (In reply to Krzysztof Nowicki from comment #52) > (In reply to Vincent Fortier from comment #51) > > Now, the real thing! A few comments: > > - The domain box should be optional and thus perhaps a click on/off be > > appropriate > I agree that some sites do not require it, but nevertheless I think that > hiding it behind some checkbox would be more confusing. Agreed. Perhaps adding a "(optionnal)" tool-tip message? > > - I think same should be true for the username: in my case there are no > > username except my email user... again, by default it may be more > > appropriate to auto-fill that box with the name section of the email address > > with a on/off to edit manually? > Similar as above. Same is true, a tooltip or auto-complete with what you username maybe based on your email would be nice. > > - server auto-discovery failed to work... In my case I use an internal > > auto-discovery URL that I have to specify manually. My understanding of the > > interface is that it tries to auto-discover "online" but I cannot assign an > > auto-discovery URL manually? > Server autodiscovery relies on resolving an address based on your e-mail > domain. Sometimes this won't as the autodiscovery service is not available > (this is the case with my corporate account). In such case you can uncheck > the "Server Autodiscovery" checkbox and enter the EWS URL manually. It > should be something like: https://yourdomain.com/EWS/Exchange.asmx Under evolution I manually entered my "autodiscover" URL then hit get URL and it fills up the URL OAB field automatically. In this case I manually entered the EWS URL and hit Try connect.. Which i found simpler to evolution as the user don't really care about the underlying UUID type OAB URL. Although a connection successful may be appropriate? It ended up not adding any folder within kmail for the new account (maybie a bug related to kmail and totally unrelated to your new feature, will further investigate?). Although from the subscription tab I can select my various folders and as well, it says "ready" under it in the reception tab. It's sad that it blocks over tiny details as I'd rather provide you with comments on the real stuff :) I'll reinitiate my kmail config as it may have older configs stuck? and give it another try. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 --- Comment #51 from Vincent Fortier <th0...@gmail.com> --- I gave it a try. I had not played with KDE since around a year so I had to play a little with my installation in order to get things working as is seems there is a bug blocking plasma to startup properly with 16.04. For other who might be interested (not entirely related to this thread...): sudo add-apt-repository -y ppa:kubuntu-ppa/staging-misc sudo apt-get update sudo apt-get -y install plasma-desktop kde-l10n-fr Then getting your package installed: wget https://github.com/KrissN/akonadi-ews/releases/download/v0.8.0/akonadi-ews_0.8.0-1_amd64.deb sudo dpkg -i akonadi-ews_0.8.0-1_amd64.deb sudo apt-get install -f Then finally kontact ready: sudo apt-get update sudo apt-get -y install kontact kleopatra Once all set I was able to login into KDE/plasma and launch kontact and get things going. Now, the real thing! A few comments: - The domain box should be optional and thus perhaps a click on/off be appropriate - I think same should be true for the username: in my case there are no username except my email user... again, by default it may be more appropriate to auto-fill that box with the name section of the email address with a on/off to edit manually? - server auto-discovery failed to work... In my case I use an internal auto-discovery URL that I have to specify manually. My understanding of the interface is that it tries to auto-discover "online" but I cannot assign an auto-discovery URL manually? End-result: sadly as-is I wasn't able to get access to my inbox through EWS. Lastly, hopefully at some point full support for calendar along with contacts & task will be made available! Thnx for finally trying to close this gap within the KDE suite, it is really much appreciated and I look forward at trying later versions! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 --- Comment #49 from Vincent Fortier <th0...@gmail.com> --- I will gladly do as soon as there is a PPA or (other relatively simple mean for trying it) and provide feedbacks! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 --- Comment #43 from Vincent Fortier th0...@gmail.com --- Believe it or not, today marks the 10th anniversary of this bug entry! Happy birthday! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 227672] MAPI support in kmail
https://bugs.kde.org/show_bug.cgi?id=227672 Vincent Fortier th0...@gmail.com changed: What|Removed |Added CC||th0...@gmail.com --- Comment #10 from Vincent Fortier th0...@gmail.com --- Bump for 2013 with linkage to https://bugs.kde.org/show_bug.cgi?id=78629 ;) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 --- Comment #42 from Vincent Fortier th0...@gmail.com --- Bump for 2013 with linkage to https://bugs.kde.org/show_bug.cgi?id=227672 ;) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 --- Comment #38 from Vincent Fortier th0ma7 gmail com 2011-12-01 12:06:17 --- As bug initiator, I will re-explain: Built-in exchange support means: - Most probably using native communication protocol (no imap or whatever) - kmail2 was not existing at the time but it does also affect it indeed - that would also mean the other components would also follow: address book + calendar + etc to be able to communicate with exchange server using native communication protocol Is that sufficient? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 78629] MS Exchange mail support
--- 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=78629 th0ma7 gmail com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|LATER | --- Additional Comments From th0ma7 gmail com 2008-05-08 11:42 --- Now that Microsoft specs are opening and since the code is available elsewhere (evolution) since 4 years I sincerely think this bug should be reopened. This is by far my greatest whish for KDE, being more connected with what we are stuck with in many offices. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
