I had configured Interchange to copy voicemails to email for one of my sites. It had been working fine until 2 weeks ago, and when I check the system now it seems like Interchange isn't even attempting to send out a message (I verified this with a packet capture on the Ethernet... no mail traffic is going out of the VM box).

This is what I see in the trace:

12- 4-2014 18:18:01.14 AUTO-FWD - checking box 181
12- 4-2014 18:18:01.14 AUTO-FWD - c/o timedate= 12/4/2014 18:18:1
12- 4-2014 18:18:01.14 AUTO-FWD - Time to auto-fwd msg 19
12- 4-2014 18:18:01.14 Auto-fwd from 181 to helpdesk@{domain redacted} (msg 19).
12- 4-2014 18:18:01.14 Auto-fwd Email 1
12- 4-2014 18:18:01.14 AUTO FWD Email-Delivering to helpdesk@{domain redacted}...


in engine.err:
9309 9309, M\MG000000181.028, 181, 28

Any suggestions where I should look next?

Thanks!

Ha, kind of answered my own question... ready.exe, the email service, was stuck. I restarted the service and it sent out a bunch of emails.

We'll see if it gets stuck again.

-J

That tends to happen with some revs of Interchange. If I was using email notification I just built a batch file to reboot once a week to clear up issues with ready.exe hangups.

Could users having very large mailboxes affect this?

-J

This happens if user leaves and his email address is no longer valid. Will cause ready folder to backup or the internet was down and could not send.

I have had exactly what Jim is describing happen to me. If there is a bad email,the rest of the messages will stack up behind them. It will probably work for you until that bad email comes up again.

Yes, that's what I discovered too. Thanks for the replies.

One more update: After reading the logs in ready.kvl, I found that the email service was trying to look up MX Records. I have the service pointed at my Active Directory DNS server, which doesn't normally need an MX record. Creating this was simple and cleared up recurring errors in the log.

Glad it worked out