Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Messages with URLs not being delivered to Telegram from Rocketchat via Matrix-Telegram bridge #925

Open
AnonC0DER opened this issue Jul 22, 2023 · 1 comment

Comments

@AnonC0DER
Copy link

Issue Description:

I am using the turt2live/matrix-bot-sdk library to transfer messages from Rocketchat to a Matrix-Telegram bridge. However, I am facing an issue where certain messages, especially those with URLs, are successfully delivered to Element (Matrix client) but fail to reach Telegram. Unfortunately, I am unable to determine the cause of the problem, making it difficult to reproduce at will.

Steps:

  • Set up the turt2live/matrix-bot-sdk for message transfer between Rocketchat and a Matrix-Telegram bridge.
  • Send a message from Rocketchat that contains a URL.
  • Observe that the message is successfully received in Element (Matrix client).
  • Check Telegram for the same message.
  • Notice that the message is not delivered to Telegram.

Expected Behavior:

  • Messages containing URLs should be successfully transferred from Rocketchat to both Element and Telegram.

Actual Behavior:

  • Messages containing URLs are successfully delivered to Element but fail to reach Telegram.

Additional Information:

  • Version of turt2live/matrix-bot-sdk: 0.5.19
  • I have checked several groups in Telegram ensure that permissions are not causing the problem, but they do not appear to be the issue.
@tulir
Copy link
Member

tulir commented Jul 22, 2023

Those steps don't contain anything useful, the event source and/or bridge logs are required.

Also note that m.notice bridging is disabled by default if you're sending those https://github.com/mautrix/telegram/blob/v0.14.1/mautrix_telegram/example-config.yaml#L450-L456

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants