Hi Emmanuel, > That's a bit weird, can you reproduce this warning message if you run > msmtp like the following: > > echo test | msmtp -f yourem...@domain.tld yourem...@domain.tld > > (replacing yourem...@domain.tld by your real email)
this command produces the same message. > On my side, I can't reproduce the bug even with GNOME_KEYRING_CONTROL > and GNOME_KEYRING_PID environment variables defined. Surprisingly, these variables are set in my i3 session (but the process specified by GNOME_KEYRING_PID is no longer running). I assume that these variables have been set by network-manager trying to a connect to gnome-keyring (for whatever reason -- there are only system connections on this machine). Accessing network-manager using nm-tool or nmcli produces the same "gnome-keyring:: couldn't connect to [...]" warning. Is it possible that the warning when running msmtp is actually coming from network- manager or from some library used by both msmtp and n-m? Regards, Holger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
