Bug 132196 - Rewrite of mailmerge.py
Summary: Rewrite of mailmerge.py
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: contrib (show other bugs)
(earliest affected) release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
Depends on:
Blocks: Macro-Python
  Show dependency treegraph
Reported: 2020-04-17 15:32 UTC by prrvchr
Modified: 2021-09-23 03:34 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description prrvchr 2020-04-17 15:32:43 UTC
I would like to contribute to the rewriting of mailmerge.py in order to make it functional again with new features.

In new features we can see:
- integration of Mozilla IspDB to make configuration easy.
- support for different encryption systems (TLS, SSL, None...)
- support for different authentication (OAUTH2, CRAM-MD5, PLAIN, LOGIN ..)

Rewriting mailmerge.py requires modifying the IDL files involved.
And I don't have a global vision of the uno API to be able to make these changes without help...

Do you feel ready to do something?
Thank you
Comment 1 Xisco Faulí 2020-04-17 16:37:00 UTC
@Ilmari, Do you think the reporter should send an email to the dev mailing list exposing the idea first ?
Comment 2 Buovjaga 2020-04-17 16:45:42 UTC
(In reply to Xisco Faulí from comment #1)
> @Ilmari, Do you think the reporter should send an email to the dev mailing
> list exposing the idea first ?

Yes. It would also be a good idea to split the effort into sub-tasks, different Bugzilla report for each.
Comment 3 Julien Nabet 2020-04-17 16:51:26 UTC
prrvchr: it seems you'd like to contribute to LO, great!
However, don't multiply tasks, you already submitted tdf#132195

Focus on one task and start from the beginning:
retrieve LO code then try to build it.
(see https://wiki.documentfoundation.org/Development/GetInvolved)
Comment 4 prrvchr 2020-04-17 18:31:21 UTC
(In reply to Julien Nabet from comment #3)

> However, don't multiply tasks, you already submitted tdf#132195

Do not think that i multiply the tasks, it is just that i would like to carry out my project, and to finish it, it is necessary that I deal with these two things.
Comment 5 prrvchr 2021-01-11 22:07:48 UTC
Hi all,

I did half the way:

Now we have a new Wizard accessible by Tools -> Options -> Internet -> smtpServerOOo with the smtpServerOOo extension (https://prrvchr.github.io/smtpServerOOo/) which is able to return the configuration of an SMTP server from your email address (thanks to Mozilla IspDB technology)
I am in the process of registering with Google so that the OAuth2OOo extension is approved to use the scope necessary for the SMTP connection. Google seems reluctant, it would like me to use their API with a more restricted scope. It is out of the question that I use the Google API, because I want to be multi-provider and therefore use the Python smtplib library. Maybe it will end with the help of the CNIL, if I do not succeed.

I still have to write a mail spooler, because I would like the mail to be sent in the background in order to be able to do mass sending (mail merge) and I am looking for some help and good idea for this famous spooler...

Comment 6 Julien Nabet 2021-01-12 16:49:56 UTC
(In reply to prrvchr from comment #5)
> ...
> Maybe it will end with the help of the CNIL, if I do not succeed.
> ...
You're relying on French administration! Unless CNIL is an exception, what a dreamer! :-) (I'm French)
Comment 7 prrvchr 2021-01-13 09:45:49 UTC

In order to speed up the registration process with Google, so that the OAuth2OOo / smtpServerOOo extension is approved to use the necessary scope (https://mail.google.com/) for the SMTP connection, it would be a good idea, that the LibreOffice Team help me with this, by sending an email to Google.

Because if I have to involve the CNIL, I enter into a very long procedure (the CNIL takes 4 months to open a request, and I think twice about it to process it)

I want to point out that:

- All my extensions do not collect any data and were produced so that the end user can use this data present in GAFA in a Free Software.

- OAuth2OOo / smtpServerOOo is one of the types of applications that can access Restricted Scopes for Gmail (see the end at section: Restricted Scopes of Google API Services User Data Policy available at: https://developers.google.com/terms/api-services-user-data-policy

If you are ready to help me, I will give you the Google email address to contact for this request (perhaps with a private message).

Thank you

Comment 8 Julien Nabet 2021-01-13 11:31:34 UTC
I don't know at all if TDF can do something. There are already pbs about dev workforce (Base in general but not only, accessibility part too, MacOs pb with 10.15, ...) and no reaction from them.

It seems it will be a David (you) vs Goliath (Google and/or CNIL) episode.
I can't help here => uncc myself.
Good luck!
Comment 9 Xisco Faulí 2021-02-23 09:34:04 UTC
Hi prrvchr@gmail.com,
are you working on this issue? should it be assigned to you ?
Comment 10 QA Administrators 2021-08-23 03:51:57 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2021-09-23 03:34:41 UTC
Dear prrvchr,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team