Created attachment 1699 [details] Shows the IMAP configuration in the main window and POP3 in the accounts window. After an update I was unable to connect anymore. The program complained about POP3 even though I had no POP3 accounts. The funny thing is that the main window still thinks that the accounts are IMAP4 while in the accounts window they all show as POP3!! See the attachment. Very strange. I tried to change the values of the protocol in accountsrc but did not change the behaviour. Is there any way to get my accounts back without deleting them all and recreating them? I have the OpenSuse provided binaries, which are still at 3.12 level Thanks.
The problem was caused because you used a newer version than 3.12.0 and then downgraded. Quit claws-mail, open ~/.claws-mail/accountrc and for each of your imap accounts change protocol=0 to protocol=1
(In reply to comment #1) > The problem was caused because you used a newer version than 3.12.0 and > then downgraded. I have never done that, at least not intentionally as the updates are automatic and there is a very small chance to have happened as you describe > Quit claws-mail, open ~/.claws-mail/accountrc and for each of your imap > accounts change > > protocol=0 > > to > > protocol=1 I have done that before you suggested but it did not work. However, I have upgraded to 3.14.1, I created a new IMAP account and the protocol was 3. I changed the protocol numbers for all my accounts to 3 and all is fine now. I still can't figure out what happen but thanks for stirring it up, I gave it one more try and worked.
That was not nice. My bug report was not invalid. The behaviour was caused by some combination of changes in software and using sequence. For example if you had in accountrc a version number that was read at startup and pop up a warning that an older version of software is used this situation could have been avoided. Going silently to change things is a bug and will happen in the future if you change protocol numbers. I will change the resolution to what I think it deserves. Please don't let the author's pride bring the worst of you. This report may be useful for other future bug reports and fixes. Cheers
i'm not the author, and there's no pride involved
well, just words actions tell a different story.
And BTW, this place is not a democratic place, Bogdan. You are not managing the bug tracker nor the project itself, Paul and few others constitute the Claws Mail team and this team decide where the project goes and how bugs are handled in the tracker.
look I am not here to haggle. I was trying to help as I appreciate free software. However, I noticed many times this arrogant, "I know better" behaviour for many OSS maintainers or developers. Remember, the only way to go better is to listen to your users. We are the helpers not your enemies. If this is not a democratic place then just close the code and sell the software to us. Your comment just reinforced what I said before: not democracy, and if I don't like it I can go somwhere else. Right? Look at kovid goyal the creator of calibre. He is a fine example of that. Good sofware but the guy will curse you if you make suggestions. OSS is there so that everyone can contribute even if this is with ideas or bug reports. Not all the ideas are good or reports valid, but this is how it works. I'll leave it resolved and invalid although I think none is true, but of course you guys know better. good luck.
We all appreciate free software and open source, but this doesn't mean it must reign the caos. Users are free to make suggestions and developers are also free to valuate them and decide what's is the way to go, according to their knowledge of the source base (thing that users aren't aware of) and many other aspects which belongs to developers only. This is sometimes interpreted the wrong way by some users who too easily mix the concepts of arrogance and knowledge.
Salvatore, if it is all about knowledge why don't you share that with the users so that they don't make the mistake of reporting the wrong thing next time. Why is it invalid? I have no clue and nobody bothered to say so! just marking something invalid is plainly disrespectful. If marked invalid but associated with a very small comment about why it is invalid would go a log way. Anything that makes sense and the dismissal would not appear as offensive. It will even save time. I am a developer too, but if I would commit something without a comment I would be given some warning by my peers. Modern versioning tools don't even allow it. Why would be a bug system any different? Anyway, this has dragged too long and it is going nowhere. Perhaps you can try in the future to see the other side of the story, because I have already been on your side many times and I know the feeling.
(In reply to comment #7) > look I am not here to haggle. I was trying to help as I appreciate free > software. > > However, I noticed many times this arrogant, "I know better" behaviour for > many OSS maintainers or developers. Remember, the only way to go better is > to listen to your users. We are the helpers not your enemies. If this is not > a democratic place then just close the code and sell the software to us. Did you notice it here? or are you simply prejudicing this project based on your bad past experiences? > Your comment just reinforced what I said before: not democracy, and if I > don't like it I can go somwhere else. Right? Look at kovid goyal the creator > of calibre. He is a fine example of that. Good sofware but the guy will > curse you if you make suggestions. Ah! so it's been bad past experiences :) BTW, FOSS projects are not democratic because voting and talking neither get the things done nor fixed. And believe or not this has worked far better than democracy ;-) AFAIK nobody has cursed you here (yet), so comparison is out of place, IMHO. > OSS is there so that everyone can contribute even if this is with ideas or > bug reports. Not all the ideas are good or reports valid, but this is how it > works. Sure, but accepting the opinion of others about your ideas when isn't the same is also a good policy, specially when you're not willing to contribute to demonstrate your ideas are feasible and just play ping-pong with bug status. > I'll leave it resolved and invalid although I think none is true, but of > course you guys know better. That's perfectly OK to think that, no problem :) BTW, this is not a forum, if you want to discuss/ask/whatever, please join the mailing list: http://lists.claws-mail.org/cgi-bin/mailman/listinfo/users > good luck. Same to you! best regards,
I think Paul did so when told you what exactly happened. If this was your fault or your distribution fault it has little concern. I expect you to understand that the code have to be maintained, that this project is open source and we're not paid for that, so it's better to use the time for better things instead of corner cases which will be reproduced *only* in a specific condition that in future will be missing. So it's just a waste. You fixed the problem, this is documented here, if ever someone (I have doubts) will have the same problem will understand what to do. o/
(In reply to comment #9) > Salvatore, if it is all about knowledge why don't you share that with the > users so that they don't make the mistake of reporting the wrong thing next > time. Why is it invalid? I have no clue and nobody bothered to say so! Paul explained it in the very first reply of your report. You said you didn't upgrade, but the version you have has no code to change that. What do you expect to be fixed? > just marking something invalid is plainly disrespectful. If marked invalid > but associated with a very small comment about why it is invalid would go a > log way. Anything that makes sense and the dismissal would not appear as > offensive. It will even save time. I'm starting to think you didn't read Paul's comment... > I am a developer too, but if I would commit something without a comment I > would be given some warning by my peers. Modern versioning tools don't even > allow it. Why would be a bug system any different? ..or that you didn't understand the implications of that comment joined with your denial of upgrade. > Anyway, this has dragged too long and it is going nowhere. Perhaps you can > try in the future to see the other side of the story, because I have already > been on your side many times and I know the feeling. Please, stop trying to image what we feel, you don't even approach :)
> Paul explained it in the very first reply of your report. You said you > didn't upgrade, but the version you have has no code to change that. > > What do you expect to be fixed? First of all Paul explained how to fix what I had and it wasn't exactly correct, but true, gave me the idea to go in the right direction. It looks like you don't read the comments, because I suggested what can be done: if claws mail noticed a different accountrc version should at least pop up a warning or refuse to modify the RC file. Look above in my comments. I would have known that there is something happening. However, claws has silently changed configurations. > I'm starting to think you didn't read Paul's comment... I believe that you did not read the thread, I complained only when he changed it to INVALID when it could be a WONTFIX which does need explanation. Obviously, it is not invalid but as you just said it happens in rare occasions. That's why I changed it to MINOR and WONTFIX, but someone, I don't remember who, changed it back to BLOCKER and INVALID! OK I understand that it is your code, but these actions contradict your comments. That change is plainly not logical, as you said it is not a blocker but it is an issue, even if a small one. This is when I brought up the pride issue and when you all guys started to lecture me about how I can't understand things and how wrong I am. Or course, what would a user know ... > your denial of upgrade. Denial? > Please, stop trying to image what we feel, you don't even approach :) I'll stop completely, this is my last comment because as, mentioned above the pride syndrome is not helping steering towards a honest, unbiased conversation, and honestly I did not envision such an escalation. I was just trying to help, but it was perceived as a critique and lack of understanding. No need to bash me I already got it, I can't understand.
(In reply to comment #3) > For example if you had in accountrc a version number that was read at > startup and pop up a warning that an older version of software is used this > situation could have been avoided. Just FYI. That was done back in July, see http://git.claws-mail.org/?p=claws.git;a=blob;f=src/prefs_migration.c;h=cf8a103da55119cc7a1e5136783fe7c39ec32c68;hb=HEAD But if you downgrade to an older version than that (which you did)...
Just for the record I experienced this problem when Arch Linux upgraded me from 3.14.0 to 3.14.1. I haven't run any other versions so not sure if this means Arch mislabelled one of the versions or what. The accounts still worked as IMAP, but they showed as POP and I kept getting errors saying the POP server was unavailable (despite being able to read and move e-mail on those accounts via IMAP.) Changing "protocol=0" to "protocol=1" in accountrc as suggested did fix the problem for me - now the accounts are showing as IMAP again and the POP errors have gone away.
(In reply to comment #15) > Just for the record I experienced this problem when Arch Linux upgraded me > from 3.14.0 to 3.14.1. That's not possible, unless Arch Linux has some weird policy regarding patches, versioning, etc. That could only happen if you upgraded to 3.14.x and then downgraded to 3.13.2 or lower. Upgrading from 3.14.0 to 3.14.1 could never cause that.
Yes, it's an Arch Linux packager error. See the tarballs here: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/claws-mail&id=7069252d132437450f95c2718572298f83533247 trunk/PKGBUILD is correct repos/extra-1686/PKGBUILD is incorrect repos/extra-X86_64/PKGBUILD is incorrect