- 论坛徽章:
- 0
|
请问如何更改iplanet中smtp端口号?
趋势的答复和楼上的一样。但以前请人帮忙做成功过的,用了都快两年了,恢复了smtp认证,webmail也正常,这次是为做双机系统重装了,装得一摸一样,imta.cnf文件也是以前的文件拷贝过来的,拷过来的文件里面没有mustsaslserver这个关键词,只有maysaslserver。现在就是想不起来还有哪里需要修改。哪位帮忙的同志也忘记了。按照趋势的方法在tcp_local中加mustsaslserver关键词更本无效。
另外我的邮件现在处于集群环境,运行邮件服务的机器上至少有两个同网段的IP,不知道这个会不会有影响。
现在破趋势的管理页面还经常出现aphost错误,按照它的方法把配置文件中的IP地址改成域名,错误几率更大了。
趋势的网站上是这么写的:
标题: IMSS 5.5 for Solaris with Iplanet认证穿透问题
问题描述: 1、在Iplanet服务器上安装IMSS的时候,由于Iplanet与Postfix不能同时在一台机器上运行(有冲突),因而建议将IMSS配置成独立工作模式,由IMSS侦听SMTP 25端口,然后将检扫描后的邮件转发给本机侦听另一个端口(比如6000)的Iplanet:
->; IMSS (25) ->; Iplanet (6000)
2、在启用了IMSS后,所有邮件不需认证就可以外发。
3、Foxmail系统的用户在启用了认证后,无法外发。
解决方案: 出现该问题的原因是:用户的iplanet对本机不作认证限制,因此所有通过imss过去的邮件都可以往外发送邮件。
解决方法:
在Iplanet的配置文件中,修改以下字段:
! tcp_local
tcp_local smtp mx single_sys remotehost inner switchchannel identnonelimited subdirs 20 maxjobs 7 pool SMTP_POOL maytlsserver mustsaslserver saslswitchchannel tcp_auth
tcp-daemon
在上述加入mustsaslserver 字段就可以了
另外,还需要把smtp_greeting_msg=TrendMicro IMSS SMTP proxy前加#把头信息去掉,
即:#smtp_greeting_msg=TrendMicro IMSS SMTP proxy
这样,Foxmail系统也可以实现认证传递。
对于aphost错误也给出了解决方法,但是无效
Users of InterScan Messaging Security Suite (IMSS) for UNIX 5.5 receive the following message: "Cannot send request to aphost".
Product: InterScan MSS for UNIX
Version: 5.5 for Linux/Solaris
Solution ID: 20263
Created: 6/10/2004 9:53:19 AM
Problem: When users access the IMSS console, it displays the "Cannot send request to aphost" message.
Here is the complete message in the commoncgi.log file:
Tue Apr 27 16:33:49 CEST 2004 [DEBUG] HostID:
Tue Apr 27 16:33:49 CEST 2004 [DEBUG] 192.168.11.1:10319|212.8.120.212:10319|212.8.120.210:10319|212.8.120.211:10319| 212.8.120.214:10319|172.31.10.19:10319|192.168.1
Tue Apr 27 16:33:49 CEST 2004 [DEBUG] ApHost to be connectted:
Tue Apr 27 16:33:49 CEST 2004 [DEBUG] IMSS
Tue Apr 27 16:33:49 CEST 2004 [DEBUG] Result code of MR_queryToken:-101:1176871120
Tue Apr 27 16:33:49 CEST 2004 [DEBUG] Failed to query token of aphost
Tue Apr 27 16:33:49 CEST 2004 [DEBUG] Error comm with ApHost
Users made the following verifications:
TMI, CCGI and Aphost services are all running with no errors.
The IMSS daemon or the server has been restarted.
The console is accessed from another machine.
Users opened the console using IE and Mozilla.
However, the issue still persists.
Solution: In the following log entry:
"Tue Apr 27 16:33:49 CEST 2004 [DEBUG] HostID:
Tue Apr 27 16:33:49 CEST 2004 [DEBUG] 192.168.11.1:10319|212.8.120.212:10319|212.8.120.210:10319|212.8.120.211:10319|212.8.120.214:10319| 172.31.10.19:10319|192.168.1"
It appears that aphost is unable to bind correctly to the specified IP addresses. Thus, you must do the following to resolve the issue:
Go to /opt/trend/imss/TMI.
Open the TMI.cfg file and look for the HOSTID parameter.
Instead of the IP addresses, enter an FQDN.
Check on the PREVIOUS_HOSTID value as well to see what the value was prior to the issue.
Restart S99ISIMSS. |
|