Ignore it :) There is no harm done. The Forward.Res confirms receipt on the other side. Mbuni doesn't care really since it hands over to the MTA and assumes success means message will be delivered. Perhaps we don't want this??
On Dec 20, 2007 12:20 AM, Matthew Brown <[EMAIL PROTECTED]> wrote: > Has anyone run into the problem where you send a MM4 message successfully > but the MM4_forward.RES fails? You can see in the two log entries that when > we send the message and when we receive the RES that the message id is the > same. The file does still exist in the global directory but it fails to > correlate them. Does anyone have any thoughts? > > > > Thanks! > > > > Matthew > > > > 2007-12-19 16:09:04 [26853] [5] INFO: Global Queue MMS Bill: >From > 10.2.250.110/TYPE=IPv4, to_count=1, msgid= > newmms.revol.us-j-bq-qf8527.1.x856.46, msgsize=15784: returned=0.00 > > 2007-12-19 16:09:16 [26916] [0] WARNING: MM4 Received MM4_forward.RES from > mm4.shar.mms.ericyhost.com but cannot find queue entry for transaction > newmms.revol.us-j-bq-qf8527.1.x856.46 [j-bq-qf8527.1.x856.46]! > > > > > > > > Matthew Brown > > Manager, Network Systems Administration > > Revol > > (216) 573.7030 office > > (440) 341.0959 Revol line > > [EMAIL PROTECTED] > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.mbuni.org/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.mbuni.org/mailman/listinfo/users
