6.0.0-alpha14
7/2/25

[#7145] Hordemail login problem
Summary Hordemail login problem
Queue Horde Base
Queue Version 3.2.1
Type Bug
State No Feedback
Priority 1. Low
Owners
Requester Andrew (at) aallison
Created 08/02/2008 (6178 days ago)
Due
Updated 08/14/2008 (6166 days ago)
Assigned 08/02/2008 (6178 days ago)
Resolved 08/14/2008 (6166 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
08/14/2008 10:50:44 PM Jan Schneider State ⇒ No Feedback
 
08/02/2008 10:23:39 PM Chuck Hagenbuch Comment #2
State ⇒ Feedback
Reply to this comment
Why would a js warning cause logins to fail? What does the Horde 
logfile say? And what are "spam protection letters"?
08/02/2008 09:27:17 PM Andrew (at) aallison Comment #1
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Base
Summary ⇒ Hordemail login problem
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
for the past couple of months or so (since the release of 3.2?), I've 
been getting "Login failed" with successful Firefox login, probably 
due to:

Warning: Use of captureEvents() is deprecated, see bug 330494.

Source File: 
https://aallison.com:2096/horde/imp/login.php?logout_reason=failed

Line: 0

Also, the spam protection letters are not displayed properly by Firefox!

Saved Queries