Some thoughts:
1. Messaging Server 5.2 has been End Of Support Life, as of last month. You REALLY need to upgrade.
2. Messaging Server 5.2p1 is OLD OLD OLD. At least, you should apply p2, available from our download site. Hundreds of bug fixes. This should help keep you online until you can upgrade to 6.3.
3. There are several kinds of "smarthost".Depending on what you have, to change it takes different techniques.
If your current smarthost means that all outbound mail for, say the internet, all goes through one hub, then it's easy.
Locate the "imta.cnf" file.It's in two sections. You want the second section, "Part II, channel blocks". Locate the "tcp_local" line.Locate the "daemon" keyword. The smarthost follows that immediately. Change it. Run:
imsimta cnbuild
imsimta restart
done.
If your smarthost is of another type, it could be a "domain smarthost" or something else, and will be in the LDAP record for your domain.
Thanks for this. I'll nose around. As far as I know we're sending to only one smart host. This server was config-ed by a 3rd party vendor who no longer works for the vendor. Plus, being so dependable, I've rarely had the need to poke around in it, which has only added to my neglect in learning the unix environment as quickly as others. :-)
Our changes effect all domains hosted on this server, which need their mail to go to the new smart host.
I found the file you mentioned. The lines in question looks like this:
! tcp_local
tcp_local smtp mx single_sys daemon someserverA.here.net remotehost inner switchchannel identnonenumeric subdirs 20 noreverse
maxjobs 7 pool SMTP_POOL maytlsserver maysaslserver saslswitchchannel tcp_auth
tcp-daemon
!
! tcp_intranet
tcp_intranet smtp mx single_sys daemon someserverB.here.net subdirs 20 noreverse identnonenumeric maxjobs 7 pool SMTP_POOL ma
ytlsserver allowswitchchannel saslswitchchannel tcp_auth
tcp_intranet-daemon
I'll edit this file & see what we get.
If there is another smart host mention in our LDAP where would I find that?
Regards.....
Hi,
First off, I recommend you get some Unix training ASAP.
To run a command, any command, either your login must be configured to point to the PATH where the program is (for example /usr/sbin if you want to run programs under the /usr/sbin directory) OR you need to be in the directory where the command resides OR run the command with the full path.
Now the problem is that for iPlanet Messaging Server this path can be anywhere, it is configurable during installation.
By *default* you need to go to:
cd /usr/iplanet/server5/msg-<hostname>/
e.g. For my system which has a hostname of mysystem.sun.com
cd /usr/iplanet/server5/msg-mysystem/
Then you can run (the ./ out the front is required as it means "run the program called imsimta in THIS directory):
./imsimta cnbuild
Regards,
Shane.