|
Blue Forest http://www.lslnet.com at 13:28 on July 26, 2006
|
|
Will you be able to master a safe /etc/mail/access? PASTE
|
|
I have more doubts about how the access or relay-domain document, which made it to prevent spam, the user can be made to make the machines legal address. For example : I found someone with 163.net mail sent to the fake address, I set up inside : 163.net REJECT if access is to prevent the spam from 163.net, but I can not write to the users of 163.net. In addition, a simple method, together with the addresses of all the legal shield swap, a REJECT found a hidden Arab. My question is a bit stupid? Will instructions, the Xianxie
|
|
|
Re : Will you be able to master a safe /etc/mail/access? PASTE
|
|
You mentioned the significance of this problem is indeed very representative. Relay-domain or access installed in the handbook, can play in protecting the safety, but not very safe, and sometimes even at the cost of sacrificing usability of the mail service. For access to the configuration, I suggest you allow a small number of trusted users transmit mail through your mail server. For example, the internal local network users. It would be best not to use the domain name, but the use of IP addresses to restrictions. If you discover that you have an illegal users of the mail server, you can individually be refused. 163.net REJECT should avoid the use of the way. In short, we should use this type of security principles : tacit shielding all users, and then set up to allow a small number of legitimate users. Although rbl handbook provides a functional, but many of its popular free e-mail sites are listed, so little value.
Heart-->Linux!
|
|