| Summary: | kmail offline imap disconnects with 2 accounts to same IMAP server | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | AL13N <alien> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | balcaen.john |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kmail | CVE: | |
| Status comment: | |||
| Attachments: | Screenshot of kmail notification error | ||
|
Description
AL13N
2011-08-08 10:05:20 CEST
Created attachment 709 [details] Screenshot of kmail notification error (In reply to comment #0) > I have multiple accounts to the same imap server and i use offline imap so that > i may have the emails when i have no connection to the imap server. > > at start (with check new email at startup) it seems that one of the 2 accounts > does not get checked at all, it disconnects immediately > > later (at 5min check interval) it checks both accounts, one after the other, > but it seems to not do all folders, and it disconnects, it may be always at the > same folder that it disconnects, but that means that about 10 folders are not > being checked at all; even though one of those unchecked folders is in my > favourites. > that means i have to check manually that folder. This part should probably check on the server side i guess, because i used the same setup without problem with kmail 4.4.8 (last time i did it until switching only to dimap). > also with offline imap, you don't get any notification if you type in wrong > password, you just don't get folders, even in the subscribing options you don't > see folders, but just "loading..." This is strange because you're supposed to get a notification windows like « Authentification Failed » that's whay i get here when using a wrong password for my dimap account.(cf screenshot done) But in all case thoses bugs are going to be closed as wontfix or switch to kmail2 by upstream. (In reply to comment #1) > Created attachment 709 [details] > Screenshot of kmail notification error > > (In reply to comment #0) > > I have multiple accounts to the same imap server and i use offline imap so that > > i may have the emails when i have no connection to the imap server. > > > > at start (with check new email at startup) it seems that one of the 2 accounts > > does not get checked at all, it disconnects immediately > > > > later (at 5min check interval) it checks both accounts, one after the other, > > but it seems to not do all folders, and it disconnects, it may be always at the > > same folder that it disconnects, but that means that about 10 folders are not > > being checked at all; even though one of those unchecked folders is in my > > favourites. > > > that means i have to check manually that folder. > This part should probably check on the server side i guess, because i used the > same setup without problem with kmail 4.4.8 (last time i did it until switching > only to dimap). server side? why would this be server side?(server is a dovecot) same setup? you mean also with 2 accounts from same server? and what do you mean switching to dimap? is that what i'm using? > > also with offline imap, you don't get any notification if you type in wrong > > password, you just don't get folders, even in the subscribing options you don't > > see folders, but just "loading..." > This is strange because you're supposed to get a notification windows like > « Authentification Failed » that's whay i get here when using a wrong password > for my dimap account.(cf screenshot done) even here, perhaps this may be due to the 2 accounts, since the first was ok, and the second was wrong (at addition, not afterwards) > But in all case thoses bugs are going to be closed as wontfix or switch to > kmail2 by upstream. huh? why can't this be solved? do you mean that this kmail2 is completely different? (In reply to comment #2) > > This part should probably check on the server side i guess, because i used the > > same setup without problem with kmail 4.4.8 (last time i did it until switching > > only to dimap). > > server side? why would this be server side?(server is a dovecot) same setup? I was using the same setup as you before aka : 1 « online » imap account & a « disconnect » imap account (dimap) using the same « account » on my dovecot server with kmail 4.4.8 and i did not noticed the problem you're reporting. So i'm wondering if it's not a problem on the host simply by a restriction to a maximum concurrent connection. > you mean also with 2 accounts from same server? only « one » account (aka same login) but 2 local account > and what do you mean switching to dimap? is that what i'm using? As said earlier i was using 2 locals account for the same imap login, one « online » imap account & an disconnect imap account. and later i simply switched to only one dimap account (deleting the « online » imap account) > > This is strange because you're supposed to get a notification windows like > > « Authentification Failed » that's whay i get here when using a wrong password > > for my dimap account.(cf screenshot done) > > even here, perhaps this may be due to the 2 accounts, since the first was ok, > and the second was wrong (at addition, not afterwards) i did not understand here. > > But in all case thoses bugs are going to be closed as wontfix or switch to > > kmail2 by upstream. > > huh? why can't this be solved? do you mean that this kmail2 is completely > different? Upstream will ask to first switch to kmail2 & then reproduce the bug Also regarding kmail2 the imap/dimap are now stricly different so you can simply check a case to switch an account from « online » imap to « disconnected » imap. (The component kmail is simply disabled so in fact you can't even report a bug against kmail1 but of course you can try to report it ) CC:
(none) =>
balcaen.john (In reply to comment #3) > (In reply to comment #2) > > > This part should probably check on the server side i guess, because i used the > > > same setup without problem with kmail 4.4.8 (last time i did it until switching > > > only to dimap). > > > > server side? why would this be server side?(server is a dovecot) same setup? > I was using the same setup as you before aka : 1 « online » imap account & a « > disconnect » imap account (dimap) using the same « account » on my dovecot > server with kmail 4.4.8 and i did not noticed the problem you're reporting. > So i'm wondering if it's not a problem on the host simply by a restriction to a > maximum concurrent connection. > > > > you mean also with 2 accounts from same server? > > only « one » account (aka same login) but 2 local account Can you maybe retry with a different account on same server, perhaps this has different implications? > > and what do you mean switching to dimap? is that what i'm using? > > As said earlier i was using 2 locals account for the same imap login, one « > online » imap account & an disconnect imap account. > and later i simply switched to only one dimap account (deleting the « online » > imap account) ic > > > This is strange because you're supposed to get a notification windows like > > > « Authentification Failed » that's whay i get here when using a wrong password > > > for my dimap account.(cf screenshot done) > > > > even here, perhaps this may be due to the 2 accounts, since the first was ok, > > and the second was wrong (at addition, not afterwards) > > i did not understand here. i mean that maybe, due to having 2 accounts this could be an issue (not to have notification); because, as that was a fresh install, i added my 2 accounts, before applying, and the second account had a faulty password at the very start. i also used kwallet on the passwords (donno if that has a bearing). then i pressed apply. i rightclicked on the first account (because it had no folders), and clicked on the server side subscription, but cancelled it, i still saw no folders, even after trying to get email, so i killed kmail (kontact really) and at restart, there were effectively folders (maybe because i had checked the "fetch email on startup" option before applying when adding the accounts. i tried to do the same thing for the second account, but it didn't work, and then i thought maybe i have wrong password and retried and eventually succeeded. also, i'll mention this, but i had this problem in mdv too; at work as well as at home, with different servers (both dovecot). (using imap itself never had this problem even when using kwallet). > > > But in all case thoses bugs are going to be closed as wontfix or switch to > > > kmail2 by upstream. > > > > huh? why can't this be solved? do you mean that this kmail2 is completely > > different? > Upstream will ask to first switch to kmail2 & then reproduce the bug > Also regarding kmail2 the imap/dimap are now stricly different so you can > simply check a case to switch an account from « online » imap to « disconnected > » imap. > (The component kmail is simply disabled so in fact you can't even report a bug > against kmail1 but of course you can try to report it ) so they have no LTS system? :-( . and anyway, is kmail2 even ready yet? also, i think we should try to support mageia 1 packages, so we should either try to fix this or have kmail2 as update rather than backport. (even though i generally would be against doing such things) i hope i'm not asking too much, but in any case, if there's something you want me to test, by all means i'll test. (In reply to comment #4) [...] > Can you maybe retry with a different account on same server, perhaps this has > different implications? Well in fact i'll already fetching 2 differents accounts on the same imap server so i can't reproduce here (well both are using dimap). [...] >> i did not understand here. > > i mean that maybe, due to having 2 accounts this could be an issue (not to have > notification); because, as that was a fresh install, i added my 2 accounts, > before applying, and the second account had a faulty password at the very > start. i also used kwallet on the passwords (donno if that has a bearing). then > i pressed apply. i rightclicked on the first account (because it had no > folders), and clicked on the server side subscription, but cancelled it, i > still saw no folders, even after trying to get email, so i killed kmail > (kontact really) and at restart, there were effectively folders (maybe because > i had checked the "fetch email on startup" option before applying when adding > the accounts. That's « normal » : you need to fetch manually on first start (or wait for the automatic fetch if you did configure kmail to fetch every 'x' minutes ) to see the folders. > i tried to do the same thing for the second account, but it didn't work, and > then i thought maybe i have wrong password and retried and eventually > succeeded. > > also, i'll mention this, but i had this problem in mdv too; at work as well as > at home, with different servers (both dovecot). (using imap itself never had > this problem even when using kwallet). > > > (The component kmail is simply disabled so in fact you can't even report a bug > > against kmail1 but of course you can try to report it ) > > so they have no LTS system? :-( . and anyway, is kmail2 even ready yet? Well kmail2 was expected for kde SC 4.5 so that's already 1 year ago (& they stopped working on kmail probably 16 months ago with some small bugfixes) > also, i think we should try to support mageia 1 packages, so we should either > try to fix this or have kmail2 as update rather than backport. (even though i > generally would be against doing such things) i'm not sure it's wise to provide kmail2 as an update for Mageia 1 because migration is far (but really far) from perfect & i doubt end users would like it ;o) > i hope i'm not asking too much, but in any case, if there's something you want > me to test, by all means i'll test. Well i can provide a kdepim 4.6 for you if want to test (& cry) /me sighs fine, i give up... close it as wont_fix i still think it's bad for mageia 1 to have this kind of broken functionality, but i can see that you're not in a position to fix it... (In reply to comment #6) > /me sighs > > fine, i give up... close it as wont_fix so let's go Status:
NEW =>
RESOLVED |