Telegram RegisterThe public register of Telegram
Telegram profile photo for mailcow updates (dev)

Channel

mailcow updates (dev)

@mailcowUpdates

On this record: Topic · Growth · Engagement · Posts · Cite this entry

61subscribers

+5 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001657583567
TypeChannel
Username@mailcowUpdates
CreatedBetween 1 December 2021 and 31 May 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live6 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 6 October 2026
On Telegramt.me/mailcowUpdates

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

566158.58 August 2026 — 56 subscribers10 August 2026 — 56 subscribers29 August 2026 — 57 subscribers5 September 2026 — 59 subscribers12 September 2026 — 60 subscribers6 October 2026 — 61 subscribers8 August 20266 October 2026
6 measurements spanning 60 days, net +5. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 55–62 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 18:3861+1
12 Sept 2026, 15:1860+1
5 Sept 2026, 12:4059+2
29 Aug 2026, 08:2357+1
10 Aug 2026, 08:0056no change
8 Aug 2026, 02:4656first reading

Engagement

20 posts held, back to 30 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Aug 2026, 07:01 UTC18 viewsread 10 August 2026

#master #stable update README.md sponsors https://github.com/mailcow/mailcow-dockerized/commit/54da526d418f0bef3f4e9160847dff87cfab0bd6 (author: MaximalBenedikt)

5 Aug 2026, 07:01 UTC18 viewsread 10 August 2026

#master #stable Merge pull request #7392 from mailcow/update-sponsoring update README.md sponsors https://github.com/mailcow/mailcow-dockerized/commit/8b456a33e79fe638af9da473c98af1991adef00d (author: MaximalBenedikt)

5 Aug 2026, 07:01 UTC19 viewsread 10 August 2026

#master #stable update postscreen_access.cidr (#7394) https://github.com/mailcow/mailcow-dockerized/commit/f7a536d63463236973898a2fde7fb686ca82683e (author: milkmaker)

5 Aug 2026, 07:01 UTC19 viewsread 10 August 2026

#master #stable Merge pull request #7393 from mailcow/staging update README.md sponsors https://github.com/mailcow/mailcow-dockerized/commit/06424670fa5d60fee851f58bfc49f66086d5f0a6 (author: FreddleSpl0it)

4 Aug 2026, 16:40 UTC21 viewsread 10 August 2026

#staging update postscreen_access.cidr (#7394) https://github.com/mailcow/mailcow-dockerized/commit/f7a536d63463236973898a2fde7fb686ca82683e (author: milkmaker)

30 Jul 2026, 12:25 UTC40 viewsread 10 August 2026

#staging Merge pull request #7392 from mailcow/update-sponsoring update README.md sponsors https://github.com/mailcow/mailcow-dockerized/commit/8b456a33e79fe638af9da473c98af1991adef00d (author: MaximalBenedikt)

30 Jul 2026, 12:25 UTC38 viewsread 10 August 2026

#staging update README.md sponsors https://github.com/mailcow/mailcow-dockerized/commit/54da526d418f0bef3f4e9160847dff87cfab0bd6 (author: MaximalBenedikt)

30 Jul 2026, 09:17 UTC40 viewsread 10 August 2026

#master #stable Merge pull request #7391 from mailcow/staging Update 2026-07a https://github.com/mailcow/mailcow-dockerized/commit/489db905122d20487e29c9a8438b311c403442ab (author: FreddleSpl0it)

30 Jul 2026, 09:17 UTC33 viewsread 10 August 2026

#master #stable Merge pull request #7390 from mailcow/fix/6859 [ACME] Skip mta-sts certificate request when MTA-STS is not active for a domain https://github.com/mailcow/mailcow-dockerized/commit/50be483c3949300c22b6f40259cc26e3f5deb714 (author: FreddleSpl0it)

30 Jul 2026, 09:17 UTC25 viewsread 10 August 2026

#master #stable [ACME] Skip mta-sts certificate request when MTA-STS is not active for a domain https://github.com/mailcow/mailcow-dockerized/commit/d64c923aca1d80f8e2b73b0664500399a60542e2 (author: FreddleSpl0it)

Showing the 12 most recent of 20 posts we hold for @mailcowUpdates. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 6 October 2026 — this entry's latest reading, not the date you are reading this.

“mailcow updates (dev)” (@mailcowUpdates), 61 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/mailcowUpdates.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.