Wow, what a rant. Given that I have a limited number of hours in the day, I'll ignore most of it, but this part right here:
Parsing emails is really needed task, it's text processing task and it's related to system administration. CPAN has huge amount of modules for this task, and no one of them support all email-related RFC. After so many years no one developed such module! AND NO ONE THINK IT'S NEEDED - at least comments to my question say so......... "Yeah, why you think you need reliable email parser, what you will use it for? Forget about it, man, you don't need it. Nobody need it!" :(
needs a response. I guess you miss the entire point of the Perl Email Project, as pointed out to you earlier? The project aims to identify the current best-of-breed email modules in CPAN, and:
- Recommend them as the best option for those tasks
- Develop and improve them further
So, here's at least one group thinking critically about CPAN, and working to improve it, in the particular area you're ranting about. The modules aren't perfect, nor will they ever be -- no software is -- but they can get a lot closer, and that's what we're trying to do.
If you actually want better email modules, it would be a good idea to (politely) file bugs on those modules for whatever it is you claim is broken. Ideally, providing a patch, or a test case, but at minimum a description of the bug and how to reproduce it.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.