Exchange 删除对 SMTP 的支持吗?

发布于 2024-07-05 13:51:50 字数 165 浏览 5 评论 0原文

我想通过使用 telnet 到端口 25 来通过 Exchange 发送电子邮件。直到两周前我还可以这样做,但现在 Microsoft 的“安全修复”消除了这种可能性。

当我尝试时,我收到以下消息:

421 4.3.2 服务不可用,正在关闭传输通道

我该怎么办?

I want to send email with Exchange by using telnet to port 25. Until two week ago I was able to, but now a "security fix" from Microsoft has removed this possibility.

When I try, I get this message:

421 4.3.2 Service not available, closing transmission channel

What can I do?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

昇り龍 2024-07-12 13:51:50

我使用服务(消息实验室(ML))来过滤掉所有垃圾邮件。 我们获得了新的互联网连接,在将 ML 的入站/出站服务重新配置到新 IP 的过程中,我遇到了错误。 因此,我通过远程登录到端口 25 上的 IP 从外部对其进行了测试,并收到“421 4.3.2 服务不可用,关闭传输通道”错误。 我一开始没有意识到它失败的原因是我在 2007 边缘服务器接收连接器(用于 ML 服务器)上设置了特定的 IP 分组。 所以,我添加了我的局域网网络和 另外,我正在测试的外部主机的另一个IP,你瞧,我可以从两者进行连接。

我认为 ML 发生的情况是,他们测试连接的服务器所在的地址被排除在边缘服务器之外。

因此,我删除了测试 IP,并在边缘服务器上创建了一个新的临时接收连接器,接受来自所有地址 (0.0.0.0 - 255.255.255.255) 的连接。 然后我再次向 ML 提交了更改,你猜怎么着……这次他们接受了。 现在,我将简单地移除测试接收连接器,一切都应该是金色的。

I use a service (Message Labs (ML)) to filter out all the spam. We got a new internet connection and in the process of re-configuring ML's inbound/outbound services to the new IP, I got an error. So, I tested it from external by telneting to the IP on port 25 and got the "421 4.3.2 Service not available, closing transmission channel" error. What I didn't realize at first was that the reason it failed was because I had set a specific grouping of IPs on the 2007 edge server receive connector (for the ML servers). So, I added my lan network & additionally another IP for the external host I was testing from and low and behold, I could connect from both.

What I figured was happening with ML was that their server that was testing the connectivity was on an address that was excluded from the edge server.

So, I removed my testing IPs and created a new, temporary, receive connector on the edge server, accepting from all addresses (0.0.0.0 - 255.255.255.255). I then submitted the change to ML again and guess what...this time they accepted it. Now, I'll simply remove the test receive connector and everything should be golden.

夜还是长夜 2024-07-12 13:51:50

SMTP 是用于接收来自世界其他地方的电子邮件的协议,因此我怀疑 Microsoft 是否已放弃该协议。 您的服务器上一定存在其他配置错误。

尝试仔细检查您的中继设置和交换服务器上的事件日志。

SMTP is the protocol that is used to receive email from the rest of the world so I doubt that Microsoft has dropped that. There must be some other misconfiguration on your server.

Try double-checking your relay-settings and the event-log on your exchange-server.

与风相奔跑 2024-07-12 13:51:50

经过 5 年多的完美工作后,2010 年的 EDG 服务器突然停止接受并显示“421 4.3.2 服务不可用”。 SmtpReceive 日志 (Get-TransportServer | select ReceiveProtocolLogPath) 确认确实是边缘服务器生成了此错误。

EDGE 服务器在单个 NIC 上有两个 IP 地址。 经过以下步骤后,一切再次正常工作:

  1. 从边缘服务器上的网卡中删除一个 IP 地址,
  2. 更新 DNS 中的静态条目,以指向
  3. 默认内部接收连接器上的第二个 IP 地址,允许接收所有可用 IPv4 地址上的邮件。

注意:此设置不是 DMZ 的安全最佳实践。 最好使用两个 NIC,每个 NIC 的一条线路位于不同的区域。

After more than 5 years of flawless working, the 2010 EDG server suddenly stopped accepting with "421 4.3.2 Service not available". The SmtpReceive log (Get-TransportServer | select ReceiveProtocolLogPath) confirmed that it was indeed the edge server generating this error.

The EDGE server had two ip-addresses on a single NIC. After the following steps all worked fine again:

  1. remove one ip-address from the nic on the edge server
  2. update the static entry in DNS to point the second ip-address
  3. on the Default internal receive connector allow to receive mail on all available IPv4 addresses.

Notice: this setup is not a security best practice for a DMZ. Better to use two NICs each with a leg in a different zone.

独﹏钓一江月 2024-07-12 13:51:50

我在网站上找到了答案:

http://forums.microsoft .com/TechNet/ShowPost.aspx?PostID=2900802&SiteID=17

感谢您的帮助!

基本上,此功能在默认情况下已被删除,可以通过临时配置来恢复 - 但不能保证进一步的“更新”会再次破坏系统。 谢谢,微软。

I found the answer at website:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2900802&SiteID=17

Thanks for your help!

Basically, this functionality was removed by default and it could be restored by means of an ad hoc configuration - but with no guarrantee that further "updates" break the system again. Thanks, Microsoft.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文