Hello,
We appear to be hitting a capacity wall from one of our ranges (
15.222.16.128/25) in delivering to their servers at 184.150.200.82 and
184.150.200.210.
I reached out to postmas...@bell.ca (postmas...@bell.net bounced) at the
end of yesterday (PDT) but no response yet, so maybe here?
Sinc
You won't get an official statement from Barracuda *here*, nor from me
(here or anywhere else).
Your customer's recipient (which should be the Barracuda customer) should
be able to log in to our website and find the message in their log, and see
what the reason was for blocking. If that doesn't en
In the circumstances you described it probably means your message was
deemed spammy for whatever reason. If that is the typical message content
for the sender on your end, then yes they should probably treat it as a
hard bounce.
It is difficult to say more without some context, or in a public foru
Hi,
I asked around and gather that they are aware and actively working on resolving
this issue.
Disclaimers as needed (not my team, code, and not an official statement)
—Erwin
> On Jun 18, 2019, at 04:57, Kieran Cooper via mailop wrote:
>
> A couple of our customers at SparkPost have started
Yeah, that’s what we’re going with right now. Our support team has been made
aware of this ongoing issue.
Thanks,
Erwin
> On Jun 13, 2019, at 10:49, Laura Atkins via mailop wrote:
>
>
>> On 13 Jun 2019, at 18:11, Kevin A. McGrail via mailop
>> wrote:
>>
>>
That’s ESS, our hosted email filtering service which includes customer
configured list of RBLs.
--Erwin
> On Jun 13, 2019, at 09:48, Kevin A. McGrail via mailop
> wrote:
>
> Nick,
>
> Thanks for escalating to them. I've been doing the same.
>
> However, I think you were given wrong informa
