Open
Bug 531704
Opened 16 years ago
Updated 13 years ago
the ISP submission form should specify the requested information
Categories
(Webtools :: ISPDB Server, defect)
Webtools
ISPDB Server
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: mozilla.8id1r, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; nl; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5
Build Identifier:
The ISP submission form as it stands now is fairly undocumented and for a contributor it is hard to understand what information is actually expected in each field.
I think that sufficient information should be provided such that regular users who are able to setup their Thunderbird account should also be able to complete the form.
At least should there be a link to the spec at https://wiki.mozilla.org/MailServerList but probably the most important information should be ported to the form. Without focussing on layout and html-form implementation, I think we should add:
- portnumbers: suggest the default values
- socket types: make reference to encryption
- authentication: if there's only one option, this field makes no sense (and moreover it's not documented in the spec)
- username formula: tell what it is and mention the special values
- language of account spec: add option 'other' and mention that English or French are preferred if one of both is available
As for the spec at https://wiki.mozilla.org/MailServerList there are some discrepancies with approved records in the ISPDB:
- special values for usernames: e.g. "localpart" (spec) or "%EMAILLOCALPART%" (ISPDB)?
- port numbers: the spec seems to favour blank values rather than defaults but the ISPDB still includes defaults
There's some relation with https://bugzilla.mozilla.org/show_bug.cgi?id=528513 for describing the username field in the form. And https://bugzilla.mozilla.org/show_bug.cgi?id=518319 for the language field.
Reproducible: Always
| Assignee | ||
Updated•13 years ago
|
Component: ispdb → ISPDB Server
Product: Mozilla Messaging → Webtools
You need to log in
before you can comment on or make changes to this bug.
Description
•