PowerMTA配置覆盖用于虚拟MTA的返回路径 [英] PowerMTA Config Override for Return-Path for Virtual MTA

查看:427
本文介绍了PowerMTA配置覆盖用于虚拟MTA的返回路径的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们的设置使用OEM Pro将电子邮件删除到PowerMTA拾取目录中。 OEM Pro只允许我们指定一个全局捕获所有域。这个全局捕获所有域都被用作返回路径,返回路径是必须由SPF记录查找进行验证的。所以这不是一个理想的情况,因为我们希望每位客户拥有自己的SPF记录,并将域名置于返回路径。

Our setup uses OEM Pro to drop the emails into a PowerMTA pickup directory. OEM Pro only allows us to specify one global catch all domain. This global catch all domain is being used as the return-path and the return-path is what has to be verified by the SPF record lookup. So this is not an ideal situation since we would like each client to have their own SPF records, and have their domain in the return-path.

我们推断,最佳方法是配置PowerMTA来覆盖返回路径地址,是否可以为虚拟MTA配置PMTA配置?

We have deduced that our best approach would be to configure PowerMTA to override the return-path address, is it possible to configure this the PMTA config for a Virtual MTA?

推荐答案

我收到了PowerMTA支持部门的类似问题的以下回复:

I received the following reply from PowerMTA Support on the similar issue:


PowerMTA没有设置消息内容。我们无法设置任何标题。
这是由您的喂养应用完成的。其他MTA服务器可以提供
这个功能,但是PowerMTA没有。

No message content is set by PowerMTA. We cannot set any headers. This is done by your feeding application. Other MTA servers may offer this functionality, but PowerMTA does not.

所以,我改变了我的应用程序来使用它们。 Net API,可以从那里设置MAIL。

So, I changed my app to use their .Net API, and it's possible to set MAIL FROM there.

这篇关于PowerMTA配置覆盖用于虚拟MTA的返回路径的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆