Thanks! I'm glad to hear some "on topic" again.
In general, I agree with 'Put up or shut up'. One reason why there no my modules on CPAN is I don't think they are good enough (even if I think they better than existing CPAN modules, it isn't good enough reason to put them on CPAN just because of this!). But I'm working on this, and I hope best of them will be uploaded to CPAN in several months.
... handles a total turnaround flow of around 4 million emails per day ... The Perl modules for handling network traffic are generally solid, reliable and pretty well maintained.
Wow. Okay, you think existing modules are much more reliable than one could write using all related RFC. I don't see anything wrong with this. I want reliable solution, I suppose it must comply to all such RFC, but I may be wrong, of course.

Can you list which exactly CPAN modules you use in your system for parsing emails, with additional notes if you also use some important changes to this modules which isn't open source or just not accepted by CPAN module authors (yet). Such list can be right answer to my previous question.

As for the time issues, well, clock_gettime(CLOCK_MONOTONIC) but why do I see so many questions about it's reliability ...
Very interesting. Can you provide a link to such discussions/questions?
accept hardware that is so bad that it NEEDS NTP
Hmm. I use usual dedicated servers on some hosting companies. They do need NTP if I wish to sync time between servers to be able, for example, join and sort their logs.
Also I must use NTP if I simple wish to show correctly current date/time on project's webpage.

Anyway, my software can be used in different environments by different users, and I can't guarantee they don't use NTP or don't change time manually. But I must guarantee 30 second timeout in my software will be always 30 seconds. Is there something wrong with my point?

In reply to Re^6: Reliable software OR Is CPAN the sacred cow by powerman
in thread Reliable software: SOLVED (was: Reliable software OR Is CPAN the sacred cow) by powerman

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.