comment on

O wise ones, I seek your guidance in the veneration of the goddess Perl, and the removal of her few remaining defects.

In short, I am trying to submit a minor documentation bug against perl. I tried using perlbug, and sending a mail to perlbug@perl.org and both resulted in a bounce:

550-Your address 212.23.3.234 has mailed to spamtraps here

The problem is that the IP address above is not mine, but my ISP's outgoing mailserver. It looks like one of the thousands of customers of my fairly small ISP has sent spam to perl.org at some point over the years. Does that mean that I am locked out of submitting perl bugs unless I do so via a raw SMTP connection to perl.org?

(I did think I could use my gmail account instead, but if my small ISP is blocked, then what chance a big worldwide webmail service?)

Is there another way to submit bugs against perl? or is this some sort of test to prevent those who won't make an effort from submitting reports?

In reply to Is there a web interface to report perl bugs? by chrestomanci

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks