comment on

Well, I just tried this out. I sent the email from my work server, and picked it up at home, via Thunderbird.

The URL pointed to your script, which I copied to a local machine here.

I used the subject "Test" and the comment "Foo"

when I clicked the submit button in the email I got:

$subject is Test
$content is
[download]

The URL was correct: http://192.168.1.102/test/view_sent_form_data.cgi?subject=Test&content=Foo

Further analysis shows that the form variable in your scripts is set to a different name than what you're trying to print. IE, you do this in your script that generates the email:

Comments: <textarea name="content" rows="2" cols="15"></textarea>

and this in your script that prints:

my $comments = param("comments");

So, I think you have a combination of things. 1) Your CGI parameter is wrong, and 2) AOL may not be letting you submit properly (or may be munging your HTML as was suggested above)

In reply to Re^3: passing CGI form parameters via HTML email by mbadolato
in thread passing CGI form parameters via HTML email by gmacfadden

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.


laziness, impatience, and hubris
	PerlMonks