Forward filter

Live

Forwarded message filter

Forwarded message filter settings: source types, media handling, allowlists, denylists and punishments.

Set up in the Mini App

Open Settings in your private chat with @defendy_bot, select the group under My groups and check its name at the top.

  1. Open Anti-spam → Forwards.
  2. Expand the source type: channel, group, user, bot or hidden user. Each type has its own settings.
  3. Enable the types you want to filter, then configure message deletion and the member action.
  4. Open the allowlist or blocklist to add exceptions. Choose the source type, enter values or upload a TXT file, then tap Save.

After adding a source, test an actual forward from it. The current filter may compare the channel title or author’s display name instead of the entered ID or @username, so an allowlist entry alone does not guarantee an exemption. A hidden author may have no available ID.

Switches and selectors save when changed. In a separate form with a Save button, save before leaving. If a request fails, reopen the section to check its actual values.

Tip: change one option at a time and verify the result in the group so false positives are easy to spot.

In short

Forward filtering is split by source type because forwards from channels, users, bots and hidden users carry different risk.

How it works

  1. Defendy detects that a message was forwarded and identifies the available source type.
  2. Allowed and blocked sources are checked before the general forward policy.
  3. A matching forward is deleted or punished according to this module's settings.

Every setting explained

Enable per type

Default: Off.

Each source type has its own toggle: channel, group, user, bot and hidden user.

Delete message

Default: On.

Deletes the forwarded message when the rule matches.

Filter media

This switch is visible but currently does not change forward-filter behavior. Do not rely on it as a separate protection or exemption.

Allow the first message

This switch does not currently provide the promised exemption. A member’s first message can still be filtered by the ordinary forward rules.

Allow self-forwards

Default: Off.

For user forwards only: allows members to forward their own messages.

Member action

Default: None.

Choose the response to the member separately from Delete message. None applies no additional member penalty; it does not turn deletion off. For a warning, choose its weight; for a timed mute or ban, check the duration.

Action duration

Initial value: 1 hour (3,600 seconds).

Changing the action can reset the duration to 0. Where supported, 0 means no expiry. Select the intended duration again; a temporary mute lasts at least 60 seconds.

Warning weight

Default: 1 point.

Points added when the selected action is Warning. Existing points can bring the member to a warning threshold.

Practical example

To remove forwards from hidden authors, open Hidden user, enable that filter and message deletion, and leave the member action at None. Send an actual hidden-author forward in a test group: it should be deleted without an additional member penalty. User and channel forwards have separate settings; use the allowlist for your official channel.

Recommendations

  • Use the allowlist for official channels that members are allowed to quote.
  • Hidden-user forwards are usually harder to audit, so configure them deliberately.

Troubleshooting

  • Check that Defendy is still an administrator in the group.
  • Refresh the settings panel and make sure you are editing the correct group.
  • If a setting is saved but does not work, check the bot permissions in Telegram.
  • If logging is connected and the relevant category is enabled, check the event record. The log cannot show events that were not recorded.

Check the duration after changing an action

Changing the punishment type can reset its duration to 0. Where supported, zero means an indefinite action, not a disabled punishment. A temporary mute lasts at least 60 seconds. Recheck the duration before leaving the form.

Need help?

If a setting behaves differently than expected, contact support.@ubotz