Yes. My outgoing email goes out via Sonic's SMTP server, with the SPF records to allow it to have a source address of my own domain. Incoming email goes to my own domains and gets forwarded.
This seems to be trouble-free. The domain is on a cheap shared hosting account. I'm not running a server. I own the domain, and not though the hosting company, so I can switch to another provider if necessary. In 27 years, I've had to do that twice, because the hosting provider went out of business.
This is easy to do, and I don't have to deal with Google. I don't even get much spam. All the spammers seem to be targeting the big services now.
I just looked at my spam folder. I'm regularly being offered dental supplies, large hydraulic sheet metal bending presses, and ammonium sulfate fertilizer. It seems that having your own domain now means you get mostly business-to-business spam. I subscribe to Machine Design, which gets me some heavy industrial marketing, but I have no idea why I get dental supply ads. The fertilizer spams, from China, look like a scam - there's a fertilizer shortage, so that's a spam which might get replies.
I used to have a 'Shirley' email all the time from China about elevator parts. It was such a niche kind of spam that I eventually replied and requested pictures of a bunch of parts. They sent them!
https://web.archive.org/web/20030412191437/http://www.penny-...
Spammers are miserable, I don't fault anyone for giving up.
Third party email providers, the so-called "established businesses", get a free pass as sending SMTP servers that are accepted by almost all receiving STMP servers. Everyone just assumes everything coming from those SMTPs is legit. Establishing this "legitimacy" and getting the "free pass" is difficult and some have suggested, the third parties may employ anticompetive tactics.
However, IMHO the receiving SMTPs is a different issue. Why do we let these third parties receive and store our email. (Why do our homes have their own mailboxes. Why not use a "P.O. Boxes" instead.) Eventually we could move away from letting third parties control the receipt of our mail. Neither "POP3" nor "webmail" was part of the original concept of email.
Today, it is easier than ever to set up overlay networks where we can assign our own IP addresses and run our own SMTP servers that can communicate directly with other SMTP servers on the overlay network. These networks are not open to the world, they may only be open to people we know. Much of our mail is between people who know each other, e.g., friends, family, colleagues. Or businesses that we contact first. We can separate different social and business networks on different overlay networks.
Anyway, the sending and receiving of mail can be separated. We do not need to let a third party control both.
[1] - https://support.mozilla.org/en-US/kb/openpgp-thunderbird-how...
Or because they know the third-party doctrine doesn’t apply to attorney work product and privileged materials.
https://moxie.org/2015/02/24/gpg-and-me.html
https://blog.cryptographyengineering.com/2014/08/13/whats-ma...
I use https://github.com/Free-GPGMail/Free-GPGMail which is a plugin for GNUPG, without the "support" plan.
GPG Mail is a paid for add-on, but it works and it works well.
Here is the same thing, without the paid support. https://github.com/Free-GPGMail/Free-GPGMail
- GPG Suite was released under an Open Source license in the past. Is that stil the case?
You GPG Suite including GPG Mail is still going to be released under an Open Source license.
- Am I still allowed to compile my own version of GPG Mail / GPG Suite removing any code regarding the trial or activation?
You absolutely are, the GPL makes sure of that. You will find the source code on this website next to the download link for GPG Suite.
We would kindly like to ask you not to use our names or icons if you plan to publish a binary for others to use. Also please do not release any complete installers as that may suggest that they are official releases.
I'm not going to remotely pretend that this would make PGP attractive or viable for the greater public. I do want to address your valid point that the general-purpose computer seems to be a dying breed, but that there are still options for mobile devices.
I've used K-9 Mail, though rarely do these days (it went poorly-maintained for a while).
There seem to be some options for iOS as well, such as iPG Mail, though I've no experience at all with it.
Note that I also listed an iOS option, and mentioned that there are others.
Again: PGP-enabled email apps are available on many platforms, though, again, this addresses only a small part of the larger challenge at encouraging adoption.
You can also even keep Gmail as your MX server! Just move messages off of it as soon as they arrive. It's just a mailbox, after all
Do you have more information about this?
I've been looking to do something similar so that I can have my mail sorted into folders without setting up the same rules on multiple clients. (Gmail's sorting doesn't seem to support some of the sorting I'm currently doing in Thunderbird)
Each domain has its own user home directory so for each there is a /home/${domain_name}/Maildir/ directory as the base for storing emails, and each IMAP4 folder has an associated directory. Snippet:
$ ls -1da Maildir/.Technology.FOSS.Projects.Linux*
Maildir/.Technology.FOSS.Projects.Linux
Maildir/.Technology.FOSS.Projects.LinuxContainers
Maildir/.Technology.FOSS.Projects.Linux.drbd
Maildir/.Technology.FOSS.Projects.Linux.kernel
Maildir/.Technology.FOSS.Projects.Linux.linaro.dev
Maildir/.Technology.FOSS.Projects.Linux.linux-i2c
Maildir/.Technology.FOSS.Projects.Linux.linux-input
Maildir/.Technology.FOSS.Projects.Linux.linux-pci
Maildir/.Technology.FOSS.Projects.Linux.linux-usb
Here's an extended snippet example from $HOME/.procmailrc that directs deliveries into the correct directory (IMAP4 folder): :0H
* ^List-id: .*linux-usb\.vger\.kernel\.org
$HOME/Maildir/.Technology.FOSS.Projects.Linux.linux-usb/
:0H
* ^List-id: .*linux-wireless\.vger\.kernel\.org
$HOME/Maildir/.Technology.FOSS.Projects.Linux.linux-wireless/
:0H
* ^List-id: .*yaffs\.lists\.aleph1\.co\.uk
$HOME/Maildir/.Technology.FOSS.Projects.Linux.yaffs/
:0H
* ^List-id: .*util-linux\.vger\.kernel\.org
$HOME/Maildir/.Technology.FOSS.Projects.Linux.util-linux/
### LinuxContainers
:0H
* ^List-id: .*lxc-devel\.lists\.linuxcontainers\.org
$HOME/Maildir/.Technology.FOSS.Projects.LinuxContainers/
### Linaro
:0H
* ^List-id:.*linaro-dev\.lists\.linaro\.org
$HOME/Maildir/.Technology.FOSS.Projects.Linux.linaro.dev/
:0H
* ^List-id:.*linaro-kernel\.lists\.linaro\.org
$HOME/Maildir/.Technology.FOSS.Projects.Linux.linaro.kernel/Using an SMTP relay was a suitable trade-off, for me, but I respect those who are able to endure the pains of sending non-flagged emails without it.