how to disable Messenger Express
I'm running a new Comms Suite R5 installation:
Sun Java(tm) System Messaging Server 6.3-0.15 (built Feb 9 2007)
libimta.so 6.3-0.15 (built 19:17:24, Feb 9 2007)
SunOS crispin-s10 5.10 Generic_118855-33 i86pc i386 i86pc
This is a 2-tier environment with multiple message stores.
I would like to disable the Messenger Express user interface entirely. I do need to run the webmail server (mshttpd) on the front-end, and I gather that ME runs within this server. Is there a way to turn off the UI but maintain the multiplexing functionality of the webmail server?
Thanks.
[611 byte] By [
esb2000a] at [2007-11-27 6:27:53]
# 1
Hi,
> I'm running a new Comms Suite R5 installation:
>
> Sun Java(tm) System Messaging Server 6.3-0.15 (built
> Feb 9 2007)
> libimta.so 6.3-0.15 (built 19:17:24, Feb 9 2007)
> SunOS crispin-s10 5.10 Generic_118855-33 i86pc i386
> i86pc
FYI - 120228-20 messaging server 6.3 patch is out with many many fixes, especially if you plan on using/testing the milter functionality in the future I recommend you upgrade.
> This is a 2-tier environment with multiple message
> stores.
>
> I would like to disable the Messenger Express user
> interface entirely. I do need to run the webmail
> server (mshttpd) on the front-end, and I gather that
> ME runs within this server.
Correct. It is the same as Calendar Express which runs on the cshttpd daemon and it also provides WCAP access to the UWC server.
> Is there a way to turn
> off the UI but maintain the multiplexing
> functionality of the webmail server?
Not that I am aware of. There was discussion just prior to release on providing just that feature (not deploying the Messenger Express html files etc.) but as the interface is 'deprecated' but not 'removed' it wasn't added.
What is your concern with running the ME interface (performance/end-user access)?
There is no performance difference with having ME available and not having ME available, and if end-user access is an issue, then obscuring the port or fire-walling the port to just allow UWC server access or changing the index page to a redirect elsewhere etc. is an option.
Regards,
Shane.
