Rita HouJunior EditorRita HouJunior EditorPublished06 June 2025TagsArt-To-Experience Contest: A Creative Challenge by Emperia and 80 LevelJoin TodaySlime Lab playtests will start soon.Indie developer Retrocell has shared a clip from their upcoming VR game called Slime Lab, developed for Quest 2, Quest 3/3s, and PCVR. The footage showcases precise and satisfying cutting and dying mechanics: As the owner of a slime lab, you'll need to fulfill customer orders and match them as best as you can. Besides headphones, there might be other things to make, like the slime cake shown in this video. The end of the clip literally makes me laugh when you slap the cake onto the customer's face and give yourself a big thumbs-up for doing so. Here's another video demonstrating color mixing in our VR slime game. It gives the sensation of blending different colored doughs and watching them slowly transform into a new color. "Experiment with fluid physics to create endless combinations using unique colors and charms," reads the game's description. Like in reality, you can also add glow effects and tweak the stickiness. Your tools need to be upgraded, and more supplies should be ordered in a timely manner. The better your setup, the more you can create.The developer says that they're looking for playtesters. If you’re interested, join its Discord server to apply when the playtest is ready and don't forget to wishlist the game on your preferred platform.Don't forget to join our 80 Level Talent platform and our new Discord server, follow us on Instagram, Twitter, LinkedIn, Telegram, TikTok, and Threads, where we share breakdowns, the latest news, awesome artworks, and more.

You are the Destined One. Black Myth: Wukong is coming August 20. Pre-order begins June 18!

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. Microsoft 365 Word gets SharePoint eSignature, now you can ditch third-party signing tools Paul Hill Neowin @ziks_99 · Jun 6, 2025 03:02 EDT Microsoft has just announced that it will be rolling out an extremely convenient feature for Microsoft 365 customers who use Word throughout this year. The Redmond giant said that you’ll now be able to use SharePoint’s native eSignature service directly in Microsoft Word. The new feature allows customers to request electronic signatures without converting the documents to a PDF or leaving the Word interface, significantly speeding up workflows. Microsoft’s integration of eSignatures also allows you to create eSignature templates which will speed up document approvals, eliminate physical signing steps, and help with compliance and security in the Microsoft 365 environment. This change has the potential to significantly improve the quality-of-life for those in work finding themselves adding lots of signatures to documents as they will no longer have to export PDFs from Word and apply the signature outside of Word. It’s also key to point out that this feature is integrated natively and is not an extension. The move is quite clever from Microsoft, if businesses were using third-party tools to sign their documents, they would no longer need to use these as it’s easier to do it in Word. Not only does it reduce reliance on other tools, it also makes Microsoft’s products more competitive against other office suites such as Google Workspace. Streamlined, secure, and compliant The new eSignature feature is tightly integrated into Word. It lets you insert signature fields seamlessly into documents and request other people’s signatures, all while remaining in Word. The eSignature feature can be accessed in Word by going to the Insert ribbon. When you send a signature request to someone from Word, the recipient will get an automatically generated PDF copy of the Word document to sign. The signed PDF will then be kept in the same SharePoint location as the original Word file. To ensure end-to-end security and compliance, the document never leaves the Microsoft 365 trust boundary. For anyone with a repetitive signing process, this integration allows you to turn Word documents into eSignature templates so they can be reused. Another feature that Microsoft has built in is audit trail and notifications. Both the senders and signers will get email notifications throughout the entire signing process. Additionally, you can view the activity history (audit trail) in the signed PDF to check who signed it and when. Finally, Microsoft said that administrators will be able to control how the feature is used in Word throughout the organization. They can decide to enable it for specific users via an Office group policy or limit it to particular SharePoint sites. The company said that SharePoint eSignature also lets admins log activities in the Purview Audit log. A key security measure included by Microsoft, which was mentioned above, was the Microsoft 365 trust boundary. By keeping documents in this boundary, Microsoft ensures that all organizations can use this feature without worry. The inclusion of automatic PDF creation is all a huge benefit to users as it will cut out the step of manual PDF creation. While creating a PDF isn’t complicated, it can be time consuming. The eSignature feature looks like a win-win-win for organizations that rely on digital signatures. Not only does it speed things along and remain secure, but it’s also packed with features like tracking, making it really useful and comprehensive. When and how your organization gets it SharePoint eSignature has started rolling out to Word on the M365 Beta and Current Channels in the United States, Canada, the United Kingdom, Europe, and Australia-Pacific. This phase of the rollout is expected to be completed by early July. People in the rest of the world will also be gaining this time-saving feature but it will not reach everyone right away, though Microsoft promises to reach everybody by the end of the year. To use the feature, it will need to be enabled by administrators. If you’re an admin who needs to enable this, just go to the M365 Admin Center and enable SharePoint eSignature, ensuring the Word checkbox is selected. Once the service is enabled, apply the “Allow the use of SharePoint eSignature for Microsoft Word” policy. The policy can be enabled via Intune, Group Policy manager, or the Cloud Policy service for Microsoft 365 Assuming the admins have given permission to use the feature, users will be able to access SharePoint eSignatures on Word Desktop using the Microsoft 365 Current Channel or Beta Channel. The main caveats include that the rollout is phased, so you might not get it right away, and it requires IT admins to enable the feature - in which case, it may never get enabled at all. Overall, this feature stands to benefit users who sign documents a lot as it can save huge amounts of time cumulatively. It’s also good for Microsoft who increase organizations’ dependence on Word. Tags Report a problem with article Follow @NeowinFeed

Corsair Overhauls Prebuilt, 3-Chamber Airflow Case, & Transparent PSUJune 5, 2025Last Updated: 2025-06-05We take a look at Corsair’s upcoming i600 pre-built PC, Air 5400 case, Frame 4000D prototype, and moreThe HighlightsCorsair’s i600 pre-built PC is a new revision on the company’s i500 and overhauls its GPU cooler and CPU radiatorThe Corsair Air 5400 is an airflow-targeted case that has air ducts on the top and bottom of its chassisCorsair has partnered with Singularity to develop the Frame 4000D prototype, which has an interesting power board that handles cable managementTable of ContentsAutoTOC Grab a GN Tear-Down Toolkit to support our AD-FREE reviews and IN-DEPTH testing while also getting a high-quality, highly portable 10-piece toolkit that was custom designed for use with video cards for repasting and water block installation. Includes a portable roll bag, hook hangers for pegboards, a storage compartment, and instructional GPU disassembly cards.IntroWe visited Corsair’s suite at Computex 2025 and liked some of the stuff the company had to show. Editor's note: This was originally published on May 21, 2025 as a video. This content has been adapted to written format for this article and is unchanged from the original publication.CreditsHostSteve BurkeCamera, Video EditingMike GaglioneVitalii MakhnovetsWriting, Web EditingJimmy ThangCorsair Air 5400Corsair will release its Air 5400, which is an airflow-targeted case. On the back side of the case is a giant hole, which couples with a front-mounted radiator that will allow the case to shove air straight out of it. This design allows it to focus air flow for the GPU entirely from its own set of fans at the bottom of the case. This is probably the most interesting case from Corsair we saw at Computex this year. It should be around $220, though that’s dependent on the everchanging tariff situation. Internally, the Air 5400 has a duct at the bottom where the case has 3x120mm fans (the entire case is actually set up to support all 120mm fans, which simplifies things). The duct is there to guide air into the GPU. Corsair claims that the case is getting about a 1-2 degree improvement with the duct in a like-for-like test. If you do end up with a front radiator, then a potential area that gets abandoned in terms of airflow might be around the VRM area and some of the board components like system memory.  There are mounts for fans up on top of the case along with an additional duct. Looking at the back of the case, there are 2 holes on the back, which is surprising for a 120mm fan. The spacing doesn’t look like it would fit a 120mm fan, but Corsair’s plan is to include a bracket that would adapt a 120mm fan here and would actually cut out into the glass area on the back, which would make you lose about 40% of the fan. This should help but raises some questions about whether it may cause acoustic issues when you partially blast air into a glass wall. Speaking of glass, the Air 5400’s glass is laminated. A couple companies are doing this now. Corsair says this helps the glass stay more put together to prevent shattering. Looking at the back side panel, there’s a big acrylic sheet coupled with an area where air can escape. Opening up the back panel, there’s a huge amount of cable-management depth. You can also see that the motherboard tray is punctured all of the way through. This causes concerns around structural rigidity, but Corsair is using a .8mm thick steel, which helps a little bit here. The company has also strengthened the case’s top panel compared to Corsair’s 4000D case, which received negative feedback in that area. The Air 5400 is set to be priced at $220 with 3x120mm fans included. i600 Grab a GN15 Large Anti-Static Modmat to celebrate our 15th Anniversary and for a high-quality PC building work surface. The Modmat features useful PC building diagrams and is anti-static conductive. Purchases directly fund our work! (or consider a direct donation or a Patreon contribution!)Corsair is updating its i500 pre-built PC, which we hated, with its upcoming i600, and the company has improved it a lot. The i500’s GPU cooling solution had basically no contact with any of the power components. The i600, on the other hand, has massive overhauls here. The case itself has only slightly changed, but the changes made accommodate larger radiators. The block for the video card, including the power components, is totally different in a way that looks promising. The stuff that jumped out to us right away about the i600 is the fin stacks for the VRM, which is connected to a shared copper nickel-plated base plate for the GPU and memory. Everything is connected to the same base plate, which is connected to the liquid cooler. This means all of the heat gets dumped into the liquid cooler. There’s pros and cons to this design. The pro is that all of the other components get cooled better. The downside is that the GPU itself is sharing the heat dissipation capacity with all of the other components in the cooler. This means you typically see some increase in the GPU temperature as a result. There’s ups and downs to this approach. It doesn’t necessarily mean one solution is better than the other as long as it’s all cooled. The i600 has copper bars, which contact the MOSFETs. Otherwise, it’s very similar to the i500. Corsair has also modified its CPU cooler radiator, where the company has moved its tanks off to the side. The tubes are also running in a different direction. Corsair is also moving to 25mm thick fans, where previously they had the slimmer 15mm fans. That extra 10mm will help with pressure and performance a lot. We plan on doing a review of the PC as soon as we buy one.Corsair Frame 4000DWe saw a prototype of Corsair’s Frame 4000D, where the company changed a few things. Corsair partnered with Singularity for its powerboard. It’s somewhat similar to Elmore’s BENCHLAB, with the exception of it not logging power. With the case, you basically run all of the power cables into the power board and then route them to their final locations. We count 10 fan headers here along with a bunch of RGB headers. There’s a lot of possibilities with this. Currently, it’s mostly being used as a cable-management tool, but you could, in theory, expand this to include more switches, like fan-control switches. We would really like to see current monitoring. It would make it more expensive but that could be a potentially useful direction to go in where you could monitor on the 12VHPWR, for instance, which would become a great marketing point for Corsair and would be very useful for end users. The front panel is also different as it has a die-cut edge now.  The power supply setup is also different here with Corsair doing an acrylic wall for the PSU instead of steel. The challenge here is that plastic is an incredibly good insulator. This could raise some ESD (electrostatic discharge) concerns and may cause the PSU to lose some of the shielding that steel provides. As a part of this design, Corsair has customized the caps and PCBs so that they get nice color matching. It looks pretty nice. 3D PrintingCorsair was telling us how for its upcoming 4000D and its Frame series cases, it was getting into 3D printable panels and pieces. They showed us how one Corsair employee 3D printed a shroud-like duct, which takes air in through the bottom and shoves it up into where the pump and reservoir are in the image above. These 3D print files are available on Corsair’s account on Printables.  Corsair 5000DWe didn’t care too much about it but Corsair also showed off its new 5000D that has a screen on it, which is a thing companies are doing now. They also had a 5000D case without the screen, which is a larger variant of the Frame 4000D case. Corsair says that it should be priced around $180, but that’s in flux with the tariffs situation.  Corsair Open Concept Visit our Patreon page to contribute a few dollars toward this website's operation (or consider a direct donation or buying something from our GN Store!) Additionally, when you purchase through links to retailers on our site, we may earn a small affiliate commission.Corsair’s open concept at Computex is using some of the same Frame components, where the company is trying to make the Frame series modular and represents an open frame. There’s also an option for fan mounts as well. The company showed a gigantic radiator tower at the show, which is pretty cool to see.

Email authentication protocols like SPF, DKIM, and DMARC play a critical role in protecting domains from spoofing and phishing. However, when SEGs are introduced into the email path, the interaction with these protocols becomes more complex. Security gateways(SEGs) are a core part of many organizations’ email infrastructure. They act as intermediaries between the public internet and internal mail systems, inspecting, filtering, and routing messages. This blog examines how security gateways handle SPF, DKIM, and DMARC, with real-world examples from popular gateways such as Proofpoint, Mimecast, and Avanan. We’ll also cover best practices for maintaining authentication integrity and avoiding misconfigurations that can compromise email authentication or lead to false DMARC failures. Security gateways often sit at the boundary between your organization and the internet, managing both inbound and outbound email traffic. Their role affects how email authentication protocols behave. An inbound SEG examines emails coming into your organization. It checks SPF, DKIM, and DMARC to determine if the message is authentic and safe before passing it to your internal mail servers. An outbound SEG handles emails sent from your domain. It may modify headers, rewrite envelope addresses, or even apply DKIM signing. All of these can impact SPF,  DKIM, or DMARC validation on the recipient’s side. Understanding how SEGs influence these flows is crucial to maintaining proper authentication and avoiding unexpected DMARC failures. Inbound Handling of SPF, DKIM, and DMARC by Common Security Gateways When an email comes into your organization, your security gateway is the first to inspect it. It checks whether the message is real, trustworthy, and properly authenticated. Let’s look at how different SEGs handle these checks. Avanan (by Check Point) SPF: Avanan verifies whether the sending server is authorized to send emails for the domain by checking the SPF record. DKIM: It verifies if the message was signed by the sending domain and if that signature is valid. DMARC: It uses the results of the SPF and DKIM check to evaluate DMARC. However, final enforcement usually depends on how DMARC is handled by Microsoft 365 or Gmail, as Avanan integrates directly with them. Avanan offers two methods of integration:1. API integration: Avanan connects via APIs, no change in MX, usually Monitor or Detect modes.2. Inline integration: Avanan is placed inline in the mail flow (MX records changed), actively blocking or remediating threats. Proofpoint Email Protection SPF: Proofpoint checks SPF to confirm the sender’s IP is authorized to send on behalf of the domain. You can set custom rules (e.g. treat “softfail” as “fail”). DKIM: It verifies DKIM signatures and shows clear pass/fail results in logs. DMARC: It fully evaluates DMARC by combining SPF and DKIM results with alignment checks. Administrators can configure how to handle messages that fail DMARC, such as rejecting, quarantining, or delivering them. Additionally, Proofpoint allows whitelisting specific senders you trust, even if their emails fail authentication checks. Integration Methods Inline Mode: In this traditional deployment, Proofpoint is positioned directly in the email flow by modifying MX records. Emails are routed through Proofpoint’s infrastructure, allowing it to inspect and filter messages before they reach the recipient’s inbox. This mode provides pre-delivery protection and is commonly used in on-premises or hybrid environments. API-Based (Integrated Cloud Email Security – ICES) Mode: Proofpoint offers API-based integration, particularly with cloud email platforms like Microsoft 365 and Google Workspace. In this mode, Proofpoint connects to the email platform via APIs, enabling it to monitor and remediate threats post-delivery without altering the email flow. This approach allows for rapid deployment and seamless integration with existing cloud email services. Mimecast SPF: Mimecast performs SPF checks to verify whether the sending server is authorized by the domain’s SPF record. Administrators can configure actions for SPF failures, including block, quarantine, permit, or tag with a warning. This gives flexibility in balancing security with business needs. DKIM: It validates DKIM signatures by checking that the message was correctly signed by the sending domain and that the content hasn’t been tampered with. If the signature fails, Mimecast can take actions based on your configured policies. DMARC: It fully evaluates DMARC by combining the results of SPF and DKIM with domain alignment checks. You can choose to honor the sending domain’s DMARC policy (none, quarantine, reject) or apply custom rules, for example, quarantining or tagging messages that fail DMARC regardless of the published policy. This allows more granular control for businesses that want to override external domain policies based on specific contexts. Integration Methods Inline Deployment: Mimecast is typically deployed as a cloud-based secure email gateway. Organizations update their domain’s MX records to point to Mimecast, so all inbound (and optionally outbound) emails pass through it first. This allows Mimecast to inspect, filter, and process emails before delivery, providing robust protection. API Integrations: Mimecast also offers API-based services through its Mimecast API platform, primarily for management, archival, continuity, and threat intelligence purposes. However, API-only email protection is not Mimecast’s core model. Instead, the APIs are used to enhance the inline deployment, not replace it. Barracuda Email Security Gateway SPF: Barracuda checks the sender’s IP against the domain’s published SPF record. If the check fails, you can configure the system to block, quarantine, tag, or allow the message, depending on your policy preferences. DKIM: It validates whether the incoming message includes a valid DKIM signature. The outcome is logged and used to inform further policy decisions or DMARC evaluations. DMARC: It combines SPF and DKIM results, checks for domain alignment, and applies the DMARC policy defined by the sender. Administrators can also choose to override the DMARC policy, allowing messages to pass or be treated differently based on organizational needs (e.g., trusted senders or internal exceptions). Integration Methods Inline mode (more common and straightforward): Barracuda Email Security Gateway is commonly deployed inline by updating your domain’s MX records to point to Barracuda’s cloud or on-premises gateway. This ensures that all inbound emails pass through Barracuda first for filtering and SPF, DKIM, and DMARC validation before being delivered to your mail servers. Deployment Behind the Corporate Firewall: Alternatively, Barracuda can be deployed in transparent or bridge mode without modifying MX records. In this setup, the gateway is placed inline at the network level, such as behind a firewall, and intercepts mail traffic transparently. This method is typically used in complex on-premises environments where changing DNS records is not feasible. Cisco Secure Email (formerly IronPort) Cisco Secure Email acts as an inline gateway for inbound email, usually requiring your domain’s MX records to point to the Cisco Email Security Appliance or cloud service. SPF: Cisco Secure Email verifies whether the sending server is authorized in the sender domain’s SPF record. Administrators can set detailed policies on how to handle SPF failures. DKIM: It validates the DKIM signature on incoming emails and logs whether the signature is valid or has failed. DMARC: It evaluates DMARC by combining SPF and DKIM results along with domain alignment checks. Admins can configure specific actions, such as quarantine, reject, or tag, based on different failure scenarios or trusted sender exceptions. Integration methods On-premises Email Security Appliance (ESA): You deploy Cisco’s hardware or virtual appliance inline, updating MX records to route mail through it for filtering. Cisco Cloud Email Security: Cisco offers a cloud-based email security service where MX records are pointed to Cisco’s cloud infrastructure, which filters and processes inbound mail. Cisco Secure Email also offers advanced, rule-based filtering capabilities and integrates with Cisco’s broader threat protection ecosystem, enabling comprehensive inbound email security. Outbound Handling of SPF, DKIM, and DMARC by Common Security Gateways When your organization sends emails, security gateways can play an active role in processing and authenticating those messages. Depending on the configuration, a gateway might rewrite headers, re-sign messages, or route them through different IPs – all actions that can help or hurt the authentication process. Let’s look at how major SEGs handle outbound email flow. Avanan – Outbound Handling and Integration Methods Outbound Logic Avanan analyzes outbound emails primarily to detect data loss, malware, and policy violations. In API-based integration, emails are sent directly by the original mail server (e.g., Microsoft 365 or Google Workspace), so SPF and DKIM signatures remain intact. Avanan does not alter the message or reroute traffic, which helps maintain full DMARC alignment and domain reputation. Integration Methods 1. API Integration: Connects to Microsoft 365 or Google Workspace via API. No MX changes are needed. Emails are scanned after they are sent, with no modification to SPF, DKIM, or the delivery path.  How it works: Microsoft Graph API or Google Workspace APIs are used to monitor and intervene in outbound emails. Protection level: Despite no MX changes, it can offer inline-like protection, meaning it can block, quarantine, or encrypt emails before they are delivered externally. SPF/DKIM/DMARC impact: Preserves original headers and signatures since mail is sent directly from Microsoft/Google servers. 2. Inline Integration: Requires changing MX records to route email through Avanan. In this mode, Avanan can intercept and inspect outbound emails before delivery. Depending on the configuration, this may affect SPF or DKIM if not properly handled. How it works: Requires adding Avanan’s Protection level: Traditional inline security with full visibility and control, including encryption, DLP, policy enforcement, and advanced threat protection. SPF/DKIM/DMARC impact: SPF configuration is needed by adding Avanan’s include mechanism to the sending domain’s SPF record. The DKIM record of the original sending source is preserved. For configurations, you can refer to the steps in this blog. Proofpoint – Outbound Handling and Integration Methods Outbound Logic Proofpoint analyzes outbound emails to detect and prevent data loss (DLP), to identify advanced threats (malware, phishing, BEC) originating from compromised internal accounts, and to ensure compliance. Their API integration provides crucial visibility and powerful remediation capabilities, while their traditional gateway (MX record) deployment delivers true inline, pre-delivery blocking for outbound traffic. Integration methods 1. API Integration: No MX record changes are required for this deployment method. Integration is done with Microsoft 365 or Google Workspace. How it works: Through its API integration, Proofpoint gains deep visibility into outbound emails and provides layered security and response features, including: Detect and alert: Identifies sensitive content (Data Loss Prevention violations), malicious attachments, or suspicious links in outbound emails. Post-delivery remediation (TRAP): A key capability of the API model is Threat Response Auto-Pull (TRAP), which enables Proofpoint to automatically recall, quarantine, or delete emails after delivery. This is particularly useful for internally sent messages or those forwarded to other users. Enhanced visibility: Aggregates message metadata and logs into Proofpoint’s threat intelligence platform, giving security teams a centralized view of outbound risks and user behavior. Protection level: API-based integration provides strong post-delivery detection and response, as well as visibility into DLP incidents and suspicious behavior.  SPF/DKIM/DMARC impact: Proofpoint does not alter SPF, DKIM, or DMARC because emails are sent directly through Microsoft or Google servers. Since Proofpoint’s servers are not involved in the actual sending process, the original authentication headers remain intact. 2. Gateway Integration (MX Record/Smart Host): This method requires updating MX records or routing outbound mail through Proofpoint via a smart host. How it works: Proofpoint acts as an inline gateway, inspecting emails before delivery. Inbound mail is filtered via MX changes; outbound mail is relayed through Proofpoint’s servers. Threat and DLP filtering: Scans outbound messages for sensitive content, malware, and policy violations. Real-time enforcement: Blocks, encrypts, or quarantines emails before they’re delivered. Policy controls: Applies rules based on content, recipient, or behavior. Protection level: Provides strong, real-time protection for outbound traffic with pre-delivery enforcement, DLP, and encryption. SPF/DKIM/DMARC impact: Proofpoint becomes the sending server: SPF: You need to configure ProofPoint’s SPF. DKIM: Can sign messages; requires DKIM setup. DMARC: DMARC passes if SPF and DKIM are set up properly. Please refer to this article to configure SPF and DKIM for ProofPoint. Mimecast – Outbound Handling and Integration Methods Outbound Logic Mimecast inspects outbound emails to prevent data loss (DLP), detect internal threats such as malware and impersonation, and ensure regulatory compliance. It primarily functions as a Secure Email Gateway (SEG), meaning it sits directly in the outbound email flow. While Mimecast offers APIs, its core outbound protection is built around this inline gateway model. Integration Methods 1. Gateway Integration (MX Record change required) This is Mimecast’s primary method for outbound email protection. Organizations route their outbound traffic through Mimecast by configuring their email server (e.g., Microsoft 365, Google Workspace, etc.) to use Mimecast as a smart host. This enables Mimecast to inspect and enforce policies on all outgoing emails in real time. How it works: Updating outbound routing in your email system (smart host settings), or Using Mimecast SMTP relay to direct messages through their infrastructure. Mimecast then scans, filters, and applies policies before the email reaches the final recipient. Protection level: Advanced DLP: Identifies and prevents sensitive data leaks. Impersonation and Threat Protection: Blocks malware, phishing, and abuse from compromised internal accounts. Email Encryption and Secure Messaging: Applies encryption policies or routes messages via secure portals. Regulatory Compliance: Enforces outbound compliance rules based on content, recipient, or metadata. SPF/DKIM/DMARC impact: SPF: Your SPF record must include Mimecast’s SPF mechanism based on your region to avoid SPF failures. DKIM: A new DKIM record should be configured to make sure your emails are DKIM signed when routing through Mimecast. DMARC: With correct SPF and DKIM setup, Mimecast ensures DMARC alignment, maintaining your domain’s sending reputation. Please refer to the steps in this detailed article to set up SPF and DKIM for Mimecast. 2. API Integration (Complementary to Gateway) Mimecast’s APIs complement the main gateway by providing automation, reporting, and management tools rather than handling live outbound mail flow. They allow you to manage policies, export logs, search archived emails, and sync users. APIs enhance visibility and operational tasks but do not provide real-time filtering or blocking of outbound messages. Since APIs don’t process live mail, they have no direct effect on SPF, DKIM, or DMARC; those depend on your gateway (smart host) setup. Barracuda – Outbound Handling and Integration Methods Outbound Logic Barracuda analyzes outbound emails to prevent data loss (DLP), block malware, stop phishing/impersonation attempts from compromised internal accounts, and ensure compliance. Barracuda offers flexible deployment options, including both traditional gateway (MX record) and API-based integrations. While both contribute to outbound security, their roles are distinct. Integration Methods 1. Gateway Integration (MX Record / Smart Host) — Primary Inline Security How it works: All outbound emails pass through Barracuda’s security stack for real-time inspection, threat blocking, and policy enforcement before delivery. Protection level: Comprehensive DLP (blocking, encrypting, or quarantining sensitive content)  Outbound spam and virus filtering  Enforcement of compliance and content policies This approach offers a high level of control and immediate threat mitigation on outbound mail flow. SPF/DKIM/DMARC impact: SPF: Update SPF records to include Barracuda’s sending IPs or SPF include mechanism. DKIM: Currently, no explicit setup is needed; DKIM of the main sending source is preserved. Refer to this article for more comprehensive guidance on Barracuda SEG configuration. 2. API Integration (Complementary & Advanced Threat Focus) How it works: The API accesses cloud email environments to analyze historical and real-time data, learning normal communication patterns to detect anomalies in outbound emails. It also supports post-delivery remediation, enabling the removal of malicious emails from internal mailboxes after sending. Protection level: Advanced AI-driven detection and near real-time blocking of outbound threats, plus strong post-delivery cleanup capabilities. SPF/DKIM/DMARC impact: Since mail is sent directly by the original mail server (e.g., Microsoft 365), SPF and DKIM signatures remain intact, preserving DMARC alignment and domain reputation. Cisco Secure Email (formerly IronPort) – Outbound Handling and Integration Methods Outbound Logic Cisco Secure Email protects outbound email by preventing data loss (DLP), blocking spam and malware from internal accounts, stopping business email compromise (BEC) and impersonation attacks, and ensuring compliance. Cisco provides both traditional gateway appliances/cloud gateways and modern API-based solutions for layered outbound security. Integration Methods 1. Gateway Integration (MX Record / Smart Host) – Cisco Secure Email Gateway (ESA) How it works: Organizations update MX records to route mail through the Cisco Secure Email Gateway or configure their mail server (e.g., Microsoft 365, Exchange) to smart host outbound email via the gateway. All outbound mail is inspected and policies enforced before delivery. Protection level: Granular DLP (blocking, encrypting, quarantining sensitive content) Outbound spam and malware filtering to protect IP reputation Email encryption for sensitive outbound messages Comprehensive content and attachment policy enforcement SPF: Check this article for comprehensive guidance on Cisco SPF settings. DKIM: Refer to this article for detailed guidance on Cisco DKIM settings. 2. API Integration – Cisco Secure Email Threat Defense How it works: Integrates directly via API with Microsoft 365 (and potentially Google Workspace), continuously monitoring email metadata, content, and user behavior across inbound, outbound, and internal messages. Leverages Cisco’s threat intelligence and AI to detect anomalous outbound activity linked to BEC, account takeover, and phishing. Post-Delivery Remediation: Automates the removal or quarantine of malicious or policy-violating emails from mailboxes even after sending. Protection level: Advanced, AI-driven detection of sophisticated outbound threats with real-time monitoring and automated remediation. Complements gateway filtering by adding cloud-native visibility and swift post-send action. SPF/DKIM/DMARC impact: Since emails are sent directly by the original mail server, SPF and DKIM signatures remain intact, preserving DMARC alignment and domain reputation. If you have any questions or need assistance, feel free to reach out to EasyDMARC technical support.

Posted on : June 5, 2025 By Tech World Times Technology  Rate this post The Software as a Service (SaaS) industry has been on an unstoppable trajectory since its inception, revolutionizing how businesses and individuals consume and manage software. The landscape of subscription services within this sector continues to evolve at a rapid pace. Driven by customer expectations, technological advancements, and economic shifts, several trends are emerging that promise to reshape the SaaS industry. These trends will not only influence the way software is delivered and managed but also impact the overall subscription economy. Check out these subscription trends that are set to redefine the SaaS industry in the next few years. 1. Personalization and Customer-Centric Models Businesses are increasingly recognizing the value of tailored experiences, and SaaS companies are responding with personalized subscription offerings. By leveraging user data and machine learning algorithms, providers are crafting customized solutions that cater to individual needs, preferences, and usage patterns. Personalization also extends to the billing process, where SaaS payment processing systems are adapting to offer flexible pricing models, such as pay-per-use and tiered subscriptions. 2. Integrated Payment Solutions and Subscription Management SaaS payment processing will become a seamless and integrated part of the subscription experience. Innovations in financial technology will streamline the billing process, providing users with a unified dashboard to manage all their subscriptions. This will simplify financial management for both consumers and businesses. Companies will be able to offer various payment methods, automate billing cycles, and handle currency conversions with ease, making it easier for them to serve a global customer base. 3. The Rise of Usage-Based Pricing Usage-based pricing is gaining traction as a fair and transparent way to bill for cloud services. Instead of flat monthly or annual fees, SaaS providers will charge customers based on the actual resources consumed. This model aligns the cost with the value derived, encouraging more efficient use of resources and reducing waste. It also allows companies to scale more easily, leading to more granular and sophisticated pricing structures that can handle these complex calculations. 4. Subscription Model Innovation To stand out in a crowded market, SaaS companies are experimenting with innovative subscription models that go beyond the typical monthly or annual plans. These include freemium models, where users get a basic version of the software for free and pay for additional features, and dynamic pricing that adjusts based on demand and supply. The goal is to create a more nuanced pricing strategy that appeals to a wider range of customers and enhances the overall perceived value of the service. 5. Emphasis on User Experience and Customer Retention The importance of user experience is paramount in the SaaS industry, and in 2025, companies will invest heavily in creating delightful onboarding processes, intuitive user interfaces, and proactive customer support. The focus on customer retention will be a key driver for subscription growth, as it becomes more cost-effective than acquiring new ones. This shift will lead to the integration of more sophisticated tools for tracking customer engagement and satisfaction, allowing for targeted interventions to reduce churn rates. 6. Expansion into Emerging Markets As developed markets become saturated, SaaS companies are setting their sights on emerging economies. To cater to these diverse markets, providers will need to adapt their offerings to suit local preferences and constraints, such as language, cultural nuances, and payment methods. This trend will result in the rise of regional SaaS leaders and increased competition from local players, pushing the industry to become more global and inclusive. 7. Increased Adoption of AI and Automation Artificial intelligence and automation will play a significant role in the SaaS industry, optimizing everything from customer support to sales and marketing. Chatbots and virtual assistants will become commonplace for handling routine inquiries, while AI algorithms will be used to predict customer behavior and offer personalized recommendations. Automation will streamline backend processes, reducing costs and enhancing the overall efficiency of subscription management. This integration will lead to more intelligent and proactive services, with the potential for predictive analytics to anticipate customer needs before they even arise. The SaaS industry is poised for continued growth and evolution, with these seven subscription trends at the forefront. Personalization, integrated payment processing, usage-based pricing, innovative models, user experience enhancements, emerging market expansion, and the integration of AI and automation are all shaping the future of this dynamic sector. The most successful SaaS companies will be those that embrace these trends, adapting their offerings and operations to meet the changing demands of the modern subscription economy. With the right strategies in place, they will be able to deliver superior value to their customers and thrive in an increasingly competitive landscape. Tech World TimesTech World Times (TWT), a global collective focusing on the latest tech news and trends in blockchain, Fintech, Development & Testing, AI and Startups. If you are looking for the guest post then contact at techworldtimes@gmail.com

Two satellite heavyweights are about to form a European rival to Starlink. But they’ll face an uphill battle to compete with Elon Musk’s firm. Luxembourg-based SES’ proposed $3.1bn takeover of Intelsat is set to get the green light from EU officials, Reuters reports. A final verdict is expected by June 10.   SES first announced plans to acquire Luxembourgish-American rival Intelsat in April 2024, calling it a “transformational merger” that could reshape the satellite internet market. The merged company would have a fleet of more than 100 geostationary and 26 medium Earth orbit satellites. Intelsat would contribute 75 of those probes, which provide a range of services, including TV, radio, satellite internet, and secure communications for governments and militaries. A SES-Intelsat tie-up would create Europe’s second-largest satellite internet provider, after Franco-British firm Eutelsat. Smaller contenders include the UK’s Inmarsat and Spain’s Hisdesat.  Combined, Europe’s satellite firms could offer the continent much-sought alternatives to Musk’s Starlink or Amazon’s Project Kuiper, at a time when tech sovereignty is high on the political agenda.  European leaders are increasingly concerned about relying on Starlink. Their fears have been stoked by reports that US officials threatened to cut off the system in Ukraine if the country didn’t meet their demands on sharing its mineral wealth.   The situation raised doubts about the security implications of Ukraine — and broader Europe — relying on a single, privately owned network whose boss has direct ties to the Trump administration. Eustalstat, SES, Inmarsat, and Hisdesat reportedly entered talks with EU governments in March about providing back-up connectivity to Ukraine.  Despite the SES–Intelsat merger creating a more formidable European player, the new alliance will still face a daunting challenge against Starlink’s dominance.  Musk’s firm dwarfs its competitors in satellite numbers, with over 7,000 in low-Earth orbit (LEO). Its closest rival, Eutelsat, has around 600. Meanwhile, Amazon’s Project Kuiper is planning to deploy a constellation of 3,236 satellites.   Being part of SpaceX also affords Starlink direct access to satellite manufacturing and launch capacity. In contrast, SES and Intelsat depend on third-party launch providers and currently lack a proprietary low-Earth orbit network. While Intelsat has a $250mn agreement to access Eutelsat’s LEO capacity, this reliance on external constellations puts the merged entity at a disadvantage.  Even when combined with Europe’s other players — including Eutelsat, Inmarsat, and Hisdesat — the proposed merger pales in comparison. As European policymakers push for strategic autonomy in space, the SES–Intelsat merger may be a step in the right direction, but it’s still a far cry from a true Starlink rival.

Reddit a porté plainte contre Anthropic devant un tribunal de San Francisco, mercredi 4 juin. DADO RUVIC / REUTERS La plateforme Reddit a porté plainte contre Anthropic, start-up californienne d’intelligence artificielle (IA). Reddit accuse l’entreprise d’avoir utilisé sans autorisation des conversations publiques de ses utilisateurs pour entraîner ses modèles d’IA générative – parmi lesquels figure Claude, un modèle de langage et chatbot concurrent de ChatGPT. D’après la plainte, déposée mercredi 4 juin à San Francisco, Reddit reproche à Anthropic d’avoir entraîné ses modèles de langage à partir de messages « humains » postés sur Reddit. L’action en justice se base notamment sur un document de recherche publié en décembre 2021 par les équipes d’Anthropic et cosignés par le chef de l’entreprise, Dario Amodei. Le texte mentionne certaines conversations spécifiques de Reddit pouvant servir à l’entraînement de tels modèles. Celles tenues sur Wikipédia sont aussi mentionnées. La plainte allègue que malgré les déclarations publiques d’Anthropic, qui a assuré avoir bloqué l’accès à Reddit à ses systèmes automatisés de récolte des données, les robots de l’entreprise ont malgré tout continué « à se connecter aux serveurs de Reddit, et ce plus de cent mille fois » depuis juillet 2024, indique le texte. Lire aussi | Le gouvernement retire une vidéo générée par IA sur la Résistance, à la suite d’une erreur historique Anthropic conteste « Nous ne sommes pas d’accord avec les affirmations de Reddit et nous nous défendrons vigoureusement », a réagi un porte-parole d’Anthropic auprès de l’Agence France-Presse. Fondée à San Francisco par d’anciens ingénieurs d’OpenAI, Anthropic promeut de manière ostensible un développement responsable de l’IA générative. « Cette affaire porte sur les deux personnalités d’Anthropic : la personnalité publique qui tente de faire croire aux consommateurs qu’elle est une entreprise juste qui respecte les limites et la loi, et la personnalité privée qui se moque de toutes les règles qui gênent ses tentatives de s’en mettre plein les poches », accuse Reddit dans la plainte. Reddit demande désormais des dommages et intérêts, et une injonction pour obliger Anthropic à respecter les termes de son contrat d’utilisation. Ce dernier interdit depuis 2024, date d’entrée en Bourse de Reddit, l’utilisation de données issues des discussions Reddit sans qu’un accord, ou un contrat, ne soit signé avec la plateforme. Reddit, qui déclarait en octobre 2024 compter sur 97,2 millions d’utilisateurs actifs chaque jour, a déjà conclu des accords de licence avec d’autres géants de l’IA générative, dont Google et OpenAI. Ces accords permettent à ces firmes d’utiliser les contenus de Reddit suivant des conditions qui protègent les informations confidentielles des utilisateurs, et offrent une compensation financière à la plateforme. Lire aussi | Article réservé à nos abonnés Un pionnier de l’IA veut construire des systèmes non nuisibles à l’humanité Le Monde avec AFP