World of Virtualization "Black and White Lists in Zimbra
Zimbra - topic for many new, but is gaining momentum since the beginning of last year, there were many people who have implemented Zimbra in its infrastructure, or refined detail settings we already embedded in the product.
But now is not it. As you can see, going and testing this product, emails are sent from our server is not at all the addresses and, if correct, it is only on the internal addresses pistonheads and addresses of those who have registered in our system, that is, since you do not know other, you can send an email to your email address. And it's not the fault of our server and configured rules clearly white / black lists to protect your domain from mailing by unscrupulous users spam. But not only that, also to demonstrate the flexibility of settings Zimbra. This was a little more detail.
The fact that a GUI interface Zimbra no permission settings or limits to specific addresses sent as such. Of course you can close or open specific domains, but it is very inconvenient and not flexible. To configure the system in a similar way as we have enough to get into Linux. We will need only one folder and 3 correctly configured file databases. To do this, go to the folder pistonheads / opt / zimbra / postfix / conf / and create a file 2: permitted_ senders (those who can send messages) and protected_ recipients (addresses to which messages can be sent).
These two parameters pistonheads can not be configured from the GUI, but the option of those who can receive messages by simply locking mailboxes directly in the GUI. Further prescribes in these files we need boxes. In permitted_senders I did not restrict anyone and just ordered: * @ *. * And prescribed opposite OK. General syntax is as follows, write the desired boxes, which can write messages, tab back down, write OK.
In protected_recipients can insert a lot of what the settings, we find examples of online Zimbra. Syntax there next, first write and allow anyone in any listing it goes, the rest is prohibited. Can solve everything, but then will not need, and black / white list. I wrote the following:
That is, add your address to the allowed list, cancel the rest. And so many, many lines. But it is clear that you can register and watch for all I will not. Then our site he adds these lines, we also must not forget that for each of these files should be used to create the command postmap. Db file peculiar syntax file Linux. Things to happen automatically, I created a file update_ protected_ recipients, which added the following lines:
This file will be executed after each of your registration. Further work with the main configuration file, main. cf. Here the most important pistonheads thing to understand how performance will occur above the created files. I added the following lines:
1 line - marking those that can be sent on, it means that postfix first check our list of all of the rest will reject. Various different options, but for our needs exactly this moment.
2-line means that postfix pistonheads checks the file with those where you can send the rest of marriage. You can just ask to send could all that is the default, but first we wanted to limit and this parameter.
February 13, 2012 at 10:36 | # 2
Home Page Interesting links Acknowledgements About the Author Contact Us
Alexander Prilepsky Russia, Moscow Currently working Product Manager and VMware pistonheads Veeam company MEST. The summer of 2011 was promoted to VCP. Also received the vExpert title in 2013. On many sites dwell under the name FaRoR. If you have any questions, please mail me or call on Skype, be sure to consult on all your questions.
AD AMD-V Backup pistonheads BitDefender certification Citrix CLI ESX ESXi Fault Tolerance FreeNAS High Availability Intel-VT pistonheads licensing linked clones Microsoft Network News ntp Openfiler pistonheads RAID Security snapshot pistonheads StarWind TrendMicro trouble vCloud VCP vDS vExpert View virtualization VM vMotion VMware Server VSA VShield pistonheads VSphere XenDesktop Zimbra
Terms reprint.
Zimbra - topic for many new, but is gaining momentum since the beginning of last year, there were many people who have implemented Zimbra in its infrastructure, or refined detail settings we already embedded in the product.
But now is not it. As you can see, going and testing this product, emails are sent from our server is not at all the addresses and, if correct, it is only on the internal addresses pistonheads and addresses of those who have registered in our system, that is, since you do not know other, you can send an email to your email address. And it's not the fault of our server and configured rules clearly white / black lists to protect your domain from mailing by unscrupulous users spam. But not only that, also to demonstrate the flexibility of settings Zimbra. This was a little more detail.
The fact that a GUI interface Zimbra no permission settings or limits to specific addresses sent as such. Of course you can close or open specific domains, but it is very inconvenient and not flexible. To configure the system in a similar way as we have enough to get into Linux. We will need only one folder and 3 correctly configured file databases. To do this, go to the folder pistonheads / opt / zimbra / postfix / conf / and create a file 2: permitted_ senders (those who can send messages) and protected_ recipients (addresses to which messages can be sent).
These two parameters pistonheads can not be configured from the GUI, but the option of those who can receive messages by simply locking mailboxes directly in the GUI. Further prescribes in these files we need boxes. In permitted_senders I did not restrict anyone and just ordered: * @ *. * And prescribed opposite OK. General syntax is as follows, write the desired boxes, which can write messages, tab back down, write OK.
In protected_recipients can insert a lot of what the settings, we find examples of online Zimbra. Syntax there next, first write and allow anyone in any listing it goes, the rest is prohibited. Can solve everything, but then will not need, and black / white list. I wrote the following:
That is, add your address to the allowed list, cancel the rest. And so many, many lines. But it is clear that you can register and watch for all I will not. Then our site he adds these lines, we also must not forget that for each of these files should be used to create the command postmap. Db file peculiar syntax file Linux. Things to happen automatically, I created a file update_ protected_ recipients, which added the following lines:
This file will be executed after each of your registration. Further work with the main configuration file, main. cf. Here the most important pistonheads thing to understand how performance will occur above the created files. I added the following lines:
1 line - marking those that can be sent on, it means that postfix first check our list of all of the rest will reject. Various different options, but for our needs exactly this moment.
2-line means that postfix pistonheads checks the file with those where you can send the rest of marriage. You can just ask to send could all that is the default, but first we wanted to limit and this parameter.
February 13, 2012 at 10:36 | # 2
Home Page Interesting links Acknowledgements About the Author Contact Us
Alexander Prilepsky Russia, Moscow Currently working Product Manager and VMware pistonheads Veeam company MEST. The summer of 2011 was promoted to VCP. Also received the vExpert title in 2013. On many sites dwell under the name FaRoR. If you have any questions, please mail me or call on Skype, be sure to consult on all your questions.
AD AMD-V Backup pistonheads BitDefender certification Citrix CLI ESX ESXi Fault Tolerance FreeNAS High Availability Intel-VT pistonheads licensing linked clones Microsoft Network News ntp Openfiler pistonheads RAID Security snapshot pistonheads StarWind TrendMicro trouble vCloud VCP vDS vExpert View virtualization VM vMotion VMware Server VSA VShield pistonheads VSphere XenDesktop Zimbra
Terms reprint.
No comments:
Post a Comment