HabrSeptember 8, 2026🇷🇺Translated from Russian

Yandex 360 Email Archive Documentation Shows Search Snapshots and Former Employee Log Filters

The Yandex 360 administrator documentation defines the email archive as a feature that preserves copies of every message sent or received by employees whose mailboxes belong to the organization's domain. Once enabled, the archive continues to retain messages even if the original owner deletes them from their mailbox. The guide explicitly warns that messages deleted before the archive was turned on cannot be restored.

Search functionality is implemented as named objects rather than live queries. The documentation states: “Each search runs once. The results do not update as employees send and receive new messages.” Administrators must either create a new search with identical parameters or use the “Clone search” button and adjust the date range to obtain fresh results. No method exists in the documented Yandex 360 API to automate this process.

The action log records every interaction with the archive and promises that “you can always see who searched for what.” However, the employee filter only lists active accounts. The documentation advises that if an administrator has left the organization, their actions cannot be selected by name in the filter and other criteria such as event type and time period must be used instead.

Additional constraints listed in the FAQ section include the permanent loss of messages belonging to fully deleted accounts and the exclusion of any mail from mailboxes that were imported rather than created on the organization's domain. These documented limitations affect routine tasks such as retrieving correspondence of a departed employee or reconstructing an audit trail after an administrator departure.

Related articles

HabrPolicy & Regulation

Global AI Regulation: From Strict School Bans to Unregulated AI Havens

Countries are adopting sharply different approaches to AI oversight, ranging from comprehensive risk-based frameworks to outright prohibitions on generative tools in education. The United States relies on a patchwork of state laws and presidential actions, including Texas TRAIGA restrictions on high-risk AI systems and New York’s moratorium on generative AI in grades 2–8. The European Union enforces the AI Act with four risk categories, while Italy adds criminal liability and human oversight requirements in critical sectors. Norway and China have implemented some of the strictest classroom and content-authenticity rules, and Russia introduced its first baseline AI law defining sovereign models effective September 2026. Several nations have also blocked popular chatbots such as ChatGPT, DeepSeek, and Grok. Meanwhile, commercial platforms like FinamX continue integrating multiple AI models into financial workflows despite the regulatory tightening.

HabrPolicy & Regulation

How Russian Companies Can Legally Transfer Personal Data to Contractors Under 152-FZ

The article explains the legal distinction between data processors and independent operators when outsourcing tasks involving personal data. It details that the role of a contractor is determined by who sets the processing purpose, not by the service contract itself. For processors, a detailed data processing instruction under Article 6 of 152-FZ is required, while independent operators need a separate legal basis such as consent or contract performance. Special rules apply to employee data under Article 88 of the Labor Code, mandating written employee consent for transfers to third parties. The guidance also covers sub-processing risks, transparency obligations, and penalties under Article 13.11 of the Code of Administrative Offenses. Practical checklists help organizations classify contractors and prepare the correct documentation.

AntiMalwarePolicy & Regulation

Russian Data Centers May Face Temporary State Management Under Decree 604 for Protection Shortfalls

Large Russian data centers could be placed under temporary government administration if they fail to meet security requirements outlined in presidential decree No. 604. The measure targets critical infrastructure operators that neglect physical and cyber protections, create operational risks, or respond slowly to incidents such as drone strikes. Rosimushchestvo would typically assume management duties by default. Market participants note that Tier III and higher facilities generally maintain strong cyber defenses, shifting the main compliance burden to physical safeguards for generators, cooling systems, and network nodes. Operators including RTK-DC and RUVDS have already begun reviewing and upgrading external equipment protection. Additional costs for redundant communications, DDoS mitigation, vulnerability management, and faster recovery are expected to be passed on to clients in government, finance, and telecom sectors. First Deputy Prime Minister Denis Manturov stated that decisions will remain targeted and will not trigger widespread nationalization.

AntiMalwarePolicy & Regulation

iMazing 3.6.3 Restores Sideloading of Removed iOS Apps via macOS After Apple Authentication Changes

Developers of iMazing have released version 3.6.3 that restores the ability for users to download and install applications previously removed from the App Store onto iPhone devices. The update currently functions only through macOS, with Windows support still pending further development. The changes address authentication and download errors that appeared in macOS 26 and earlier versions following modifications by Apple to its CommerceKit system. Apple began returning HTTP 403 Forbidden responses to tools including iMazing, ipa_downloader, and 3uTools by deactivating legacy tokens and revoking certificates used for app authentication. The restrictions have particularly affected Russian users who relied on these tools to reinstall banking and other applications removed due to sanctions. Support for macOS 27 Golden Gate and Windows remains unavailable and requires additional engineering work.