Dave wrote on 06/17/2011 10:44:13 AM:

> That's the funny thing about this error; we don't get an error or
> even a trace that the message is getting processed.  As I type this
> I'm starting to think this problem may be with the exchange server
> and not the Listserv.

If it is not showing up in the logs on Listserv, then you're probably
correct, it isn't Listserv.  Check the user's mail server and any others
in the path.


> I did look over the logs for anything and didn’t find anything.

Which logs did you check? Do you see Exchange handing the message off?  To
where? What did the logs on that host say?

Tracking mail is pretty straight forward if you have good logs.  Just
follow the bouncing ball.  Unfortunately, I've been told, Exchange does
not enable some needed logging by default.





Confidentiality Notice:
This electronic message and any attachments may contain confidential or
privileged information, and is intended only for the individual or entity
identified above as the addressee. If you are not the addressee (or the
employee or agent responsible to deliver it to the addressee), or if this
message has been addressed to you in error, you are hereby notified that
you may not copy, forward, disclose or use any part of this message or any
attachments. Please notify the sender immediately by return e-mail or
telephone and delete this message from your system.

############################

To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTSRV-L&A=1