Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Email was a feature of MILNET and BITNET before there was an Internet, and LONG before the World Wide Web (www/html). Actually, it was also a feature of many BBS systems and all of Fidonet even before THAT. Webmail came late, and is still not a standard for secure or many business systems.
While a gui interface is a nice addon- that is not the mail server. Sendmail (for every sane operating system) and Exchange (for Microsoft systems) were the primary corporate mail servers the last time I checked (five years ago, I admit), A WEB interface is just a gui front end that may be added onto the mail server.
It seems email is more important than an OS or even the internet.
OS and Internet has changed the world. People around the world can see and hear each other.
Yet secure communication is not easy (e.g US 2020 data breach).
Thank you, this is very helpful.
So email servers are email providers.
These email servers will have their own email clients to present the emails to the user.
There are basically two ways of doing email. Company servers that are on 24/7 use smtp to push mail around the internet. An smtp server program like mail or postfix can both send and receive emails. But obviously that won't work for home machines that may be on only intermittently. smtp will try again with mail that doesn't get through the first time but there's a high risk that mail may simply be dropped after a few unsuccessful tries.
Email clients like thunderbird use smtp only to send mail out. They use a different protocol called pop3 to download mail from a pop server or they might use imap to read the mail remotely. Both use "pull" rather than "push".
There are two ways of doing email.
Company servers that are on 24/7 use smtp to push mail around the internet. An smtp server program like mail or postfix can both send and receive emails.
Quote:
But obviously that won't work for home machines that may be on only intermittently. smtp will try again with mail that doesn't get through the first time but there's a high risk that mail may simply be dropped after a few unsuccessful tries.
Quote:
Email clients like thunderbird use smtp only to send mail out. They use a different protocol called pop3 to download mail from a pop server or they might use imap to read the mail remotely. Both use "pull" rather than "push".
You see, that's 'email'. It's complicated.
It shouldn't be.
Not in a good world.
It was a lot more complicated in the old days. Then you had three programs working together. A mail transport agent used smtp to send email between servers, a mail distribution agent distributed incoming emails to individual mailboxes, and finally an email client was used to read and write emails. This was in accordance with the Unix philosophy that each program should do one thing and do it well.
Programs like thunderbird are Swiss army knives that speak smtp and pop3 to a limited extent and therefore can send and receive emails without you needing to run a mail server on your machine.
It was a lot more complicated in the old days. Then you had three programs working together. A mail transport agent used smtp to send email between servers, a mail distribution agent distributed incoming emails to individual mailboxes, and finally an email client was used to read and write emails. This was in accordance with the Unix philosophy that each program should do one thing and do it well.
Programs like thunderbird are Swiss army knives that speak smtp and pop3 to a limited extent and therefore can send and receive emails without you needing to run a mail server on your machine.
Hazel is exactly right. I will not detail it here, but at times it was even more complicated. There are MANY more choices today, but things for you and I are FAR more simple!
"I want to note that if that mail client causes you issues or you simply do not like it, there are MANY MANY other email clients out there, and MANY of them are really quite good! You do not have to seek far. While every distribution is likely to default to one, the REPOS for your distribution are likely to have SEVERAL other options. I would not even attempt to load one outside of your REPO system, unless you have developer experience: manual software maintenance is not something to dive into lightly. The packages in your REPO are tested and maintained by your distribution maintainers for you. Saves no end of problems.
(PS. Thank you again guys who maintain distributions! I appreciate you all, even the ones who maintain distributions I do not use directly!)
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,364
Rep:
Hey larstrier,
Not sure if it's been mentioned yet, but another advantage of local email clients (Thunderbird or other) is that they offer the possibility of reading and writing email while not connected to the Internet, and then sending and receiving once online again. Whether this is useful or not depends on each user's particular needs.
I have never used "Webmail." I always use "an email client," whether on Linux or something else. I like being able to collect all of my mail simultaneously, from every one of the email identities that I have, and then to deal with them – if need be – offline.
(Yes, several of them are "Gmail," but quite a few of them aren't.)
And of course, millions of (say ...) "Microsoft Outlook" users routinely enjoy exactly the same convenience, although the exchange of their communiques does not involve SMTP nor POP.
Fortunately, this is not a "Linux-specific" matter. Offline email clients are legion.
Can you use Public Access Networks to host your email?
It seems that once your email is hosted on a commercial server or ISP you lose privacy and control. A number of people would like to have more control of your email and the number of notifications that get pushed out to you.
Has anyone looked into hosting your email on a Public Access Network such as Panix? You can set them up to be a Virtual Private Server and host email and websites. My question is whether they can interoperate with the mainstream global email servers?
Most VPS sites can interact with mainstream email servers. The issue I would anticipate would be that you would need to have a valid domain email server hosted by the VPS site to be able to send/receive email or you would need to use a mainstream server such as gmail/yahoo/etc. for your email. You also could set up your own domain and email server if the VPS site allows such. Lots of things to consider before you jump into that ocean.
I think a VPS like Panix can host one's own domain, and probably send email too. Whether it can be my own domain and avoid all the mainstream extra traffic and controls is a very good question I will track down.
I'm not sure what you meant by "having a valid domain email server" hosted by the VPS site. What makes an email server a valid domain?
I would like to avoid using mainstream servers if I could. I used Thunderbird many years ago and liked it, but now it seems as if it is just another wrapper for mainstream email servers.
I think a VPS like Panix can host one's own domain, and probably send email too. Whether it can be my own domain and avoid all the mainstream extra traffic and controls is a very good question I will track down.
I'm not sure what you meant by "having a valid domain email server" hosted by the VPS site. What makes an email server a valid domain?
I would like to avoid using mainstream servers if I could. I used Thunderbird many years ago and liked it, but now it seems as if it is just another wrapper for mainstream email servers.
Thanks again
Jojo
'
Two things to start with your own mail server: 1. your email server must be to current standards of behavior and security. Email security means it will, at the very least, refuse to forward email from non-verified sources. 2. You need an accepted MX record in the nameserver system. Generally this can be your own if you register and maintain your own domain. Otherwise, you apply to have an MX record registered with your ISP.
The, of course, if you fail to secure and maintain it properly, it may be blocked or blackwalled by any of several services or even your own ISP. There are enough threat sites out there without adding another.
I think a VPS like Panix can host one's own domain, and probably send email too. Whether it can be my own domain and avoid all the mainstream extra traffic and controls is a very good question I will track down.
I'm not sure what you meant by "having a valid domain email server" hosted by the VPS site. What makes an email server a valid domain?
I would like to avoid using mainstream servers if I could. I used Thunderbird many years ago and liked it, but now it seems as if it is just another wrapper for mainstream email servers.
Thanks again
Jojo
'
As noted, the email server is not the domain. It must be configured for dns to recognize that it is a valid email server for your domain, whatever that is. There is a lot of admin put into properly configuring a domain email server, then once it is working properly the management is much less.
Thunderbird is an email client that can work with almost any email server regardless of size. Do not judge thunderbird as limited to mainstream email servers because it is far more than that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.