Closed Bug 561560 Opened 14 years ago Closed 13 years ago

530 login incorrect

Categories

(SeaMonkey :: Composer, defect)

x86
Windows 7
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: geoff, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MAMD; Media Center PC 5.0; OfficeLiveConnector.1.4; OfficeLivePatch.1.3; SLCC1)
Build Identifier: Seamonkey 2.0.4

After using latest update and agreeing to disable part of Jave script as I was warned that this could make my system unstable I "published" to my website and although this worked OK I kept getting the above warning"530 login incorrect" which I had to keep pressing "OK" for publishing to complete. This has only happened since the latest update.

Reproducible: Always

Steps to Reproduce:
1.using "Publish as" on Composer page creates the warning"530 login incorrect"
2.
3.
Actual Results:  
page published OK but I had to keep clearing above warning with OK.

Expected Results:  
published as normal without login warnings
The warning about the java-deployment plugin didn't change anything in Seamonkey.
It disabled only an insecure plugin, you should see the disabled plugin under Tools/Addon Manager/plugins. Upgrading to Java 1.6 U20 should update both, the java plugin itself and the java deployment plugin.

Do you use ftp for uploading the website ?
(bug 467524 got fixed with SM2.0.4)
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.