Smtp relay error SJES 2005Q4

Question

Hi,
In SJES 2005Q4 ....the switching to tcp_auth does not happen ......
I have done the setting as per admin guide.....
============
! tcp_local
tcp_local smtp mx single_sys remotehost inner switchchannel subdirs 20 maxjobs 7 pool SMTP_POOL mayt
lsserver maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0
tcp-daemon
! tcp_intranet
tcp_intranet smtp nomx single_sys subdirs 20 dequeue_removeroute maxjobs 7 pool SMTP_POOL maytlsserv
er allowswitchchannel saslswitchchannel tcp_auth missingrecipientpolicy 4
tcp_intranet-daemon
! tcp_submit
tcp_submit submit smtp mx single_sys mustsaslserver maytlsserver missingrecipientpolicy 4
tcp_submit-daemon
! tcp_auth
tcp_auth smtp mx single_sys mustsaslserver missingrecipientpolicy 4
tcp_auth-daemon
==========
Now a hosted user ......sends mail from a IP which does not fall in INTERNAL MAPPING IP ....he is sending this mail out .......and is doing authentication....
But the mail.log logs show relaying not allowed ....
550 5.7.1 Relaying not allowed:
On checking the logs further ..I see there is no switching to tcp_auth ..channel ..therefore tcp_local ==> tcp_local is treated as relaying....
WHY DOES'NT the switching to tcp_auth happen ...when a user tries to send mail to non-hosted Domain ...and uses SMTP AUTH...????
This would happen in iMS5.2 without any setting>>>
imsimta version
Sun Java(tm) System Messaging Server 6.2-4.03 (built Sep 22 2005)
libimta.so 6.2-4.03 (built 04:37:42, Sep 22 2005)
SunOS mta 5.9 Generic_118558-14 sun4u sparc SUNW,Ultra-80
Don't have any clues ..here ??
HAS anybody tried the SMTP AUTH...
Thanks

Answer 1

Think you're already getting good response on the other list.
2. About SMTP AUTH - you need to exclusively turn on this capability on
MTA side, file imta.cnf,
include maysaslserver on specific channels such as tcp_intranet,
tcp_local.
Compile the MTA configuration with imsimta cnbuild followed by
imsimta restart
==================================================================
Well,
By default this is enabled on Backend Server ...and I think it is
always enabled by default...
On my MTA the default settings in imta.cnf are already set for SMTP auth
....as per Admin guide
IMTA.CNF
defaults logging notices 1 2 4 7 copywarnpost copysendpost postheadonly
noswitchchannel immnonurgent maxjobs 7 defaulthost domain.com domain.com
Note the default noswitchchannel in the defaults above ....then
! tcp_local
tcp_local smtp mx single_sys remotehost inner switchchannel subdirs 20
maxjobs 7 pool SMTP_POOL maytlsserver maysaslserver saslswitchchannel
tcp_auth missingrecipientpolicy 0
tcp-daemon
Now I have switchchannel , maysaslserver saslswitchchannel tcp_auth ON
THE tcp_local ...which takes the non INTERNAL SMTP connections ...
! tcp_auth
tcp_auth smtp mx single_sys mustsaslserver missingrecipientpolicy 4
tcp_auth-daemon
As there is no switch statement here ...defaults noswitchchannel applies
SO THE DEFAULT imta.cnf supports smtp auth ....but it does not work here
I just tried to replicate the symptoms you see but I am having the
opposite effect.
Out of the box both the backend Messaging Server and the MTA have the
same keywords on the tcp_local channel and on the tcp_intranet
channel.
Here is a test I would suggest you try out.
I forgot to mention that these tests changes should take place only on the MTA.
>>
- Pick a host that you are going to do the telnet tests from and place
its IP address into the INTERNAL_IP mappings table. Place it as the
very first entry in that table and specify a $N so as to ensure that
this IP address is most definitely not considered internal.
Your mapping table should now look like:
INTERNAL_IP
172.16.131.88 $N
$(172.16.131.131/24) $Y
127.0.0.1 $Y
* $N
where 172.16.131.88 is the IP address of the node you telnet from.
In my testing, I get behaviour that is the opposite to what you
report. The MTA will announce the AUTH capabilities and the Message
Store will not do so.
Please test as shown above and see if you are able to get this behaviour.
Also the imta.cnf files are same (except the hostnames) in the backend
messaging server and the frontend MTA ...backend supports SMTP
AUTH...which I have already tested.
Further, I have a similar setup in iMS5.2 ....there everything works as
expected.....
I think there is a BUG in the installation of SJES 2005Q4 ...when we
choose single component MTA ....
One problem which I already solved is that ...the latter installations
(MMP, MTA, MEM etc) reset the MailHost ldap attribute value in the
directory server.