SOLVED

550 spamcop.mimecast bounces

Go to solution

550 spamcop.mimecast bounces

We're currently implementing Marketo at my current company and our IT does not want to whitelist the shared IP addresses, as it masks other issues. However, we also use mimecast, so most of our test and actual email sends to ourselves internally are bouncing due to spamcop blacklists.

Are there any other options to resolve this issue besides a dedicated IP?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Level 10 - Community Moderator

Re: 550 spamcop.mimecast bounces

The most accurate way to whitelist is based on DKIM signature: it can't be forged by outsiders, nor shared by other tenants on your shared Marketo instance.

However, aside from the technical difficulty (IT may not have a way of treating signed mail from certain domains differently) it's still the case that you're skipping spam checks that would otherwise help you diagnose deliverability probs (if it uses the same signing From: domain and thus same DKIM private key).

View solution in original post

3 REPLIES 3
Highlighted

Re: 550 spamcop.mimecast bounces

Hi Kelly,

Depending on your send volume, you can always apply to be in a trusted pool of IPs (which tends to get hit far less often by Spamcop.) I believe the limit before you need to consider a dedicated IP is ~75K emails/mo.

Highlighted

Re: 550 spamcop.mimecast bounces

Thanks! Yeah we did look into that, but you have to be sending emails for at least 6 months from Marketo first too - plus we send well over 75k emails a month. Bummer!

Highlighted
Level 10 - Community Moderator

Re: 550 spamcop.mimecast bounces

The most accurate way to whitelist is based on DKIM signature: it can't be forged by outsiders, nor shared by other tenants on your shared Marketo instance.

However, aside from the technical difficulty (IT may not have a way of treating signed mail from certain domains differently) it's still the case that you're skipping spam checks that would otherwise help you diagnose deliverability probs (if it uses the same signing From: domain and thus same DKIM private key).

View solution in original post