Bug 155854 - Mail Merge hangs after connecting to the mailserver
Summary: Mail Merge hangs after connecting to the mailserver
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.3.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Mail-Merge
  Show dependency treegraph
 
Reported: 2023-06-15 13:23 UTC by Bernard Decock
Modified: 2023-06-25 12:02 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 Bernard Decock 2023-06-15 13:23:01 UTC
Description:
Mail Merge hangs when it starts sending e-mails. I set the dbg variable in mailmerge.py True. The logging reveals that a connection is made with the SMTP-server and the connection is acknowledged. The logging ends with
reply: b’235 2.0.0 OK Authenticated\r\n’
reply: retcode (235); Msg: b’2.0.0 OK Authenticated’
PyMailSMTPService isConnected
XSL Vendor: ‘libxslt’
After a while a notification pops up that LO is unresponsive. It looks that something goes wrong while parsing the info into data to be emailed.
I have this behavior on 3 computers with Linux Mint 21.1 Cinnamon. I installed Ubuntu 23.04 in a virtual machine and Mail Merge started working fine in the VM.
Is this a known bug in Version: 7.3.7.2 / LibreOffice Community
Build ID: 30(Build:2)?

Steps to Reproduce:
1. Open the Mail Merge Wizard
2. Configure
3. Request to send the emails

Actual Results:
LO Hangs

Expected Results:
LO is unresponsive and shuts down after selecting to terminate the app. It tells afterward that the documents have to be recovered, although they haven't been changed.


Reproducible: Always


User Profile Reset: No

Additional Info:
It should the proper email
Comment 1 Bernard Decock 2023-06-25 08:57:50 UTC
Problem solved with LO 7.5.4.2
Comment 2 Aron Budea 2023-06-25 12:02:24 UTC
Let's use state WORKSFORME, as the fixing change isn't known.