Bug 41710 - Mail merge configuration wording leads users to use wrong or nonexistent smtp port
Summary: Mail merge configuration wording leads users to use wrong or nonexistent smtp...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.4.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-12 00:48 UTC by Allan Jacobs
Modified: 2012-08-31 10:04 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Allan Jacobs 2011-10-12 00:48:19 UTC
The context for this is
Tools->Options
LibreOffice Writer->Mail Merge E-mail

The wording in the dialog should be 'Use secure connection (TLS)' instead of what is there now: 'Use secure connection (SSL)'.

587 is the usual port assignment for smtp servers that use TLS.  465 is the port assignment when SSL is used. gmail users are normally directed to use SSL port 465.  It takes some detective work to find that TLS is supported at port 587.  Many mail services only provide SSL and do not offer TLS (Yahoo, for example).

The wording of the options dialog does not make the distinction clear and encourages use of LibreOffice with mail servers where it is bound to fail.

If a user attempts the following in LibreOffice:

Use secure connection (SSL) [check]
Port: 465

then LibreOffice will either hang or take a very long time to return with an error message.  Since 465 

If the user attempts:

Use secure connection (SSL) [check]
Port: 587

then LibreOffice will work (provided authentication is set up properly).
Comment 1 Björn Michaelsen 2011-12-23 12:33:50 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 2 sasha.libreoffice 2012-02-04 05:36:31 UTC
@ Allan Jacobs
So, for better understanding, write: 1) what is now written, 2) what will be written
Comment 3 Florian Reisinger 2012-08-14 13:57:52 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 4 Florian Reisinger 2012-08-14 13:59:11 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 14:03:44 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 Florian Reisinger 2012-08-14 14:06:00 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian