Re^2: Reliable email parsing

Replies are listed 'Best First'.
Re^3: Reliable email parsing by davorg (Chancellor) on Sep 13, 2006 at 12:28 UTC
I've checked them. They are far away from compliance to all RFC I've listed. :( So, my question is still actual: is there exists realization compliant to all (or most) listed RFCs? Well, as I said, I'm pretty sure that's pretty well all of the email modules on CPAN. So if they don't come up to your high standards, then it looks like you're out of luck. Or... here's a wild and crazy idea. If you have specific areas where you know the existing modules have problems, then why not get involved with the Perl Email Project and help them fix those problems. Your involvement could be as small as raising bugs against the existing modules pointing out their deficiencies, or perhaps you could go as far as creating test cases that demonstrate the problems, or maybe you could even produce patches that fix them. Just saying that there are problems, doesn't really achieve much. Documenting the problems and helping to fix them benefits everyone. -- <http://dave.org.uk> "The first rule of Perl club is you do not talk about Perl club." -- Chip Salzenberg	[reply]
Re^3: Reliable email parsing by davorg (Chancellor) on Sep 13, 2006 at 12:05 UTC
I've noticed 818 perl modules(packages) listed on this site Yes, well that's because they seem to list every mail handling module that they found on CPAN. As I understand it, the Email::* namespace is supposed to be a complete set of modules for carrying out all email processing in Perl - all of which will work nicely with each other. Once that set is complete (and I'm afraid I don't know how far off that is) anything in any of the other namespaces will be redundant. This is a similar approach to the one taken by the Perl DateTime project a few years ago. -- <http://dave.org.uk> "The first rule of Perl club is you do not talk about Perl club." -- Chip Salzenberg	[reply]
Re^3: Reliable email parsing by dave0 (Friar) on Sep 14, 2006 at 03:42 UTC
I've noticed 818 perl modules(packages) listed on this site. I agree, this task is complex. But having 818 modules for single task looks like no one of them really solved it. :( The 818 modules are a nearly exhaustive list of any email-related module available from CPAN, and they're certainly not all for a single task. The list includes POP3 clients, SMTP servers, MIME parsers, local delivery agents, pipemailers, antispam tools, etc, etc. The reason they're all listed on the PEP wiki is to provide an easy way to categorize and annotate the modules, so that a subset of those modules can be recommended and improved as the current "best practice" for email handling in Perl. UPDATE: I've checked them. They are far away from compliance to all RFC I've listed. :( So, my question is still actual: is there exists realization compliant to all (or most) listed RFCs? Well, given that I use quite a few of those modules on a daily basis, I find it hard to believe that they're all "far away" from compliance. Do you have any specific issues to point out?	[reply]