After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 438111 - No credentials cache found' when send/receiving
No credentials cache found' when send/receiving
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks: 502515
 
 
Reported: 2007-05-13 13:54 UTC by terrymarchant
Modified: 2012-01-02 09:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description terrymarchant 2007-05-13 13:54:44 UTC 
'Error: No credentials cache found' when send/receiving. Mails received just fine, now what do I do?


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1
Comment 1 André Klapper 2007-05-15 20:21:10 UTC 
what kind of server/directory do you try to access?
if this is about Kerberos, do you have a Kerberos ticket yet?
Comment 2 terrymarchant 2007-05-18 07:55:30 UTC 
Started with a fresh installation of Ubuntu from the CD image off the Internet. All fine.
I use a public mail server at jerseymail.co.uk with smtp and pop server names = mail.jerseymail.co.uk and have no idea whether its a Windows box or a UNIX one - I suspect UNIX as it's never off air..!
Went through the Evolution setup wizard and added my uid and password to the credentials for smtp and pop servers. Tried send/receive and messages received from the mail server with no problem.
If I compose a new message and try to send it, I get the 'no credentials cache found' error, although inbound messages still arrive OK.
Have since installed Thunderbird, been through setup and this works fine and can send and receive without error.
Comment 3 Akhil Laddha 2011-10-14 06:59:56 UTC 
Can you please check again whether this issue still happens in Evolution 3.0.3 or 3.2.0 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.
Comment 4 Akhil Laddha 2012-01-02 09:43:29 UTC 
Please feel free to reopen this bug if the problem still occurs with a newer
version of Evolution.