Evolution insists on password every time

I’ve used Evolution before on a CentOS system so have some experience with it. BUT it was a long time ago and I don’t remember EVERY step specifically…

I’ve setup Evolution, got all my mail, contacts, calendar in from the CentOS system that’s being abandoned. It’s all perfect.
But every time the system or me manually checks for mail, it’s prompting me to enter the password.
The box has been checked each time to save the password “Add this password to your keyring”, but it seems to not be doing that.

If I recall correctly the options are different now for the Receiving EMail and Sending Email options in the account editor panel.
Ports and servers are correct as I can actually download as long as I enter the password first. Sending mail works as well.

Referencing the Receiving EMail options, Security section I note now there is no SSL option as I think I recall it being before.
So I read up on that and now see it’s TLS so I’ve set **Encryption Method : TLS on a dedicated port.
**The only other options haven’t worked for me. (no encryption / StartTLS after connecting )

Then below that is the Authentication section. Theres a button Check for Supported Types. I know I’ve not seen that before.
Checked and only 2 options present Password and APOP. All others have a line drawn through them. I set Password
I’ve tried both and there’s never a field to insert/save the password. Neither one solves the problem when I try to send/receive.

Referencing the Sending Email panel:
**Server Type SMTP **/ port set to 465 / and Server requires authentication is Checked
Again the the Security section the same options as above are presented and I’ve set it to TLS on a dedicated port.
In the Authentication section, the Check for Supported Types offers Plain and Login. All others are stricken. I’ve tried both with no resolution.
In the Username field, my email address…

I’ve poked through menu options thoroughly and see nowhere to otherwise save the password to the mail account.

I feel like I’ve got to be missing something obvious but I can’t sort it out.

Hi, using Evolution on Gnome with no problems here, so please confirm that you are actually using Gnome, otherwise something might have gone wrong with integration of the (Gnome)Keyring.
For instance, if I logon via the regular login screen I don’t need to enter a password for Evolution (GnomeKeyring unlocked by the login process), while if I login “automatically” for a selected user, I have to enter the password the first time I start Evolution after logging in.
Then no password is needed on any new invocation of Evolution.

If I recall correctly the options are different now for the Receiving EMail and Sending Email options in the account editor panel.
Ports and servers are correct as I can actually download as long as I enter the password first. Sending mail works as well.

Referencing the Receiving EMail options, Security section I note now there is no SSL option as I think I recall it being before.
So I read up on that and now see it’s TLS so I’ve set **Encryption Method : TLS on a dedicated port.
**The only other options haven’t worked for me. (no encryption / StartTLS after connecting )

Then below that is the Authentication section. Theres a button Check for Supported Types. I know I’ve not seen that before.
Checked and only 2 options present Password and APOP. All others have a line drawn through them. I set Password
I’ve tried both and there’s never a field to insert/save the password. Neither one solves the problem when I try to send/receive.

It might depend on the mail server, but that setting works for me.

Referencing the Sending Email panel:
**Server Type SMTP **/ port set to 465 / and Server requires authentication is Checked
Again the the Security section the same options as above are presented and I’ve set it to TLS on a dedicated port.
In the Authentication section, the Check for Supported Types offers Plain and Login. All others are stricken. I’ve tried both with no resolution.
In the Username field, my email address…

The “Login” setting works for me, but again it might depend on the mail server.

“please confirm that you are actually using Gnome”…
and there it is… I knew it had to be something basic. Thanks OrsoBruno.

I’m running KDE, so I went into YaST and installed “keyring” with dependencies as necessary and have rebooted with no help.

Can someone advise … how much of / what of Gnome do I need to make this work again?

Maybe of interest to someone, running KDE in CentOS and Evolution somehow seemed no problem. At least I don’t recall having to do anything other than install Evolution.
But I’m happy to be back on an OpenSuSE system. Overall I like it much better.

I suggest you switch to using “lightdm” for login. Either “lightdm” or “gdm” will unlock the Gnome keyring. But “sddm” probably doesn’t.

So far I’ve installed the keyring and lightdm packages.
I wasn’t sure what was supposed to happen so I rebooted and tested, and still needed a password constantly.

So did some digging and found instructions and have done this:

[b]localhost:/home/MyUserName #[/b] update-alternatives --list default-displaymanager

/usr/lib/X11/displaymanagers/console
/usr/lib/X11/displaymanagers/lightdm
/usr/lib/X11/displaymanagers/sddm
/usr/lib/X11/displaymanagers/xdm

[b]localhost:/home/[FONT=monospace][b]MyUserName[/b] #[/b] update-alternatives --config default-displaymanager

There are 4 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager)
  Selection    Path                                  Priority   Status

------------------------------------------------------------
  0            /usr/lib/X11/displaymanagers/sddm      25        auto mode
  1            /usr/lib/X11/displaymanagers/console   5         manual mode
* 2            /usr/lib/X11/displaymanagers/lightdm   15        manual mode
  3            /usr/lib/X11/displaymanagers/sddm      25        manual mode
  4            /usr/lib/X11/displaymanagers/xdm       10        manual mode
Press <enter> to keep the current choice
[li], or type selection number: 2[/li]```
  

A noted, I've already set the displaymanager for lightdm
When I rebooted, I could not find any  display manager options so I entered my system password and booted into KDE... 
Still requiring a password on every mail check.

"I suggest you switch to using "lightdm" for login"...   How is that done?

And I don't know what to expect.  I'm following direction but really am not familiar with the concept in total.
When I login lightdm, am I still going to see the KDE GUI as previously?

Thanks![/FONT]

You should be able to select KDE (it is probably called “Plasma 5”). As I recall, the place to select as near top right of the login screen.

I hope that makes the Gnome keyring available for evolution. But perhaps evolution has already saved somewhere in its settings, to no try the keyring.

I’m close to 70yrs old now so some of this stuff is getting more difficult to grasp. But I am determined to make this work.
So… I see now the login screen is “different” which I suppose is “lightdm”? And I found in the upper right corner how to choose KDE to start up and did so.
Still not working without continued password prompts.

I’ve looked in root and user folders for hidden files with keyring in the name, No joy.
Looked for everything that says ** gnome** in it and tried to find something keyring in all of the files I could look into and I see a few references in some files to keyring but I’m not seeing something that I can change a value in.
Same with an ** evolution** search. LOTS of files, no idea if there’s something in there I can edit but I didn’t see any files with keyring in the filename.

In the course of looking for the answer I encountered a site that is fedora based I guess. They state:

I found in fedorahosted.org where someone committed a simple script that generates GNOME keyring startup and shutdown scripts for KDE. I’m guessing this is used in the KDE live CD spins for Fedora. Anyway, this script can easily adapted to generate GNOME keyring integration scripts for your local KDE installation. Just start Konsole, and paste this into the command line:

cat > $HOME/.kde/env/start-custom.sh <<EOF
#!/bin/sh
eval \`gnome-keyring-daemon\`
export GNOME_KEYRING_PID
export GNOME_KEYRING_SOCKET
EOF
chmod 755 $HOME/.kde/env/start-custom.sh
cat > $HOME/.kde/shutdown/stop-custom.sh <<EOF
#/bin/sh
if -n "\$GNOME_KEYRING_PID"]; then
kill \$GNOME_KEYRING_PID
fi
EOF
chmod 755 $HOME/.kde/shutdown/stop-custom.sh

I tried running that but it failed after restarting the system.
So I tried entering each line one at at time to see if I could understand what it was doing and sorted out that the first bit of code was trying to create a file and failed.

**localhost:/home/MyUsername #** cat > $HOME/.kde/env/start-custom.sh <<EOF 
> #!/bin/sh 
> eval /'gnome-keyring-daemon/' 
> export GNOME_KEYRING_PID 
> export GNOME_KEYRING_SOCKET 
> EOF 
bash: /root/.kde/env/start-custom.sh: No such file or directory

Finally the lightbulb lit in my head - the code must be different for Tumbleweed,
So walking the folders in Dolphin, as the better of you will know, there is no .kde folder on the system. Mine is .kde4 and it’s not in the root tree but in my user folder.

Can this code be modified somehow for opensuse?

I noted also on that site it stated:

The solution is simple – have GNOME keyring launch automatically when you log in to KDE

Well that seems obvious enough and I understand there is an “autostart” folder but I don’t know how to make Gnome keyring launch automatically.

In my /home/UserName/.config folder are two empty folders
autostart
autostart.scripts

My tired old brain tells me that it’s likely there should be some sort of script file in one of those to “start gnome keyring”, but I don’t know how to structure it.

Sorry I cannot help you with integration of Evolution and KDE, but here on Gnome I see the following packages installed and you may want to check if you have them all:

# zypper se -i keyring
Loading repository data...
Reading installed packages...

S | Name                         | Summary                                                               | Type
--+------------------------------+-----------------------------------------------------------------------+--------
i | gnome-keyring                | GNOME Keyring                                                         | package
i | gnome-keyring-pam            | GNOME Keyring - PAM module                                            | package
i | libgck-modules-gnome-keyring | Glib wrapper library for PKCS#11 - Modules                            | package
i | libgnome-keyring0            | Library to integrate with the GNOME Keyring                           | package
i | typelib-1_0-GnomeKeyring-1_0 | Library to integrate with the GNOME Keyring -- Introspection bindings | package
#

I also see the following files in /etc/xdg/autostart/

# ls /etc/xdg/autostart/ | grep keyring
gnome-keyring-pkcs11.desktop
gnome-keyring-secrets.desktop
gnome-keyring-ssh.desktop
#

which are apparently responsible for launching the gnome-keyring at login; they are installed by the gnome-keyring package, so you should have them too.

And, BTW, you are not alone approaching 70 here :wink:

I dunno. Maybe I need to just quit with computers.
The keyring works flawlessly with no messing around… once I actually installed the keyring files.
I had installed something of gnome but not what OrsoBruno specified.
Ran those through YaST with dependencies as the system presented and restarted.
All is well. With the PC at least.

Thanks all!