How to setup BIMI when sending from Iterable through SES shared pools?

Setting up BIMI when sending from Iterable through SES shared pools involves a multi-faceted approach. Initially, understand that SES's default DKIM/SPF settings may provide partial coverage, but fully configuring your sending domain within Iterable's 'Custom project sending domain' settings is crucial. The process necessitates DMARC enforcement with a quarantine or reject policy for both the subdomain and apex domain, DKIM signing achieved by generating a key pair and adding a public key as a TXT record in your DNS, and obtaining a Verified Mark Certificate (VMC). A BIMI DNS TXT record pointing to your securely hosted SVG logo is also required. Using SES shared IP pools might limit control over your sending reputation, affecting DMARC enforcement; consult your ESP about their policies on this. Select a BIMI vendor with VMC acquisition and DNS management expertise. Post-implementation, monitor email deliverability and engagement. In essence, BIMI requires authentication, policy, and logos, building upon DMARC, DKIM, and SPF setup, making it somewhat complex but beneficial for enhancing brand recognition and trust.

Setting up BIMI when sending from Iterable through SES shared pools involves several key steps and considerations. It requires DMARC enforcement (quarantine or reject policy), DKIM signing, and obtaining a Verified Mark Certificate (VMC) to display your logo. Configuring a Custom Sending Domain in Iterable is crucial, involving DNS record setup for DKIM and SPF. Using shared IP pools, like those in SES, may limit control over your sending reputation, impacting DMARC enforcement. Therefore, it's essential to check with your ESP about their policies on custom DMARC setups with shared IPs. Implementing BIMI enhances brand recognition, trust, and open rates. The setup complexity includes DMARC configuration, DKIM setup, and VMC acquisition, necessitating careful selection of a BIMI vendor experienced in VMC and DNS management. Post-implementation, monitoring email deliverability and engagement metrics is crucial. Additionally, seeking assistance from Iterable's Deliverability Team can be beneficial.

Setting up BIMI with Iterable and SES shared pools involves configuring authentication (SPF and DKIM), policy (DMARC set to quarantine or reject), and providing logos in SVG format. SES's default settings might initially cover SPF, but fully configuring your domain (mail.signos.com) is crucial. Look for "Custom project sending domain" settings within Iterable, particularly a DNS subsection for DKIM setup. DMARC is a foundational dependency for BIMI, requiring both DKIM and SPF to be established beforehand.

Setting up BIMI involves several technical steps: DKIM setup requires generating a key pair, adding the public key as a TXT record to your DNS, and enabling DKIM signing for your SES identity. A DMARC record with a quarantine or reject policy must be created and published in your DNS. BIMI also requires a DNS TXT record pointing to your SVG logo file hosted securely (HTTPS). To display your logo, you need a Verified Mark Certificate (VMC) to verify logo ownership and compliance.