Open
Bug 259679
Opened 20 years ago
Updated 2 years ago
Make the mechanism used for POP authentication mechanism adjustable
Categories
(MailNews Core :: Networking: POP, enhancement)
MailNews Core
Networking: POP
Tracking
(Not tracked)
NEW
People
(Reporter: ch.ey, Unassigned)
Details
Since users again and again run into buggy servers with which our automatic fallback doesn't help (e.g. bug 258077) it seems necessary to give the user the ability for enabling/disabling various authentication mechanisms. Currently m_prefAuthMethod (class nsSmtpProtocol) and pref mail.smtpserver.default.auth_method can only become PREF_AUTH_ANY and PREF_AUTH_NONE, so all or nothing. If we'd have PREF_AUTH_PLAIN, PREF_AUTH_LOGIN, PREF_AUTH_CRAM_MD5 a.s.o. and the code to interpret it, the user could choose (in a pref var first and then in UI). The questions are with or without UI and how to save it to the prefs (single pref for each mechanism or bitfields)? One solution would be a drop-down menu with all the mechanisms supported by Mozilla listed plus "automatic" for the current (and default) behaviour. This would enable the user to choose one mechanism to use or to fail (if not automatic). Or a series of checkboxes (one for every supported mechanism) so the user can combine any mechanism with every other.
Updated•20 years ago
|
Product: MailNews → Core
Comment 1•17 years ago
|
||
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•16 years ago
|
QA Contact: networking.pop
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•