Groups.io: Changelog

Subscribe via RSS

Area All areas Messages & Topics Editor & Drafts Hashtags Email & Delivery Members Moderation Group Settings Subgroups Integrations Calendar Files Photos Wiki Databases Chat Ask Subscription Account & Login Billing Enterprise Design & Accessibility Public Pages & Help Mobile App Site-wide

Type All types New Change Bug fix API

Search

Filter Clear

---

October 16, 2026

Email & Delivery

• BUGFIX: Replies sent to the moderators from the website never reached them. The message was rejected by our own mail server, so only the BCC Me copy, if requested, was delivered, even though the website said it had been sent. Because the message never arrived, it was also missing from the member's Owner Messages history and from the Activity log. Replies to the moderators are now delivered to them with the [Owner] and group tags in the subject, saved in the member's Owner Messages history, and logged in the Activity log, like a message sent to the group's +owner address by email. https://beta.groups.io/g/main/message/41439
• BUGFIX: Some email providers send vacation and out-of-office replies to the address group messages are sent from, which is used to collect bounces, instead of the group. Each of those replies was recorded as a bounce for the member, showing "Unable to parse bounce message" in their Email Delivery History. Auto-replies are now ignored and no longer counted as bounces.

October 2, 2026

Email & Delivery

• BUGFIX: Messages sent to a group from Proton Mail, and occasionally from other email providers, were sometimes bounced with "Invalid request, no reverse DNS", even though the sending server was set up correctly. It happened when a lookup of the sending server's name briefly failed on our end. A brief lookup failure now asks the sending server to try again later instead of bouncing the message, and we check with a second, independent DNS service before treating the lookup as failed.
• BUGFIX: Since September 30, some messages sent to a group from iCloud (me.com, icloud.com, mac.com) were delivered with a large block of raw, encoded text instead of the formatted message, and failed DKIM checks at Gmail. iCloud began adding stray characters to one of its message headers, and we passed them on to members, which made Gmail and other email programs think the headers ended early. We now remove those characters when a message arrives, so iCloud messages display normally.
• BUGFIX: When a member's Yahoo Mail account automatically forwarded to another address that rejected the message, the bounce recorded for the member just said "5.0.0", with no hint of the real cause. Yahoo had changed the format of these forwarding failure notices. The bounce now shows the forwarding address and the reason it was rejected, for example that the account doesn't exist, so members and moderators can tell that the problem is the forward and not the member's Yahoo address.
• BUGFIX: When a member with a group signature replied by email from a program that doesn't mark the earlier message as a quote, such as Samsung Email or Outlook, their signature was hidden on the website in the collapsed "..." along with the earlier message, because the signature was added at the very end, after the earlier message. When a reply is written above the earlier message, the signature is now added between the reply and the earlier message, where email programs put signatures. A signature that still ends up after the earlier message is now recognized and shown. Messages already posted are unchanged. https://beta.groups.io/g/main/message/41335

September 25, 2026

Email & Delivery

• CHANGE: Digest and daily summary sender names could be ambiguous when different groups used the same subgroup name. They now use the standard breadcrumb naming, such as Beta | Main Digest and Beta | Main Summary. https://beta.groups.io/g/main/message/41233
• CHANGE: HTML digests were larger than they needed to be. Gmail cuts off any message over about 102KB and shows a "View entire message" link, and a digest could reach that size after only five or six messages. Everything after the cut was missing, including the messages that the Topics in this digest links jump to. Digests are now about 40% smaller, so many more messages fit before Gmail cuts them off. Digests look exactly the same as before.

September 11, 2026

Email & Delivery

• BUGFIX: Some bounce messages from Exim mail servers showed only a generic error code instead of the delivery failure explanation. We now extract the detailed error from these messages and correctly identify mailbox-full errors as quota failures.

September 4, 2026

Email & Delivery

• BUGFIX: The links in the Topics list at the top of the HTML digest did nothing for members reading AOL mail in Firefox, because each link's target was marked with only the older name attribute, which that combination ignores. The targets now also carry an id attribute, so the topic links, and the "Top" link at the end of each message, work there. https://beta.groups.io/g/main/message/41142

August 29, 2026

Email & Delivery

• BUGFIX: The "view all your groups" links at the top of HTML digests and daily summaries, and in the default Welcome notice, pointed at the site home page — which took logged-in members to whatever page they last used as their home view instead of their groups list, and showed logged-out members the front page. Those links now go directly to the Your Groups page, and if you are logged out, you are prompted to log in and then taken there. https://beta.groups.io/g/main/message/41020
• BUGFIX: The check that blocks executable files inside archive attachments — which Gmail and most other providers reject outright, for every recipient — decided whether an attachment was an archive from its file name. An archive renamed to a different extension (a .zip sent as .zip.xxx, with a note telling recipients to rename it back) slipped past the check, so the message was accepted and distributed, and then rejected by every provider that looked inside — half the group never received it, with no indication to the sender that anything had gone wrong. Attachments are now recognized as archives by their content, whatever the file name, including archives nested inside other archives, and such messages are returned to the sender at posting time with the usual executable-attachment notice.
• INTERNAL: Related: an executable renamed to an innocuous extension — attached bare or placed inside an archive — still passes the name-based checks but is likewise rejected by providers that inspect content. Messages are now scanned for Windows, Linux and Mac executable content behind misleading names at posting time; detections are logged but not yet enforced while the detector's accuracy is confirmed against real traffic.