Bug 117624 - error in mail merge when sending emails
Summary: error in mail merge when sending emails
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Mail-Merge
  Show dependency treegraph
Reported: 2018-05-15 14:20 UTC by Francesco Pagano
Modified: 2019-11-12 23:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

the screenshot (239.62 KB, image/png)
2018-05-15 14:25 UTC, Francesco Pagano
the document (512.76 KB, application/vnd.oasis.opendocument.text)
2019-01-11 16:44 UTC, Francesco Pagano
list of email addresses (11.51 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-01-11 16:45 UTC, Francesco Pagano

Note You need to log in before you can comment on or make changes to this bug.
Description Francesco Pagano 2018-05-15 14:20:39 UTC
I want to send by email a personalized document to a list of customers.
Following https://wiki.documentfoundation.org/images/3/3c/WG4211-UsingMailMerge.pdf, I created the plain document using Writer and I made the list of recipients using Calc. If I run the mail merger to create a printed version all is ok, but when I asked to send te document by email a lot of difficulties arose:
1) since I am using SMPTP_SSL, I had to make the changes described in https://cgit.freedesktop.org/libreoffice/core/commit/scripting/source/pyprov/mailmerge.py?id=036b51dbc49b533d1db773d8627d56ab86bca487
2) each document is sent to the email address of the next row in the database
3) even if I asked to not use a greeting, a standargreeting was added on top of the email.
I am using Libreoffice for Windows (10) Version: (x64) Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf.

Steps to Reproduce:
1. create a document in Writer
2. create a list in Calc
3. run the mail merge requesting to send an email to all

Actual Results:  
The email is sent to the email address of the next row

Expected Results:
The email is sent to the email address of the actual row

Reproducible: Always

User Profile Reset: No

Additional Info:

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Comment 1 Francesco Pagano 2018-05-15 14:25:17 UTC Comment hidden (obsolete)
Comment 2 Francesco Pagano 2018-05-15 14:37:08 UTC
(In reply to Francesco Pagano from comment #1)
> Created attachment 142113 [details]
> the screenshot

I correct myself: the third point was my mistake.
Comment 3 Alex Thurgood 2018-05-17 07:00:24 UTC
Not a Base module problem generally, these bugs are reported against Writer (or the scripting component).
Comment 4 Xisco Faulí 2018-06-18 16:39:51 UTC
Dear Francesco Pagano,
Thank you for reporting the bug. To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 5 QA Administrators 2019-01-11 15:22:58 UTC Comment hidden (obsolete)
Comment 6 Francesco Pagano 2019-01-11 16:44:24 UTC
Created attachment 148240 [details]
the document
Comment 7 Francesco Pagano 2019-01-11 16:45:04 UTC
Created attachment 148241 [details]
list of email addresses
Comment 8 Francesco Pagano 2019-01-11 16:47:42 UTC
The bug is still here. I have attached the master document and the mail list to verify the bug. I needed to insert a fake row "finto" to realign email address with the right owner.
Comment 9 Xisco Faulí 2019-07-31 11:55:03 UTC
A new major release of LibreOffice is available since this bug was reported.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 10 Francesco Pagano 2019-11-12 17:39:07 UTC
Now it seems good, thanks.
Comment 11 Xisco Faulí 2019-11-12 23:42:30 UTC
(In reply to Francesco Pagano from comment #10)
> Now it seems good, thanks.

Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.