I don't think that's specifically Emacs-related. Your problem seems to be that you only have access to ports 80/443, and Gmail doesn't provide IMAP access over those: they only have 993 open for IMAP/SSL
See https://support.google.com/mail/troubleshooter/1668960 for reference
So unless you can bypass your proxy (by means of an external gateway for example),...
Short answer: switch to melpa.org or stable.melpa.org.
Long answer: marmalade goes down a lot, and the maintainers don't acknowledge it in the news section of the site. So it might simply have been the case that the site was down. I advise you not to use it.
If anyone needs to answer this question, here's how I solved it:
Install CNTLM and configure it with your NTLM creds.
Set environment variables HTTP_PROXY & HTTPS_PROXY to the localhost presented by CNTLM
that should sort it
Unless your mail provider provides IMAP/SMTP access on ports 80/443, you are out of luck. No email client can be tuned to give access to a port that is being blocked by a firewall.
When I am in these circumstances, I use a VPN such as OpenVPN (e.g. with a third party service provider) that CAN be accessed over these ports.
Then, you can tunnel all of your ...
There is a variable for debugging URL calls, url-debug, set it to true:
(setq url-debug t)
Use the function url-retrieve-synchronously, this will create a debug buffer called *URL-DEBUG* and there you can see all the debug output from the call:
(url-retrieve-synchronously (url-generic-parse-url "https://elpa.gnu.org/"))
I've never heard of CyberArk Privileged Session Manager, but from your description adding it to tramp-methods shouldn't be too hard. The simplest way is probably to add an entry with
Tramp could cache passwords. See variable password-cache-expiry. Its default value expires cached passwords after 16 seconds.
And/or configure auth-source.el properly. For example, add respective entries to .authinfo.
Read the Tramp manual, section "Password handling", for more details.
As per M.W.'s Answer to a Similar Question,
Emacs populates the url-proxy-services variable from the http_proxy, https_proxy and no_proxy environment variables if they are set.
You can then start your emacsclient from you GNOME terminal, just make sure that all variants (lowercase and capitalized) of the proxy variables are exported in your ~/.bashrc, ...
This seems an issue with PIA. By default they restrict SMTP access through their service to avoid SPAM abuse. You can contact their helpdesk to allow access to gmail from your account:
In order to have your SMTP server white listed, please submit a ticket
via the following link (or emailing