I haven't tested your code just yet, but I mean to get around to it. I should have a chance today or tomorrow.

I do have a comment on the name. I think Net::SMTP::Pipelining is fine. I know the protocol RFCs usually show their commands in uppercase, but unless it's actually an acronym (like SMTP) I personally wouldn't expect a module name to be all capitals.

This is an interesting problem you're solving. It's good to see it as a module in its own right. It'd be even more interesting to me if the functionality was worked into Net::SMTP::TLS which is my mail-sending module of choice. Having pipelining along with encryption and SMTP authentication would be really nice. I'm sure others would like it worked into Net::SMTP since that's a commonly used module.

Is the end plan to have yet another mail sending module, or are you proving the concept for adding this feature elsewhere? Keeping it separate is good. Getting this functionality into modules with other features would make those other modules that much better, though. The folks who maintain the other modules would probably be happy to help implement this in them, too. I know I'd be happy to help put it into Net::SMTP::TLS as a user of that module.

In reply to Re: RFC: Net::SMTP::Pipelining by mr_mischief
in thread RFC: Net::SMTP::Pipelining by tirwhan

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.