Yes - it looks like when I had “Email body contains URL encoded input parameters” set to “No” it would send two messages - one html encoded and another text endcoded so setting the value to “Yes” gives me one message which looks like html endcoded - this is the result w/o an attachment:
2009-02-05 08:35:04 PST [ISP.0068.0026D] Content type: multipart/alternative;
boundary=“=alternative 005b161388257554=” Subject: bpm.mailToIS:testEmail
2009-02-05 08:35:07 PST [ISP.0068.0025D] No content handler for content type text/html. Service bpm.mailToIS:testEmail called without content handler.
2009-02-05 08:35:07 PST [ISS.0014.0016T] Invoking service bpm.mailToIS:testEmail
2009-02-05 08:35:07 PST [ISC.0049.0005D] Invoke : index=1 depth=1
2009-02-05 08:35:07 PST [ISS.0014.0016T] Invoking service PSUtilities.stream:streamToString
2009-02-05 08:35:07 PST [ISC.0049.0005D] Invoke : index=1 depth=1
2009-02-05 08:35:07 PST [ISS.0014.0016T] Invoking service pub.flow:debugLog
2009-02-05 08:35:07 PST [ISP.0090.0003C]
testbody
2009-02-05 08:35:07 PST [ISS.0013.0002D] Registering multipart coder multipart/mixed;
boundary=“----=_Part_12_21912271.1233851707388” for service {1}.
2009-02-05 08:35:07 PST [ISP.0068.0004T] Processed 1 new message(s)
but with an attachment - it seem to fail to launch and this is all i get:
2009-02-05 08:37:49 PST [ISP.0068.0026D] Content type: multipart/mixed; boundary=“=mixed 005b583888257554=” Subject: bpm.mailToIS:testEmail
#webMethods#Integration-Server-and-ESB#Flow-and-Java-services