requesting assistance troubleshooting Kmail
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Apologies if this turns out to be a duplicate message. I tried to send
to the list using my problematic Kmail client (and a message appeared
in my sent mail folder) but so far I don't see it having posted when I
look at the web archives for debian-user.
I sent a similar message to debian-kde this morning, but it appears
there's not much activity there, so I figured I'd also try here.
I've been a debian GNU/linux user (I like KDE for my desktop, though I
generally keep openbox (and gnome) available as "fallbacks") for quite
some time now (decades at least) and am in general a very happy user.
I've been using both thunderbird and claws-mail as IMAP clients for
some time, but recently (a few months ago) I set up Kmail (and I like
it very much, as integration with gnupg was relatively painless). I am
again using it as an IMAP client (with a different gmail address). I
have two computers, both running debian 9 stretch. On one of them (the
laptop), Kmail is functioning properly, but on the desktop machine
which I'm writing from now, incoming email has not been appearing since
the end of January. I don't see any obvious menu entries which would
give me access to log files in order to try to troubleshoot the
problem, so I'm looking for any advice as to how I might go about
correcting the issue so this instance of Kmail can again receive email
(it's possible that the problem is as simple as an incorrectly entered
password though I've just attempted to reenter it with no improvement
in mail fetching behavior). I'm not currently subscribed to this list,
so CCing me is perfectly fine (though I'll monitor the web archives for
responses on which I may not be CCed).
thanks so much in advance for any information anyone may have to
share with me,
~c
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEETiJHl0qlojpckrtNu4s9czGpNn8FAlqImY8ACgkQu4s9czGp
Nn/OzQ/+IBWlE2dCMIe/e74XGA8Uq8Gd2ngiWFPMUim18rLjNP2Ovz94ZmiIWk6u
8/jQEBi8e9rXw4I+cZ9746vBlsHgg7up685BTU4E0x5l8jKvWd5X5fOtZEKmKqZw
wQmG5QDeDhlDc8cJSIvy2x+lydMcBK+tb5OWmGVk6oqL+MrD6YHF7kR1EjLKpRzO
s8w41HNYLfykkcp5sccyDWizMu1YxlW5uft0p7ZeaEbqR7Dvq53M+VaVhckyUCuO
4BkTe8U5WVmP9cWwA3qADH5xg/TLmyzOUlNNVNHck0AVG/sg73M86vsayeTnHEhh
81uCDWPqBl7Z7WtqYBVFnIwQ7oa0tSmEn5RaEceEELeLAKlbiMJI6zzqB1f95ro4
xESoXAFxWtGr+snBMKFQU0RG3D900ehdeRa6lzr4A4QnndbVSd7B1soxmRaB5jFI
3y5Daknz6Fgdq74lJbW71m6vBz7qcfAGpPCBXm2t8DfeCQ6i/xQgv97Quse7l1Bi
wuInU+Hdxa4W7kW005qiiaP4ZQGhg3/dMQCsSehBKJHEWdzeB51mKAtVOW/iF+m+
Odwkbhe9YqxQr4dS7ad1dVZ0In64RM2kWaQpezKYqpqf1k+f2C5/YEE9AzFQsgMI
7OAtbLni/eAwH7HGy+iHhpjzWBZGlb7YwDnfGaILhrEk5PhgofA=
=4e9G
-----END PGP SIGNATURE-----
Reply to: