We are experiencing problems with Eudora 5x clients on iMS 5.2 whereby some attachments are being embedded in the body of the message. I have made sure that Eudora is not configured to do this but it seems to happen mostly within the internal channel; from one user on the system to another user on the same system. External messages seem to go out fine. Any ideas?
If you really want to know what is happening, then enable MM_DEBUG=5 in your option.dat file. Also put the channel keyword logging in the defaults section, then you don't have to guess what channels to enable it on while debugging this problem. Then do ./imsimta cnbuild; ./imsimta restart dispatcher.
NOTE -- this will cause some serious logging on the system so in a heavily loaded production environment take care.
Now cause a problematic message to be generated. Now you can look at the resulting log file for the message. In that log file you should see exactly what the client sent over the wire, before iMS has possibly touched it in any way.Its almost like doing a snoop wire and translating the output of that to text. I've used this technique many times in the last 10 years and is really the only way to know exactly what the remote system is sending.
Regards,
Chad
