Version: 1.99.0 (using KDE 4.7.2) OS: Linux Hello, I made a new install of openSUSE 12.1-RC2 and KDE 4.7.2 All used partions are newly formatted, so no previous data to convert. 1 I can send mails after initial configuration. 2 I can make new entries in address book 3 I cannot receive mails send to me from external systems nor mails created via point 1. In the beginning I saw some notion in the system message corner ( 0 %) but after resolving the password issue with KWallet I do not see any sign from the system upon clicking the check(receive) mail button and also no received mails. In the receive mail configuration I have set the following: a In receiving tab: Account: Receiving Frans -- off-line -- with detais: Account name: Receiving Frans Incoming mail server:pop.xs4all.nl Username: xxx Password: yyy via kwallet Destination Folder: inbox from Local Folders Port:110 Account: Local Folders -- Ready with information about: Mail Dir: /home/frans/.local/share/local-mail/ How can I get account Receiving Frans from the off-line stage to ready. In the file menu there is an entry activated with work off-line. If I deactivate this and go again in the file menu and click check mail(receive) a pop-up window askes to work on-line or off-line. Clicking on-line generates the following message in the msg window: Kmail is set to work on line, all network jobs resumed. The file menu again shows works off-line entry activated ????? What is wrongly set, please advice Regards, Frans Reproducible: Always Steps to Reproduce: Try to receive mail Actual Results: No mail received Expected Results: received mail OS: Linux (i686) release 3.1.0-1.1-default Compiler: gcc
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.