Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
I'm not sure. You could build using the source package and tweak that so it installs somewhere you have write access to. However, the mail for the users needs to get written under their permissions and that requires root. Also, binding to port 25 requires root, even if only temporarily. I'm not sure what kind of hoops you have to hop through to get the external mail servers to send to you on a non-standard port.
Then there is probably the need for IMAPS which means setting up Dovecot.
I'm not sure. You could build using the source package and tweak that so it installs somewhere you have write access to. However, the mail for the users needs to get written under their permissions and that requires root. Also, binding to port 25 requires root, even if only temporarily. I'm not sure what kind of hoops you have to hop through to get the external mail servers to send to you on a non-standard port.
Then there is probably the need for IMAPS which means setting up Dovecot.
You mean that every mail account will also need an user on the server itself? How can I overcome this limitation? Lets imagine one probable reality, as I am seeing things now: 5 kids -> 2 Yahoo accounts; 1 Yandex account; 1 Hotmail account; 1 Gmail account. Each will have an account on DSafeMail. Wouldn't all of these accounts be stored on the service that makes the DSafeMail site?
Temporarily binding to port 25? Temporarily? I do not understand why.
((just imagining)) I would probably not bind it to port 25, but to one free port after the predefined ports.
I may ask root to install packages, this is not hard to happen. But I would like to run the needed programs somehow separated from other users and from the server, as a whole. It should be binded with my user only, as the websites I have in my subdomain.
Temporarily as root. The usual way is for the SMTP server to listen on the official port, that's port 25. Newer programs start as root to bind to a low port but then drop to an unprivileged user to manage the rest of the activities. I gather there are ways around using port 25 and using a higher one, but as mentioned my mail service knowledge is quite rusty.
Temporarily as root. The usual way is for the SMTP server to listen on the official port, that's port 25. Newer programs start as root to bind to a low port but then drop to an unprivileged user to manage the rest of the activities. I gather there are ways around using port 25 and using a higher one, but as mentioned my mail service knowledge is quite rusty.
No problem. (: Now I am mostly needing pointers and simpler steps to find what will be needed. Once I reach that list of a clearer situation, is when I will start trying to build it.
Continuing my readings in some pages pointed here, I thought something new. Most of what have been pointed here, is about spam and measures a mail server can do to avoid receiving spam or to reject messages (possibly being spam).
This might be because our ideas are diverging in a basic point. When I talked about receiving messages only for pre-aproved addresses, I was thinking in the point view of the end user. In other words, the work to prevent spam messages coming to my users is in a previous level of the service. Thus, the white and black lists (as I meant initially) should not make the server reject messages as if they were spam. This would not be fair, from the point of view of the mail servers network.
The messages I want to reject (or to keep in a separate folder for, at least, sometime) are not good examples of messages the server should reject (as spam messages are). They are bad from a different point of view: the kids using the service with the protection of not receiving messages from random people around the web.
Please confirm to me. Do you think that I still should learn about mail server configurations related do spam, white, grey and black lists, and other related matters?
If the answer is yes, will it be possible that this knowledge is applied in a new level of the server (the "DSafeMail" service's), capable of procesing the good and bad messages, as I idealize?
The whitelisting should work in that regard, but rather than rejecting the unknown addresses they need to go into a queue of sorts. Blacklisted addresses can be dropped, as they are known bad. Perhaps the greylisting method can be adapted so that the unknown messages are not rejected but simply queued and that the acceptance is based on manual action. Most of the whiteslisting advice has to do with hostnames and ip addresses, but should be modifiable to evaluate e-mail addresses. Both are just speculation as I haven't tried it.
About the spam, though the one article above comes in part from a marketing arm of M$, one that they like to try to position as "research", even they have to admit the level of economic damage. Though they may lowball the estimate, it's still in the same general level. What they fail to go into is the cause: botnets of M$ machines connected to the net. So the reality is that in order to eradicate spam, M$ products have to be eradicated at least from the open Internet.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.