You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using Postfix as an MTA so that local mail on a linux box gets delivered to somewhere useful
Simple Postfix MTA Setup for headless hobbyists
So, you're a hobbyist or maybe even a user in a small-scale business capacity
and you have some kind of headless Linux (or other *nix) box, maybe it's a VPS
or a Raspberry Pi, and you want it to be able to email you with alerts (setting
up monitoring is a separate subject!)
History
I went round in circles with this for a while, because it seemed like such a
Situation: I had Ubuntu 18.10 successfully dual-booting with Windows 10. Tried to do_release_upgrade to 19.04 but it couldn't complete, probably because I had a million *-desktop packages installed and they'd trodden all over each other.
So I decided to install a fresh 19.04, using all defaults for everything. Install went smoothly but on reboot, there was no GRUB menu, just straight into Ubuntu.
After MUCH experimenting, it seems that the problem was that the default install was creating an "efi" partition which was effing it up somehow. The fix was to re-run the install, but instead of accepting the option to delete the previous Ubuntu and install over it, choose to "do something else", and manually the pick the partition to nuke and recreate. Do not create an efi partition.
It will piss and moan about not having an efi partition, but ignore it. It's fine, it will boot fine. Once you're up and running, pop a terminal and do:
--disable-web-security is the one that turns off the same-origin policy (the name is scarier than the action). Although the docs don't say this, this flag is ignored unless you also specify --user-data-dir. That's because --disable-web-security can be super risky so you shouldn't be surfing in that mode all the time, so Chrome requires you to use an alternative user profile, specified with --user-data-dir. However, you can get away with just giving --user-data-dir and not specifying a dir, and it will use the default one (so you get all your bookmarks, cookies, extension, etc. but --disable-web-security will still feel that honour has been satisfied and tuirn off same-origin policy.