Welcome to WebmasterWorld Guest from

Forum Moderators: coopster & jatar k & phranque

Message Too Old, No Replies

NMS FormMail FireFox Problem

Can't See Success Page in FireFox

1:43 pm on Nov 12, 2009 (gmt 0)

New User

5+ Year Member

joined:Nov 12, 2009
posts: 1
votes: 0

Hi All

I am using NMS Formmail 3.14c1 on windows 2000 Professional Server fully patched.

I have been using NMS FormMail for some time now without problem but I have just found that when using FireFox 3.5.5 FormMail does not return the default success page but instead I get a message box asking the user how FireFox should open the file. The message is sent correctly to the recipient if the user presses the Cancel Button on the message box. (Some what counter intuative)

From searching the internet it seems that the default success page "header" is the problem - but I can not find away to resolve this.

Using "LiveHTTPheaders" in FireFox I see the response from the server as "Content-type: application/octet-stream.

I have tried a few hacks but nothing I do will make it work as expected.

Using IE the form works as expected even though the same Content-type header is returned.

BTW I have also tried using Matts FormMail but I get the same result.

9:08 pm on Nov 12, 2009 (gmt 0)

Senior Member

WebmasterWorld Senior Member rocknbil is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:Nov 28, 2004
votes: 0

Welcome aboard tlefcovitch, this is most likely a server issue (?) Doesn't do this in IE?

I don't play much with open source applications, always coding my own, but you could try this. It should really already be there.

Locate the portion of the script that outputs the response. You should see a print command.

print "first line of response";

Immediately before this line, add

print "content-type:text/html\n\n";

If you can't locate it, you can put it at the top of the script, immediately following the shebang

print "content-type:text/html\n\n";

This may or may not break something else, but shouldn't.

The only think I can think of is I seem to recall when working with Perl scripts in Windows based server environments, the content type header may not be required like it is on Linux. You might have one configured with that in mind and it's not generating content type headers, and the server is errantly generating the wrong, or no, headers.