Using Novell Netmail ( when sending returns error 5 (works using IE)



15 years ago
14 years ago


(Reporter: p.kongstad, Unassigned)


Windows 2000

Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

I have an account at Novell for mail ( which uses Novell Netmail.
I can check the mail and other functions except creating new mails.
When the send button is pressed it returns the error code 5 not able to create
new  mail. Works using IE. Mistake also happens using Firebird 0.6.1

Reproducible: Always

Steps to Reproduce:
1. Create an account at Novell (demo) and follow instruction given.
2. try creating a new mail from the demo account
3. press send button

Actual Results:  
It returns the error code 5.
I cannot verify if it is a problem at Novell or Mozilla.

Expected Results:  
Sending the mail and get the message that the window will close in 3 seconds

Comment 1

15 years ago
Testing Mozilla mail client:
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030901

I used my own account to forward a message, and to sent a test
message, to an own pop3 account at another provider. 
Tested with no attachments, plain text, myrealbox account IMAP, SSL.

Comment 2

15 years ago
I have been testing further.

The problem appears when only subject is filled in resulting in error 5.

When text is entered in message the message is sent.

Comment 3

15 years ago
As per comment 2, WFM 2004021608 (pre-1.7a trunk) Windows 98.

Reporter, do you still see this problem? Even after enabling all Javascript
functions in preferences?

Comment 4

15 years ago
I have been upgrading to FireFox 0.8 on XP and error do not exist.

I have no newer mozilla installed and do not expect to do so.

Comment 5

15 years ago
Great news. Thanks. WFM as above.
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.