On Thu, 9 Apr 2009 16:35:03 +0100, "Kevin Lawry" <[email protected]> wrote:
> 
> (ASSP): DEBUG <IO::Socket::SSL=GLOB(0x6c62fac) HASH(0x6ac1544) l=3805>
> (ASSP): DEBUG <wrote: (3805)<long text>>
> 
> I am trying to capture a few more so that I can establish a pattern, but
> does this throw any light on the matter?

A normal SMTP dialog is a series of messages that are typically
under 80 characters long.  Messages containing binary data are
encoded (e.g., uuencoded or MIME encoded) into an 80-char text
format.  In practice most SMTP software accepts longer lines too.

ASSP logs all such messages in full in the log, in fact displaying
lines up to 200 chars.  Above 200 lines, ASSP just logs "long text"
as you show above.

All the above shows is that you tried to send a long line.  Could be
the message data was mis-formatted, or the SSL negotiation failed
and some SSL negotiation data was received at a higher ASSP layer
and sent as if it were message data.

        -jr

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to