#Email Deliverbility토론 중인 항목 15개

Hi all, hoping to get some real-world input on an Email Relay / deliverability issue we've been chasing.

The problem:

Our org has Salesforce configured with an Email Domain Filter (catch-all, */*) routing all outbound mail through an Email Relay pointed at our Google Workspace SMTP relay service. We've started getting persistent 550-5.7.1 "Invalid credentials for relay" bounces — root cause is that Salesforce sends from a large, rotating pool of outbound IPs, and our relay's IP allowlist can't keep up. This affects everything from Opportunity Update Reminders to account-transfer notifications, not just bulk sends.

Our Current setup:

• IP allowlist maintenance — works but requires constant upkeep as Salesforce's IPs rotate.

Questions for the community:

1. For anyone who's actually deactivated their Email Domain Filter and let Salesforce send directly. How has deliverability held up long-term, especially to Gmail/Outlook/Yahoo?
2. Is there a real, common business reason to keep Email Relay active, can I run processes without it? (DLP scanning, compliance archiving, etc.) Anything that I should weigh before dropping it, beyond Bounce Management/Email Security Compliance features?
3. For those using a third-party SMTP relay (SMTP2GO, SendGrid, Mailgun, Postmark, etc.) with Salesforce, any real experience with shared-IP-pool deliverability issues specifically for transactional CRM mail?
4. Anyone running the TLS-certificate-domain method (vs. IP allowlist) on an Exchange Online connector for Salesforce specifically — has Salesforce's certificate stayed consistent for you over time?

Appreciate any first-hand experience — trying to land on something maintainable rather than another band-aid. 

Hello everyone,

I'm looking for clarification on the current behavior of Salesforce Organization-Wide Email Address (OWEA) verification.

Historically, when an Organization-Wide Email Address was created, Salesforce sent a verification email to the specified address. The recipient could open the email, click the verification link, and the address would become verified.

We are now seeing a scenario where selecting the verification link redirects the recipient to a Salesforce login page instead of completing the verification process.

A Salesforce Support representative indicated that, following a recent Salesforce release, the person opening the verification link may need to authenticate with Salesforce to complete the verification process. However, I have not been able to find any official documentation or release notes that describe this change.

The Salesforce documentation I found states that each organization-wide address requires verification and that an admin verifies a new organization-wide address by clicking the link in the email sent after creating the address, but I don't see any mention of a Salesforce login requirement for the recipient. 

My questions are:

1. Has anyone else observed Organization-Wide Email Address verification links redirecting users to a Salesforce login page?
2. Is a Salesforce login now required to complete OWEA verification?
3. If this behavior is expected, is there any official documentation or release note that explains the change?
4. Is there a supported verification process for recipients who do not have Salesforce user accounts?

Any insight or links to official documentation would be greatly appreciated. 

Deliverability Tips Series

The @* Marketing Cloud Engagement * Deliverability team brings you helpful tips and guidance to build and maintain a great sending reputation.

In this post, we wanted to share information about "branded mail" in Apple, it's not BIMI, it's unique to Apple's new Business Connect solution which is free for companies to sign up for. Senders must have DMARC configured to display their logo.

#Marketing Cloud  #Email Deliverbility

Deliverability Tips Series

The @* Marketing Cloud Engagement *  Deliverability team shares valuable insights to help you build and maintain a strong sending reputation. Today, we discuss the dangers of list purchasing and its impact on your sender reputation. While buying lists might seem like a quick way to grow your audience, it can lead to significant problems. Here's why:

The Hazards of List Purchasing in SFMC

1. Compliance and Legal Risks

Purchasing email lists often violates privacy laws like:

GDPR in the EU

CAN-SPAM Act in the U.S.

CCPA in California

Non-compliance can result in hefty fines and penalties.

1. Poor Data Quality: Purchased lists are often filled with outdated or inaccurate data, leading to high bounce rates and low engagement. This diminishes the effectiveness of campaigns and skews your analytics in SFMC.
2. Negative Impact on Deliverability: Recipients who didn’t opt-in are likely to unsubscribe or report your emails as spam, harming your sender reputation and decreasing deliverability rates.
3. Brand Reputation Risks: Sending unsolicited emails can damage your brand’s image. If your emails are seen as intrusive, it can foster negative perceptions that are hard to reverse.
4. Ineffective Segmentation: Purchased lists lack proper segmentation, making it difficult to deliver personalized content. SFMC's powerful segmentation tools work best with quality, permission-based data.
5. Resource Drain: The time spent fixing issues from poor-quality lists—such as handling compliance problems and cleaning data—can far exceed any short-term gains.
6. Missed Engagement Opportunities: Relying on purchased lists distracts from nurturing your existing, engaged audience, which could lead to deeper customer relationships and better long-term results.

Conclusion

While list purchasing may offer a quick audience boost, the risks outweigh the benefits. Building an organic, permission-based audience ensures compliance, protects your brand reputation, and leads to more effective marketing. In the long run, focusing on quality will drive better engagement and sustainable success.

Alternatives to List Purchasing in SFMC

To avoid the risks of list purchasing, focus on organic list-building strategies. Here are some effective alternatives:

1. Create Valuable Content: Offer free resources like eBooks or webinars to attract sign-ups from genuinely interested users.
2. Optimize Your Website: Use pop-ups, subscription forms, and lead magnets to encourage visitors to subscribe, offering incentives like discounts.
3. Leverage Social Media: Promote email sign-ups via contests or gated content on social platforms to grow an engaged list.

#Email Deliverability Issues  #Email Deliverbility  #Marketing Cloud

Deliverability Tips Series

The @Marketing Cloud Deliverability team brings you helpful tips and guidance to build and maintain a great sending reputation.

In this post we’ll talk about IP capacity.

Did you know that mailbox providers limit the amount of mail an IP address can send in a day? This is not a Marketing Cloud restriction but is tied closely to how mailbox providers view your reputation as a sender. Sending large amounts of mail through a single IP can appear as 'spammy' behavior to many mailbox providers. 

Where we start seeing deferrals from major mailbox providers occur is typically once a customer starts sending 2M+ emails per day through a single IP.

3 key points to keep in mind:

* 1 Dedicated IP can send a maximum of 2.5M million sends per day (24 hour window), once you reach 2M sends per day it's time to start adding IP capacity for your campaigns.

* Project ahead for growth; if you’re going to need more IP(s) to accommodate volume in the next 1-3 months, add them now. New IPs will require a IP warm-up plan.

* Mailbox providers are on high alert Oct. - Dec. as mail volume spikes due to the retail season (Cyber Week). Learn more about how Cyber Week volume impacts a sender's reputation in our latest blog.

Remember that deliverability success is reflective of sending practices. If you are sending more than the recommended volume and seeing a decrease in deliverability or an increase in deferrals, it may be time to review your email program and IP configuration.

#Marketing Cloud #Email Deliverability Issues #Email Deliverbility