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


I had cause the other day to do a Mail Merge to Email in Writer.
I was horrified to discover that the Mail Merge to Email function does NOT call the default email client, but uses an in-built smtp function within Writer. The major problem with that as far as I can see is that there is NO RECORD ANYWHERE of the emails sent by that process. Surely in the days of Sarbanes-Oxley and other legislation that is an appalling omission? Wouldn't it be far easier to call the default email client rather than use some in-built sending mechanism, just like it does if you use the File-Send-Document as Email?

Secondly (and this is a usage comment not a plea for a change of function!)) using a Gmail account in this function causes LO to become non-responsive - it doesn't like the SSL function....


--

Registered Linux User no 240308
GBP's alternative computing:http://gbplinuxfoss.blogspot.com/
Say No to OOXMLhttp://www.linuxjournal.com/article/9594#mpart8
I only accept odf or pdf documents by email


--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.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.documentfoundation.org/www/discuss/
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.