MTA and MPP configuration -JES4 2005Q4
My configuration is:
Internal Network
- Directory Server
- Access Manager
- Calendar back-end
- Messenger back-end (Store, MTA, MEM)
DMZ
- Communication Express - not running:-(
- Calendar front-emd
- Messenger front-end (MMP, MEM)
Although CE doesn't work properly, I'll post something about it.
My main concern is about how to configure MMP to connect to the right backend.
I collected the following info:
bash-3.00# telnet jes-msg-fe 143
Trying 192.168.x.x...
Connected to jes-msg-fe.
Escape character is '^]'.
* OK [CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN BINARY UNSELECT LANGUAGE XSENDER X-NETSCAPE XSERVERINFO AUTH=PLAIN] jes-msg-fe.jes.emcdda.europa.eu IMAP4 service (Sun Java(tm) System Messaging Server 6.2-3.04 (built Jul 15 2005))
a login admin password
a OK User logged in
a proxyauth jdoe demo
a OK Completed
a select inbox
aNO Server hosting this mailbox is not available
Note: I can access the inbox from jes-msg-be (the backend)
and
at the reboot of the service I get the following warning
Warning: couldn't bind port for /opt/SUNWmsgsr/lib/ImapProxyAService=/opt/SUNWmsgsr/config/ImapProxyAService.cf g@0.0.0.0:143
I suppose the 2 messages are related, but I cannot figure out how to fix them.
Thanks
Andrea
[1458 byte] By [
rainbow1] at [2007-11-26 11:14:31]
# 1
From your description, i'm just a little confused. . .
1. Do you actually have the store, AND MEM/MMP on the same box?
2. You also have MEM/MMP in the DMZ?
Can the MEM/MMP in the DMZ resolve the host name for your store,and connect to it with that name (as found in your ldap)? this is how MEM/MMP route, they need to look up the user, and pull the "mailhost" from that, to route to the correct server.
# 2
The back-end has just the store and the MEM ( to test if it works).
The front-end has the MMP and the MEM (again for test purposes) and the MTA.
I feel quite stupid :-(((
as the Messenger Administration guide states
"it is recommended that the MMP not be enable on a machine that is also running either the POP or IMAP servers."
to fix it, I issued the command:
jes-msg-fe#/opt/SUNWmsgsr/sbin/./configutil -o service.imap.enable -v no
This is why I was getting the warning on the service start-up....
the guide is useful, but as it explains the full product it is difficult for a newbie getting what he needs.
Actually it would be nice to find some standard configuration examples on the web, but I wouldn't able to.
I hope this could be useful for other newbies like me:-)))
Thanks
# 3
The command you ran,
/opt/SUNWmsgsr/sbin/./configutil -o service.imap.enable -v no
actually turns IMAP off for the store system. Likely, not what you wanted. . .
MMP on the store will now run, but it won't be able to connect to your store.
better . ..
/opt/SUNWmsgsr/sbin/./configutil -o service.imap.enable -v yes
and don't even start the MMP on the store, OR
Your fix was likely not what you really needed.
In order to better understand the relationship between Messaging Server and MMP/MEM, think of them as three separate products.
Messaging Server stands alone. It includes the MTA (Message Transport), the store (and access to the store via POP, IMAP, and HTTP)
MEM is a proxy specifically for webmail.
MMP is a proxy for IMAP and POP. Yes, there is a SMTP proxy. Only designed to be used in rare situations, where you're doing "POP before SMTP", something that's hardly used anymore.
