Adam,
I've run into this problem on occasion when a bad email address causes it
to have a problem. The solution is to clear things out completely in the
queue and restart fresh.
I have the following CL program that I use. It has one parm. If the parm
is set to C, only the most recent entry in the queue is cleared. If it is
set to X, then the entire queue is cleared. End MSF before you run this,
then restart it when this is done:
PGM PARM(&CODE)
DCL VAR(&CODE) TYPE(*CHAR) LEN(1) /* 'X' or 'C' */
IF COND((&CODE *EQ 'X') *OR (&CODE *EQ 'C')) +
THEN(DO)
ENDTCPSVR SERVER(*SMTP)
CRTDTAARA DTAARA(QUSRSYS/QTMSCLEAN) TYPE(*CHAR) LEN(1) +
VALUE(&CODE) AUT(*ALL)
DLYJOB DLY(10)
STRTCPSVR SERVER(*SMTP)
ENDDO
ENDPGM
Let me know if this does the trick.
Rich Loeber
Kisco Information Systems
http://www.kisco.com
--------------------------------------------------------------------------
Adam Glauser wrote:
It seems that every time MSF starts up, we get errors logged about
undeliverable messages. I suspect that these are really old messages
that should just be cleared out, but I'd like to confirm that.
Google is not my friend today, nor any of the other days that I've tried
to look at this problem. I've read over what seem to be the relevant
portions of the 'AnyMail/400 Mail Server Framework Support' book from
IBM (SC41-5411-00).
The only option I've turned up in my searches is to use the
QzmfRtvMailMsg API to get information about the undeliverable messages.
This is rather a complex API. Is there another way to peek at MSF
messages?
midrange.com
