Thanks for the ideas. I haven't resorted to tcpdump, but I do log all lines received from the clients and all lines sent from the program.

The IO::Socket docs says autoflush is turned on by default since 1.18. I've just checked and it's indeed on.

I don't implement EHLO & PIPELINING (yet).

The core of problem is, my program has correctly received all the DATA as well as the ".", and has processed the transaction and sent the 250 line, but these clients don't seem to get it. Haven't checked the return value of $sock->close() as the other poster noted, will do that. I'll also try doing a manual $sock->flush().

In reply to Re: Re: Socket weirdness by dgaramond2
in thread Socket weirdness by dgaramond2

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.