Historically, test reports were sent via ordinary email.
The most common reason for errors sending a report back then was that
many Internet Service Providers (ISPs) would block
outbound SMTP (email) connections as part of their efforts to fight spam.
Since 2010, test reports are sent to the CPAN Testers Metabase over HTTPS. The
most common reason for failures are systems which upgraded CPAN::Reporter but
are still configured to use the deprecated and unsupported email system instead
of Metabase for transport.
If you are unsure which transport mechanism youre using, look for the
transport rule in the .cpanreporter/config.ini file, in the
users home directory. See CPAN::Reporter::Config for details on how
to set the transport option for Metabase.
Other errors could be caused by the absence of the
.cpanreporter/metabase_id.json file in the users home directory. This file
should be manually created prior to sending any reports, via the
metabase-profile program. Simply run it and fill in the information
accordingly, and it will create the metabase_id.json file for you. Move that
file to your .cpanreporter directory and youre all set.
If you experience intermittent network issues, you can set the
retry_submission option to make a second attempt at sending the report
a few seconds later, in case the first one fails. This could be useful for
extremely slow connections.
Finally, lack of Internet connection or firewall filtering will prevent
the report from reaching the CPAN Testers servers. If you are experiencing
HTTPS issues or messages complaining about SSL modules, try installing
the LWP::Protocol::https module and trying again. If all fails, you
may still change the transport uri to use HTTP instead of HTTPS, though
this is not recommended.
This software is Copyright (c) 2006 by David Golden.
This is free software, licensed under:
The Apache License, Version 2.0, January 2004