Export messages as file feature requires use of email

[Gummikavalier]

Description:

Export messages as file feature requires use of email. When email is not enabled on the server, users do not get the link where to download their exported messages.

In some instances sending emails is completely disabled for security reasons such as that messages could leak information via downgraded plain SMTP protocol supported in email routing.

It would be preferable that when the user selects Export as file method, the download would be offered directly to the user in UX.

Steps to reproduce:

1. Go to channel you want to export message from
2. Select Export Messages from the three dot menu on the channel
3. Select Method as Export as file
4. Define time range of messages and output format
5. Press Export

Expected behavior:

User is offered a visible download link to the zipped file containing their requested messages, or the download is offered to browser directly.

Actual behavior:

User gets a popup telling them that Your email has been queued for sending. User does not get the email as it is not allowed on the server. User has no way of finding out where to download the exported messages.

Server Setup Information:

• Version of Rocket.Chat Server: 3.8.1
• Operating System: CentOS7
• Deployment Method: tar
• Number of Running Instances: 20
• DB Replicaset Oplog: yes
• NodeJS Version: 12.18.4
• MongoDB Version: 3.6

Client Setup Information

• Desktop App or Browser Version: Chrome or Firefox

[Gummikavalier]

Additional note:
Lack of download link directly in the UX also leads to situations where the desktop client user gets Forbidden 403 error message when clicking the link in email. The link tries to open up in the browser instead of desktop client.

[Bengrunt]

Additional note:
Lack of download link directly in the UX also leads to situations where the desktop client user gets Forbidden 403 error message when clicking the link in email. The link tries to open up in the browser instead of desktop client.

Hello, we do have the same issue. Clicking the generated link that you receive gets you a 403 error.
Additionally, we use S3 as a backend and I can't seem to find the generated file with my S3 client either.

[berardin]

With Rocket.Chat Version 3.15 still the Issue is there.

Do you have any News about it?

Thank you

[emikolajczak]

I have created feature request which problem description RocketChat/feature-requests#496

[dyogaharshitha]

.take