[Evolution] SSL cert problems after server move
Hi, A few days ago I moved to a new server, on a new IP address. I used cPanel to transfer all my accounts from the old server to the new one. Old server: vortex.shinyideas.co.uk New server: fugu.fairhosting.co.uk My email services continued to be provided on the same hostname - mail.shinyideas.co.uk - but the IP address that hostname resolves to has changed to that of the new server. When I connected to webmail on the new server, I was prompted to accept new self-signed SSL certificates from fugu.fairhosting.co.uk, which obviously I expected. Accepting those gave me access to my email with no problems. Much the same workflow and outcome happened on my Android phone using the K-9 email client. When I fired Evolution back up after completing all the transfers, I got a message for each account asking me to accept new SSL certificates, but unexpectedly the Evolution messages give the old server name, vortex.shinyideas.co.uk. If I accepted them, I was then prompted for my username and password for each account, and entering the correct details was met with an 'Password was incorrect' failure message. Note that the same usernames and passwords do correctly log me in via webmail. I tried moving .local/share/evolution/camel-cert.db and .local/share/camel_certs/* away, and removing all references to mail.*, vortex.* and fugu.* from Seahorse, but that didn't make any difference. Does anybody know what's going on here? Or have suggestions for other things I could try, or specific debug info that would help? I've included the basics below. Thanks in advance for any help/suggestions anyone can offer! :) Regards, Denny denny@serenity ~ $ evolution -v evolution 3.10.4 denny@serenity ~ $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS" denny@serenity ~ $ uname -a Linux serenity 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # The following is terminal output from running Evolution, temporarily accepting the 'new' certificate for my first account and trying to log into it, then closing that and all other dialogs after that fails, then closing the app: denny@serenity ~ $ evolution (evolution:28706): camel-WARNING **: Failed to initialize NSS SQL database in sql:/etc/pki/nssdb: NSS error -8126 (evolution:28706): camel-WARNING **: Unable to load store summary: Expected version (1), got (0) (evolution:28706): camel-WARNING **: Cannot load summary file: Success (evolution:28706): camel-WARNING **: Unable to load store summary: Expected version (1), got (0) (evolution:28706): camel-WARNING **: Cannot load summary file: Success (evolution:28706): camel-WARNING **: Unable to load store summary: Expected version (1), got (0) (evolution:28706): camel-WARNING **: Cannot load summary file: Success (evolution:28706): camel-WARNING **: Unable to load store summary: Expected version (1), got (0) (evolution:28706): camel-WARNING **: Cannot load summary file: Success java version "1.7.0_95" OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.1) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) (evolution:28706): evolution-mail-WARNING **: (mail-send-recv.c:1140):receive_update_got_folderinfo: runtime check failed: (info != NULL) (evolution:28706): evolution-mail-WARNING **: (mail-send-recv.c:1145):receive_update_got_folderinfo: runtime check failed: (info != NULL) (evolution:28706): evolution-mail-WARNING **: receive_update_got_folderinfo: Could not connect to 'mail.shinyideas.co.uk:993': Issuer certificate is invalid. (evolution:28706): evolution-mail-WARNING **: (mail-send-recv.c:1145):receive_update_got_folderinfo: runtime check failed: (info != NULL) (evolution:28706): evolution-mail-WARNING **: receive_update_got_folderinfo: Could not connect to 'mail.shinyideas.co.uk:993': Issuer certificate is invalid. (evolution:28706): evolution-mail-WARNING **: (mail-send-recv.c:1145):receive_update_got_folderinfo: runtime check failed: (info != NULL) (evolution:28706): evolution-mail-WARNING **: receive_update_got_folderinfo: Could not connect to 'mail.shinyideas.co.uk:993': Issuer certificate is invalid. (evolution:28706): evolution-mail-WARNING **: (mail-send-recv.c:1145):receive_update_got_folderinfo: runtime check failed: (info != NULL) (evolution:28706): evolution-mail-WARNING **: receive_update_got_folderinfo: Could not connect to 'mail.shinyideas.co.uk:993': Issuer certificate is invalid. denny@serenity ~ $ ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] Zoom composer window?
Is there any way to zoom the composer window? I have a 4K laptop screen and the default font size is just too small. Unfortunately, while I can zoom the reading windows, I can't zoom the composer window. And while I can increase the font size in HTML emails, that makes it big for the recipient, something I'm not trying to do... Any suggestions? Thanks, Josh -- Joshua Megerman SJGames MIB #5273 - OGRE AI Testing Division You can't win; You can't break even; You can't even quit the game. - Layman's translation of the Laws of Thermodynamics j...@honorablemenschen.com ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] How to deal with S/MIME signature where address differs from from address
On Sun, 2016-03-06 at 18:23 +, Pete Biggs wrote: > > > > > > > > > > > > > the signature doesn't have much to do with the message headers, > > > not > > > with the From; evo shows at the very bottom who signed it. > > Thinking about it, I find this strange, and actually would like to > > be > > notified if the signature address differs from the From address. > > > > Maybe I do not understand the idea behind it, so I wanted to ask > > again > > for the reasoning behind the current implementation. > S/MIME certificates can be created by anyone for any email address > and > the public key for the certificate is included with every message. > As > such they are not designed to, and can not, verify the sender. The > sender, if they so wish can create a new certificate for every email > they send. In fact in Evolution I can select any S/MIME certificate > with any email address (and I have a few) to sign a message, the > email > addresses don't have to match up - it's usual that they do match, but > they don't have to. > > S/MIME certificates are designed for encryption and to verify that > the contents of a message haven't been altered in transmission. Also that the sender is in possession of the private key, i.e. has signed the message. However (for example) an assistant might send a message signed by a supervisor, in which case the sender's address would probably not match the signature. (Actually there are email protocols for the assistant to send mail on behalf of the boss, or indeed on behalf of a group of people, but they are rarely used). poc ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] How to deal with S/MIME signature where address differs from from address
> > > > > the signature doesn't have much to do with the message headers, not > > with the From; evo shows at the very bottom who signed it. > Thinking about it, I find this strange, and actually would like to be > notified if the signature address differs from the From address. > > Maybe I do not understand the idea behind it, so I wanted to ask again > for the reasoning behind the current implementation. S/MIME certificates can be created by anyone for any email address and the public key for the certificate is included with every message. As such they are not designed to, and can not, verify the sender. The sender, if they so wish can create a new certificate for every email they send. In fact in Evolution I can select any S/MIME certificate with any email address (and I have a few) to sign a message, the email addresses don't have to match up - it's usual that they do match, but they don't have to. S/MIME certificates are designed for encryption and to verify that the contents of a message haven't been altered in transmission. P. ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] How to deal with S/MIME signature where address differs from from address
Dear Evolution folks, at work we started to set up S/MIME certificates because the Apple Mail and the associated devices seem to support those by default. It was very easy to set this up with Evolution (3.12.9 from Debian 8 (jessie) too). Thank you for that! Now a colleague sent an email with an S/MIME signature, but Google Mail rewrote the from header field (see X-Google-Original-From) and therefore the address in the From header field differed from the address for the S/MIME certificate the message was signed with. The signature was marked green though, so I never noticed this, until my colleagues told me, that Apple Mail shows a warning or something like it. In #evolut...@irc.freenode.net I was told, that this is the expected behavior. > the signature doesn't have much to do with the message headers, not > with the From; evo shows at the very bottom who signed it. Thinking about it, I find this strange, and actually would like to be notified if the signature address differs from the From address. Maybe I do not understand the idea behind it, so I wanted to ask again for the reasoning behind the current implementation. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
