Environment
GroupWise 18
Situation
Sent messages are stuck in limbo. Primary MTA appeared to be having MTP connection issues which has been resolved, should have been routed through mta on secondary domain but do not appear to have done so. Cannot find the stuck messages to reprocess.
Resolution
This has been reported to engineering.
A possible workaround would be to stop grpwise-ma
allowed messages to process again, as mta was apparently waiting
for port to open. The MTA is redirecting http connections to
7100 to 8200
instead of 7180, which is usually part of the monitor
agent