edit>mailnews account settings select a pop or imap mail server and select "Server Settings" what you see: Use secure connection (SSL) ^^^^^^^^^^^^^^^^^ <- not in glossary Use secure authentication ^^^^^^^^^^^^^^^^^^^^^ <- not in glossary for fun, select a news server what you see: Always request authentication when connecting to this server ^^^^^^^^^^^^^^^^^^^^^^ <- not in glossary and not in help reached by clicking the "help" button. also incorrectly listed is newsrc file. it's offtopic for this bug, but if you're gong to fix the news pane you might as well fix it too. If something is listed for information only then it should be readonly. It isn't so we should format it the same way as the other items and tell people not to change it. next select outbound server, see "tls, if available" and panic. quickly look up tls in the glossary and get a really awful definition: TLS. See Secure Sockets Layer (SSL). It should at least have: Transport Layer Security (TLS) is the new Internet Engineering Task Force (IETF) standard based on SSL. See also SSL, encryption. It might be best for it to have nearly all of the SSL entry. Finally. click help and try to read about TLS if available. Here are the options: no; tls, if available; tls; ssl Here's the help: Use secure connection (SSL): If your outgoing SMTP server is configured to send encrypted mail, you can choose how often you want to use SSL (Secure Sockets Layer). If you are not sure which option to choose, check with your ISP or system administrator.

-> Doc: User Daniel, what do you think about this?

I don't know those terms, so I think timeless should give us a patch :-p

> Use secure connection (SSL) > ^^^^^^^^^^^^^^^^^ <- not in glossary Yes, it is in the glossary (at least SSL is). Is this really necessary with the SSL there? > Always request authentication when connecting to this server > ^^^^^^^^^^^^^^^^^^^^^^ <- not in glossary and not in help reached b Authentication and request aren't really computer terms. I don't feel that these need to be defined in the glossary. If the person doesn't know what those words mean, they need to start reading books :) As for adding the glossary entry, I think I'll do that in bug 221261.

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

Reconfirming for Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090611 SeaMonkey/2.0b1pre, neither "secure connection" nor "secure authentication" are defined in the glossary.

(In reply to comment #0) > edit>mailnews account settings > select a pop or imap mail server and select "Server Settings" I'm about to upload a patch that should address the following points of the original reporter: > what you see: > Use secure connection (SSL) > ^^^^^^^^^^^^^^^^^ <- not in glossary > > Use secure authentication > ^^^^^^^^^^^^^^^^^^^^^ <- not in glossary Both terms added. Added a link in mail_help.xhtml to secure connection. I haven't added link to secure authentication because it only appears as literals to be described in <li> elements, like this: <li><strong>Use secure authentication</strong>: Choose this setting if you want to use secure mechanisms for logging in like CRAM-MD5. If you are unsure if your service supports this, contact your service provider or system administrator.</li> > next select outbound server, > see "tls, if available" and panic. > > quickly look up tls in the glossary and get a really awful definition: > TLS. See Secure Sockets Layer (SSL). > > It should at least have: > Transport Layer Security (TLS) is the new Internet Engineering Task Force (IETF) > standard based on SSL. See also SSL, encryption. > > It might be best for it to have nearly all of the SSL entry. Added, but only with timeless' short proposal, in order to avoid duplicating information. > Finally. click help and try to read about TLS if available. > > Here are the options: > no; tls, if available; tls; ssl > > Here's the help: > Use secure connection (SSL): If your outgoing SMTP server is configured to send > encrypted mail, you can choose how often you want to use SSL (Secure Sockets > Layer). If you are not sure which option to choose, check with your ISP or > system administrator. I've revised the section corresponding to News Server Settings to match the actual contents of the preferences dialog.

A first draft of patch (surely a lot more will come) ;-)

Sorry for the bugspam, IanN, but I don't know who else is in charge of help content reviews. I've asked Neil (the current assignee for this bug) to review the patch, but probably I should ask you instead. :-? TIA

Mainly stefanh or myself that review help now.

Comment on attachment 397136 [details] [diff] [review] Patch addressing timeless points Changing reviewer address, as indicated by IanN.

(In reply to comment #10) > (From update of attachment 397136 [details] [diff] [review]) > Changing reviewer address, as indicated by IanN. Could you do your diff with unified rather than context output format (-U 8 typically).

Comment on attachment 397519 [details] [diff] [review] The same patch in the correct format (-U 8) >diff -U 8 bug221259/original/glossary.xhtml bug221259/glossary.xhtml >+<dt id="secure_connection">secure connection</dt><dd>A connection which uses >+ some type of encryption (usually, <a href="#ssl">SSL</a>) to ensure it >+ can&apos;t be intercepted by third-parties. Most of the time, the server is >+ the one providing the certificate to identify itself.</dd> What does "the server" refer to? You've not mentioned it elsewhere in this definition. >+<dt id="tls">TLS</dt><dd>Transport Layer Security (TLS) is the new Internet >+ Engineering Task Force (IETF) standard based on SSL (Secure Sockets Layer). >+ See also <a href="#ssl">SSL</a>, <a href="#encryption">encryption</a>.</dd> "and" instead of comma here. >diff -U 8 bug221259/original/mail_help.xhtml bug221259/mail_help.xhtml >+ <li><strong>Connection security</strong>: Choose &quot;SSL/TLS if your Are you missing a second &quot; here? >+ news server is configured to send and receive encrypted messages, or None You've not put quotes round None but have round SSL/TLS, be consistent. You're making changes for news server but none for POP or IMAP which need similar changes, please do them all.

BTW, assigning the bug to myself.

(In reply to comment #13) > (From update of attachment 397519 [details] [diff] [review]) > >diff -U 8 bug221259/original/glossary.xhtml bug221259/glossary.xhtml > >+<dt id="secure_connection">secure connection</dt><dd>A connection which uses > >+ some type of encryption (usually, <a href="#ssl">SSL</a>) to ensure it > >+ can&apos;t be intercepted by third-parties. Most of the time, the server is > >+ the one providing the certificate to identify itself.</dd> > What does "the server" refer to? You've not mentioned it elsewhere in this > definition. I've added "between a server and a client": <dt id="secure_connection">secure connection</dt><dd>A connection between a server and a client which uses some type of encryption (usually, Or should it be "a client and a server"? Anyway, would it be enough (in the correct order)? I thought that, although I'm adding this because of mail&news documentation, it could be used for browsing, too, so entering in details about the kind of server was not a good idea. > >diff -U 8 bug221259/original/mail_help.xhtml bug221259/mail_help.xhtml > >+ <li><strong>Connection security</strong>: Choose &quot;SSL/TLS if your > Are you missing a second &quot; here? Yes, I was missing it, sorry. :-) Added there and round SSL/TLS. > You're making changes for news server but none for POP or IMAP which need > similar changes, please do them all. I've done it, but I have to admit that I'm not really sure what is STARTTLS. From what I have just read in Wikipedia LDAP article, is an extension to standard protocols to indicate to the server to enter in TLS without having to use a different TCP/UDP port than for plain connections. I'd really like that someone with more knowledge about it review if what I've ported from the SMTP Server settings is accurate for IMAP and POP. While reviewing it, I've made sure that every option in those panels were described correctly, so I've done some minor edits. But, in POP panel, I'm not sure if this change is accurate: - <li><strong>Until I delete or move them from Inbox</strong>: Choose this - setting to remove messages from the server once you delete them or move - them from your Inbox into another folder.</li> + <li><strong>Until I delete them</strong>: Choose this setting to remove + messages from the server once you delete them or move them from your + Inbox into another folder.</li> I understand that, if you move a message out from Inbox, the POP server will still be reported that the message is no longer in that folder and delete it, and that the change in the checkbox label is due to layout restrictions or aesthetic reasons. If someone can confirm it without me having to actually test it (I'm not using SM2.0 yet to manage my e-mail accounts), he would save me from risking losing e-mails in my SM1.1 profile. :-) TIA

Comment on attachment 398888 [details] [diff] [review] Patch addressing Ian's comments >--- bug221259/original/glossary.xhtml 2009-08-28 00:40:06.000000000 +0200 >+<dt id="secure_connection">secure connection</dt><dd>A connection between a >+ server and a client which uses some type of encryption (usually, Better to have "a client and a server" as the previous entry in the glossary is written in that order. Would be useful to have an entry for STARTTLS in the glossary too (and associated links elsewhere) - what you quoted seemed a reasonable description. >--- bug221259/original/mail_help.xhtml 2009-08-28 00:40:23.000000000 +0200 >+ <li><strong>STARTTLS</strong>: Require an encrypted connection, use the >+ STARTTLS method. This mechanism will mostly run on the standard IMAP >+ port 143.</li> "usually" rather than "mostly" - same elsewhere you have added STARTTLS. >+ <li><strong>Until I delete them</strong>: Choose this setting to remove >+ messages from the server once you delete them or move them from your >+ Inbox into another folder.</li> From bug 226839 which changed the account setting, it does not delete them when moved from the Inbox any more - read that bug for more details.

STARTTLS entry added in glossary.xhtml (and help-glossary.rdf), "mostly" changed to "usually" and "Until I delete them" option description fixed. I'm sorry to giving you extra work, Ian. Thanks for you patience. :-)

Comment on attachment 399124 [details] [diff] [review] New version of the patch fixing Ian's comments in comment #16 >--- bug221259/original/glossary.xhtml 2009-08-28 00:40:06.000000000 +0200 >+<dt id="starttls">STARTTLS</dt><dd>An extension to common standard TCP >+ protocols (like SMTP, POP or IMAP) so the client can tell the server to enter >+ in <a href="#tls">TLS</a> without having to use a different TCP port than for >+ plain connections.</dd> >+ Either ...so the client can tell the server to use TLS without having to use a different TCP port as for non-secure connections. Or ...so the client can tell the server to use TLS on the same TCP port as for non-secure connections. I think the second one sounds better to me. r=me with that change. You will also need to ask for approval‑seamonkey2.0 before it can be pushed to the tree. Thank you for your work. Do you fancy looking at bug 506724 too?

I like second setence more, too. :-) Regarding bug 506724, I can try to have a look to it, although I'm waiting for review in a preliminary (RDF changes pending) to this other bug: https://bugzilla.mozilla.org/show_bug.cgi?id=373457 I asked the review to stefanh to not overload you and create a hatred feeling to me. :-) And I have to translate to es-ES every bug in help I contribute, too. ;-)

Comment on attachment 399314 [details] [diff] [review] Ian's suggestion applied in reviewed+ patch >--- bug221259/original/glossary.xhtml 2009-08-28 00:40:06.000000000 +0200 >+<dt id="starttls">STARTTLS</dt><dd>An extension to common standard TCP >+ protocols (like SMTP, POP or IMAP) so the client can tell the server to enter >+ in <a href="#tls">TLS</a> on the same TCP port as for non-secure >+ connections.</dd> Change "enter in" to "use"

Sorry to have missed the "use" replace. Once approval-seamonkey2.0 is granted, I'll add the "checkin-needed" keyword. That's the right sequence, isn't it?

Comment on attachment 399332 [details] [diff] [review] Patch with "use" instead of "enter in" Yes, that is the next step

Done. :-)

Could you attach an "hg diff" patch?

The patch created by running hg diff. I'm not sure if I should ask again for review and approval. :-?

No additional reviews are needed. You can just carry forward r+ and a+ from attachment 399332 [details] [diff] [review], which has all necessary approvals.

I pushed http://hg.mozilla.org/comm-central/rev/cc8c8f77ca34, but I unfortunately forgot to credit you, Ricardo. So I pushed a whitespace change in http://hg.mozilla.org/comm-central/rev/5323930e3e01 in order to try and correct my mistake. Sorry about this.

(In reply to comment #27) > I pushed http://hg.mozilla.org/comm-central/rev/cc8c8f77ca34, but I > unfortunately forgot to credit you, Ricardo. So I pushed a whitespace change in > http://hg.mozilla.org/comm-central/rev/5323930e3e01 in order to try and correct > my mistake. Sorry about this. No problem, I don't do this to get credit, but to give back to SeaMonkey project. :-) Thank you for pushing it.