Showing posts with label Security Updates. Show all posts
Showing posts with label Security Updates. Show all posts

Tuesday, 8 April 2025

Strengthening Email Ecosystem: Outlook’s New Requirements for High‐Volume Senders

In an era where email remains a cornerstone of both personal and business communication, ensuring the security and reliability of email ecosystems is paramount. To bolster trust and protect users, Outlook.com is introducing new requirements for domains that send over 5,000 emails per day. These measures aim to enhance email authentication and reduce malicious activities such as spoofing, phishing, and spam.

New Authentication Requirements for High-Volume Senders

Effective May 5, 2025, domains dispatching more than 5,000 emails daily to Outlook.com addresses must comply with the following authentication protocols:

  1. Sender Policy Framework (SPF):

    • Ensure that your domain's DNS records accurately list all authorized IP addresses and hosts permitted to send emails on behalf of your domain.

    • SPF records must pass validation to confirm the legitimacy of the sending source.

  2. DomainKeys Identified Mail (DKIM):

    • Implement DKIM to attach a digital signature to your emails, verifying that the message content remains unaltered during transit.

    • DKIM signatures must pass verification to authenticate the integrity and origin of the emails.

  3. Domain-based Message Authentication, Reporting, and Conformance (DMARC):

    • Configure a DMARC policy with at least a p=none setting, aligning with either SPF or DKIM (preferably both).

    • DMARC enables domain owners to specify how unauthenticated messages should be handled, providing reports on email authentication status.

For detailed guidance on setting up these authentication methods, refer to Microsoft's documentation on email authentication.

Additional Email Hygiene Best Practices

Beyond authentication, high-volume senders are encouraged to adopt the following practices to maintain email quality and user trust:

  • Valid P2 (Primary) Sender Addresses:

    • Ensure that the "From" or "Reply-To" addresses are valid, accurately reflect the sending domain, and are capable of receiving replies.

  • Functional Unsubscribe Mechanisms:

    • Provide clear and accessible options for recipients to opt out of future communications, especially in marketing or bulk emails.

  • Regular List Maintenance and Bounce Management:

    • Periodically cleanse mailing lists to remove invalid or inactive addresses, thereby reducing bounce rates and spam complaints.

  • Transparent Mailing Practices:

    • Use honest subject lines, avoid misleading headers, and ensure that all recipients have explicitly consented to receive your emails.

Adhering to these practices not only enhances deliverability but also fortifies the sender's reputation within the email ecosystem.

Enforcement Timeline and Actions

Starting May 5, 2025, Outlook.com will begin routing emails from non-compliant high-volume senders to recipients' Junk folders. This initial phase serves as a grace period, allowing senders to address and rectify any authentication issues. Future enforcement actions may escalate to outright rejection of non-compliant emails, with specific dates to be announced subsequently.

Outlook.com reserves the right to take negative actions, including filtering or blocking, against senders who fail to meet these standards, particularly in cases of significant authentication breaches or poor email hygiene.

Steps to Prepare

To align with these new requirements and ensure uninterrupted email delivery:

  1. Audit Your DNS Records:

    • Review and update your SPF, DKIM, and DMARC records to ensure they meet the specified standards.

  2. Monitor Authentication Headers:

    • Regularly inspect email headers to verify authentication status. Guidance on viewing and interpreting these headers is available through Microsoft's support resources.

  3. Stay Updated:

    • Keep abreast of further announcements regarding enforcement timelines and additional requirements by following official communications from Outlook.com.

By proactively implementing these measures, high-volume senders can contribute to a more secure and trustworthy email environment, benefiting both senders and recipients alike.

Thursday, 5 October 2023

[Solved] 0x64C(1612) : The installation source for this product is not available. Verify that the source exists and that you can access it.

When attempting an upgrade to newer version, uninstalling or repair, you may receive an error with an exit code of 1603, 1612,  0x8024002D (-2145124307), 0X80240022 (-2145124318).

The error code 1612 is the most useful in determining the underlying reason. When you run CMTrace.exe, it will deliver the results of an error lookup. "The installation source for this product is not available. Verify that the source exists and that you can access it."

Tuesday, 21 June 2022

Difference between x86, x64 and ARM architecture

Both x86 and x64 are same CPU architecture. HOW?

x86 is a "CPU" architecture which was initially used with 16bit "chip" and later on extended to be used on 32 bit chip. For most of the time, we used a 32bit chip(each number represented with 32 bits) that had x86 architecture. So basically, when we said this computer (CPU) is x86, it meant 32 bit or vice versa and same with OS, if an OS was 32bit, then it meant it was running x86 CPU architecture chip. (I'm not considering ARM here)

Now, due to the limitation of memory usage with 32bit chip that it can only support 4GB of RAM, x86 was then extended to be used on 64 bit chip, so basically now the same architecture (instructions set) was used to build a chip that used 64bit to represent a number, hence 64bit chip. Initially it was called x86-64 and later reduced to x64 which meant that x86 is the architecture on a 64bit chip.

Like x86 and x64, ARM is a different processor (CPU) architecture. The ARM architecture is typically used to build CPUs for a mobile device, ARM64 is simply an extension or evolution of the ARM architecture that supports 64-bit processing. Devices built on the ARM64 architecture include desktop PCs, mobile devices, and some IoT Core devices (Rasperry Pi 2, Raspberry Pi 3, and DragonBoard). For example the Microsoft HoloLens 2 uses an ARM64 processor.

About the architectures, you can refer to this document.

What's new in Microsoft Intune: April 2025

Microsoft Intune's April 2025 release introduces several enhancements aimed at improving device management and security: Custom Naming ...