Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On 11/04/2012 16:08, Ferry Toth wrote:
My provider uses TLS on the SMTP server which is on port 25.

When I select that server from LO, check use SSL, type in user name and
password under server verification and the click on test settings I get
the window showing that it passed.

Are you sure TLS is not working? Or is my provider supporting both SSL
and TLS?

Ferry



If I use an email account that doesn't need SSL or TLS then it all works OK - if I use a Gmail account of which the smtp server apparently (according to their website) uses either SSL or TLS on port 465, it immediately becomes un-responsive. (My Gmail accounts work perfectly well in Thunderbird and Outlook!) However that doesn't answer the question "why doesn't mail merge to email call the default email client"? This seems to be absolutely BONKERS. If I use File-Send-Document as email then it DOES call the default email client! BONKERS! Using the mail merge to email function in LO there is NO RECORD of the sent emails anywhere. Even MORE BONKERS!

--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.