etc/systemd/system/rvice ĭescription=Protonmail client bridge serviceĮxecStart=/usr/bin/protonmail-bridge -noninteractive Once the bridge was setup with a dedicated email account, it was time to make it a service/daemon, of course, to make it start and stop with the system. So in parallel, running dd if=/dev/sda of=/dev/null seemed to speed up this process. Keyboard input or disk I/O to help with that. GPG requires additional entropy to generate keys, and actually suggests some random At first I thought that gpg -batch -passphrase '' -quick-gen-key 'ProtonMail Bridge' default default never wasn't working as I did not see any output. I will add, that GPG key generation will take a considerable amount of time. Now, I am not the first to explore the Bridge setup, as PY Chuang hasĪlready done a lot of excellent work on the matter. Email clients like Mozilla Thunderbird then connect like any other SMTP/IMAP Not those you actually use to sign-in to read your mail). Listeners running on localhost ports and using ephemeral credentials (those that are generated by the bridge, but Offer people run the ProtonMail Bridge which provides SMTP/IMAP Removing all dependencies I had on Google Services.ĭue to ProtonMail’s architecture, they do not offer direct SMTP/IMAP connections to their servers. Up until recently I was using Gmail to send me such reports, but ever since moving to ProtonMail I have been slowly NAS reports, firewall, backup alerts and notifications. When running a homelab, often times there are various services which send you email notifications. Running a headless ProtonMail Bridge with a SMTP Relay for homelab use Roman Bezlepkin’s Website Running a headless ProtonMail Bridge with a SMTP Relay for homelab use
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |