Comcast email settings for a mac upgrade#
Comcast email settings for a mac download#

Have server settings requirements changed (and what should they be) or must we upgrade (with what settings) to v4.5, and will that solve the problem ?Ĭomcast server settings answer at '/t5/tkb/articlehistorypage/message-revision/2940642:8'ĪNSWERED: Having trouble connecting your Xfinity email to an email client

Comcast email settings for a mac download#

You must provide your public key to GitHub to establish a secure connection.Am not able to download (or view old) Comcast email. > debug1: Offering RSA public key: /Users/ you/.ssh/id_rsa Verify the public key is attached to your account > debug1: identity file /Users/ you/.ssh/id_rsa type 1 If a file existed, those lines would be '1' and 'Offering public key', respectively: $ ssh -vT. Later on, the 'Trying private key' lines also indicate that no file was found. The '-1' at the end of the 'identity file' lines means SSH couldn't find a file to use. In that example, we did not have any keys for SSH to use. > debug1: No more authentication methods to try. > debug1: Trying private key: /Users/ you/.ssh/id_dsa > debug1: Trying private key: /Users/ you/.ssh/id_rsa > debug1: Next authentication method: publickey > debug1: Authentications that can continue: publickey > debug1: identity file /Users/ you/.ssh/id_dsa-cert type -1 > debug1: identity file /Users/ you/.ssh/id_dsa type -1 > debug1: identity file /Users/ you/.ssh/id_rsa-cert type -1 > debug1: identity file /Users/ you/.ssh/id_rsa type -1 You can also check that the key is being used by trying to connect to $ ssh -vT. You shouldn't need to run ssh-add path/to/key unless you override the file name when you generate a key. Tip: On most systems the default private keys ( ~/.ssh/id_rsa and ~/.ssh/identity) are automatically added to the SSH authentication agent. Make sure you have a key that is being used You should verify your connection by typing: $ ssh -T Hi username! You've successfully authenticated. If your connection failed and you're using a remote URL with your GitHub username, you can change the remote URL to use the 'git' user. If you try to connect with your GitHub username, it will fail: $ ssh -T Permission denied (publickey). Always use the 'git' userĪll connections, including those for remote URLs, must be made as the 'git' user. The connection should be made on port 22, unless you're overriding settings to use SSH over HTTPS. > debug1: /etc/ssh/ssh_config line 47: Applying options for * > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Reading configuration data /Users/ you/.ssh/config To make sure you are connecting to the right domain, you can enter the following command: $ ssh -vT OpenSSH_8.1p1, LibreSSL 2.7.3 In some cases, a corporate network may cause issues resolving the DNS record as well. Pay attention to what you type you won't be able to connect to '' or ''. Check that you are connecting to the correct server If you generate SSH keys without sudo and then try to use a command like sudo git push, you won't be using the same keys that you generated. If you have a very good reason you must use sudo, then ensure you are using it with every command (it's probably just better to use su to get a shell as root at that point). You should not be using the sudo command with Git. Should the sudo command be used with Git?