Telegram: Skip Posts Forwarded from Other Chats

To skip Telegram messages that were already forwarded into your source chat, turn on the task’s Forwards filter in RedFox Auto Forward Telegram (@AutoForwardNew_Bot). The official Filter By Type guide says enabled filters exclude that type; Forwards ignores messages forwarded from other chats. This selects which whole messages can leave the source. It is not a switch that disables your entire forwarding task.

This guide is for an existing Telegram-to-Telegram route that delivers successfully but carries too many reposts. Your source channel publishes its own updates and also forwards other channels’ posts. You want the direct updates, not those already-forwarded items. Other task rules and delivery permissions still apply to the posts left eligible.

The featured image is a concept illustration of message sorting, not product UI or an executed forwarding test. The checks below are a reader-run procedure based on current documentation.

Start with the message in the source chat

Imagine a community’s Project Updates channel contains two kinds of posts: its editor writes a new release note directly, then uses Telegram’s Forward action to share a partner’s announcement. A separate Team Bulletin should carry the release note but not every partner repost. Apply the exclusion to the task that reads Project Updates and sends to Team Bulletin.

Inspect the message where the task reads it, not only the copy at the destination. A native forward commonly has a “Forwarded from” header, but the visible words alone are not a complete provenance check. Telegram’s flexible-forwarding announcement documents an option to hide the sender’s name. Its message reference also distinguishes forwarded-message origin information from ordinary message text. These platform references explain the distinction; they do not expose RedFox’s internal matching implementation.

• Direct source post: someone composes a new message in the source. It should remain eligible under this one exclusion.
• Native forward in the source: someone forwards a message from another chat into the source. This is the type the documented Forwards filter excludes.
• Copied or retyped material: someone pastes or rewrites words into a new message. Do not expect a forward-type filter to recognize that content as a repost merely because the wording came from elsewhere.

For this workflow, “direct” describes how the message arrived in the source—not proof that its author created the content. If your real requirement is “publish only material we own,” you also need an editorial permissions check. A type filter cannot establish ownership or originality.

Keep source filtering separate from header display

Several controls mention forwarding, but they answer different questions:

• Forwards filter: should a message already forwarded into the source be excluded entirely? Turn this on for the case in this guide.
• Show Forward Header: how should attribution appear on a message that is sent? RedFox’s Forward Header guide documents showing the header on all auto-forwarded messages or only when the source message is also forwarded. That display choice is not a substitute for excluding a source message.
• Keyword rules: should a post qualify because of its text? Use the keyword-filter guide when your policy is about words, not native forward status.
• Repeated-arrival diagnosis: why did the same update reach the target twice? Use the route-overlap checks in the duplicate-message guide. Two delivery paths are a different problem from one source containing native forwards.

Leave the outgoing header choice unchanged while checking this filter. Changing it at the same time makes the result harder to interpret. In particular, a wanted direct source post may still display a forwarded header after your task sends it; that destination appearance does not prove the source-type filter failed.

Enable the exclusion on one controlled task

Use a source and private destination you control, containing harmless material you are allowed to redistribute. If you do not yet have a working route, follow the existing Telegram source-to-destination setup guide first. Do not rebuild a working connection just to change one filter.

1. Bind the route. Open the RedFox Web App or official mobile app. Select the intended task and read its source and target. Record the current filter states, outgoing header choice and task status before changing anything.
2. Open its type filters. The task-settings guide identifies Filter as the task’s message-type control; the type-filter guide calls the area Filters. Locate Forwards for this task, rather than a content keyword rule or a global forwarding switch.
3. Turn Forwards on to exclude. The direction matters: enabled means “ignore this type,” not “allow this type.” Keep unrelated filters unchanged. Finish any save or confirmation shown by your interface, reopen the task and verify that Forwards is still enabled.
4. Check competing paths. Make sure another task is not carrying the same test source into the same destination. A second unfiltered route can deliver the very item your controlled task skipped.
5. Run new specimens. Use the checks below after the setting is saved. Inspect the exact destination; do not treat a task-status label as proof of either delivery or exclusion.

If you use the Telegram-bot entrypoint, the documented navigation is /settings → Manage Forwarding Tasks → select the task → Advanced Configuration → Filter. Web and mobile layouts need not match that command menu. If you cannot find the control, verify the selected account and task, then consult the current product guide rather than toggling a similarly named option.

Check a direct post and a native forward

These are hypothetical specimens and documented expectations, not results we observed in a connected account. Keep the task’s other conditions fixed. A post remaining eligible under Forwards can still be rejected by another filter or fail delivery for another reason.

• A — Direct post. Compose a fresh message in the controlled source: “Bulletin check A: our release note.” Confirm it arrives in the private target. This checks that the route still delivers an ordinary direct post.
• B — Native forward. In a second chat you control, create a different harmless message: “Bulletin check B: partner notice.” Use Telegram’s Forward action to send it into the controlled source, leaving the sender visible for this first exercise. Confirm it is present in the source but does not arrive through the filtered task.
• C — Copy-paste boundary. Copy a different harmless sentence from your own second chat and paste it as a new source post, rather than using Forward. Do not count its arrival as a failure of the Forwards filter: copied wording is not the same classification as a native forwarded message. Use distinct wording so an unrelated duplicate rule does not confuse this check.
• D — Literal phrase control. Type a new source message that includes the words “Forwarded from” as ordinary text. This is not a native forward merely because you typed the label. Check it against your other active text rules instead of treating the phrase as proof of origin.

For each specimen, note how it was created, its source message link or timestamp, the task, the saved Forwards state and what appeared at the destination. Wait through any configured task delay before concluding that an item was excluded. If the result is uncertain, keep it uncertain rather than repeatedly posting the same sample to a real audience.

Use the visible-sender native forward as the basic check. Hidden-sender forwards, albums and automatically forwarded discussion-group posts deserve their own harmless specimens if your actual feed depends on them; do not extrapolate an ordinary text result into a promise about every variant.

If the result does not match the policy

• A and B both arrive: reopen the exact task, verify Forwards is enabled, inspect B in the source and look for another route into the target. A pasted copy or a manual destination repost does not test the intended exclusion.
• Neither arrives: the negative result alone proves nothing. Check that the task is active, still reads the intended source and can post to its target; review other filters and delays. Recover a known direct-post baseline before judging the Forwards control.
• A arrives with “Forwarded from” at the target: inspect the separate outgoing header setting. Judge this filter from A’s source type, not the header added or preserved during onward sending.
• A copied sentence still arrives: revisit the policy. If you need specific authors or announcement keywords, use those documented selection controls. Do not broaden the promise of a native-forward filter into copied-content detection.
• Older reposts remain in the target: this procedure checks new-message selection. It does not establish retrospective deletion or recovery of previously skipped posts.

If the change is unsuitable, pause the affected route before restoring its previous settings. Read back the intended configuration and consider what will become eligible when forwarding resumes. Do not assume a pause or filter change clears queued work or replays earlier skips. Leave unrelated tasks alone.

For unexplained behavior, give product support a sanitized source/target description, task label, saved filter state, specimen creation method and expected versus observed arrivals. Do not send login codes, tokens, passwords or confidential source content.

Keep the feed focused without changing every message

Open one controlled task in Auto Forward Web, enable the Forwards exclusion and verify both sides: a direct post arrives, while a native forward is skipped. Keep the existing output-header policy unless you separately want to change attribution. Once the controlled result fits your needs, apply only that setting to the intended live task and check fresh examples again.

You can also manage the product through its official iOS app or Android app. Choose the surface you prefer; Web and the mobile apps are recommended for fuller management than the limited Telegram-bot entrypoint. Active tasks run in RedFox’s cloud without keeping the management interface open. See the Auto Forward Telegram overview for the wider product workflow.

Auto-Bot.io is an editorial publisher, not the developer or operator of RedFox Auto Forward Telegram. The previous bot has moved to @AutoForwardNew_Bot; use that current handle.

FAQ

Does turning on Forwards allow forwarded messages?

No. The current Filter By Type guide says turning a filter on excludes that message type. Forwards is documented to ignore messages forwarded from other chats.

Can I hide the forward header instead?

That changes presentation, not the policy of excluding an entire source item. Use the Forwards filter for selection and the separate Forward Header controls for the attribution shown on messages you send.

Will this remove every copied or unoriginal post?

Do not use it as an originality detector. A pasted or retyped message is not a native forward just because its wording was copied. Keep permissions and editorial review separate from message-type filtering.