1·Otherwise some sort of whitelist or markdown would work.
否则，某些类型的白名单或降价会工作。
2·The whitelist can be managed via the extension's options page.
白名单可以通过扩展的选项页面进行管理。
3·Whitelist filters could be enabled on the client and at the DNS level.
可以在客户机上启用DNS级别的白名单过滤。
4·You can block all contacts except address book or anyone not from whitelist.
您可以阻止或任何人，除非所有联系人的地址簿不是从白名单中。
5·You can decide who can or can't reach you by mobile using whitelist functionality.
你可以决定谁可以或不能达到的功能，你的手机使用白名单。
6·You can implement whitelist filters both privately (on the client) and at the DNS level.
可以私下(在客户机上)和在DNS级别上实现白名单过滤。
7·For example, in a given environment, you can generally auto-populate your whitelist with.
例如，在一个给定的环境中，通常您可以使用下面的内容来自动填充白名单。
8·If you just used the black and whitelist solution, the spam would most likely get through.
如果您仅使用黑名单和白名单解决方案，那么很可能无法过滤出这封垃圾邮件。
9·And you can always check whitelist log to see blocked events and read deleted messages.
并且你可以随时检查白名单阻止事件日志以查看和阅读删除的邮件。
10·You can use the device whitelist cgroup to deny the container the ability to open the devices.
可以使用设备白名单cgroup拒绝容器打开设备。
1·You can implement whitelist filters both privately (on the client) and at the DNS level.
可以私下(在客户机上)和在DNS级别上实现白名单过滤。
2·A fairly aggressive technique for spam filtering is what I would call the "whitelist plus automated verification" approach.
对于垃圾邮件的过滤，有一种主动性相当强的技术，我想称之为“白名单加自动验证”方法。
3·For example, in a given environment, you can generally auto-populate your whitelist with.
例如，在一个给定的环境中，通常您可以使用下面的内容来自动填充白名单。
4·Whitelist filters could be enabled on the client and at the DNS level.
可以在客户机上启用DNS级别的白名单过滤。
5·These are directives to the devices whitelist cgroup which will mediate device creation, read, and write by the container.
这些是设备白名单cgroup的指令，它协调由容器执行的设备创建、读和写。