如何在Zimbra中使用CB策略制作更先进的SPF控件？
我有一个带有Zimbra社区的邮件服务器和一些域。我将CBPolicy用于SPF控制，配额和其他内容。 SPF控件正在成功工作。但是，当我禁用SPF检查我的一个域之一时，它可以正确地用于外部域的电子邮件，但无法正确使用内部电子邮件地址。例如，当 www.example1.com 使用SPF支票关闭试图将邮件发送到 www.example2.com 带有SPF检查的'554 5.7.1 test@554 5.7.1 test@示例：拒绝发送者地址：失败的SPF检查；它返回错误。
有人可以帮助我正确完成此操作吗？
Webmail接口可根据SPF控件的打开和封闭域的预期工作。对于来自内部电子邮件地址和外部电子邮件地址的电子邮件，SPF控件在编程中正常运行或关闭。以上行为仅在使用POP或IMAP时发生。
I have a mail server with Zimbra community and a few domains. I use cbpolicy for SPF control, quota and stuff. SPF controls are working successfully. However, when I disabled the SPF check for one of my domains, it worked correctly for emails from external domains, but failed to work correctly for internal email addresses. For example, when www.example1.com with SPF check turned off tries to send mail to www.example2.com with spf check on, '554 5.7.1 test@example: Sender address rejected: Failed SPF check; it returns error.
Can someone help me with getting this done correctly?
The webmail interface works as expected for both open and closed domains with SPF control. For e-mails coming from internal e-mail addresses and external e-mail addresses, SPF control works correctly as programmed, on or off. The above behavior only occurs when using POP or IMAP.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我能够这样做：
首先，我创建了UNCHECK-SPF规则，并将优先级设置为1000。然后，我将源写为成员，而％internal_domain作为目的地。我从组中创建了一个名为internal_domain的组。我已经将所有内部域添加到此列表中。然后，我为SPF检查添加了一个新规则（UNCHECK-SPF）。我将其连接到了我之前创建的UNCHECK-SPF规则，USESPF =是，并将其注册为拒绝失败的SPF =否。稍后我尝试时，该规则在几分钟之内就应该运行。在完成所有这些方面，政策是Web-UI非常有帮助。
也许它可以节省别人的时间。
I was able to do it this way:
First, I created the uncheck-spf rule and set the priority to 1000. Then I wrote source as members and %internal_domain as destination. I created a group called internal_domain from the groups. I've added all my internal domains to this list. Then I added a new rule (uncheck-spf ) for spf checks. I connected this to the uncheck-spf rule I created before, usespf = yes and registered it as reject failed spf = no. When I tried it later, the rule worked as it should within a few minutes. The policyd-web-ui was very helpful while doing all this.
Maybe it will save other people's time.