Mail-POPRelay 2.1.1 Latest
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
Add =head1 LICENSE and the text of the license to the main module in your code.
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Mail-POPRelay-2.1.1/POPRelay/Daemon.pm -- Around line 104: You can't have =items (as at line 108) unless the first thing after the =over is an =item Mail-POPRelay-2.1.1/POPRelay.pm -- Around line 244: =cut found outside a pod block. Skipping to next block.Around line 348: '=item' outside of any '=over'Around line 364: You forgot a '=back' before '=head1'Around line 369: '=item' outside of any '=over'Around line 418: You forgot a '=back' before '=head2' You forgot a '=back' before '=head2'Around line 420: '=item' outside of any '=over'
List all used modules in META.yml requires
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
Add tests or move tests.pl to the t/ directory!
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
Move your *.pm files in a directory named 'lib'. The directory structure should look like 'lib/Your/Module.pm' for a module named 'Your::Module'. If you need to provide additional files, e.g. for testing, that should not be considered for Kwalitee, then you should look at the 'provides' map in META.yml to limit the files scanned; or use the 'no_index' map to exclude parts of the distribution.
Error: Object.pm, POPRelay.pm, POPRelay/Daemon.pm
Add 'use warnings' (or its equivalents) to all modules (this will require perl > 5.6), or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: Mail::Object, Mail::POPRelay, Mail::POPRelay::Daemon
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.