This was my bad when I sent this. I should have been more specific with the
exact ranges that we are sending from:
148.105.11.0/25
148.105.12.0/24
148.105.13.0/24
148.105.14.0/25
The ranges listed above have rDNS and and actively sending. Since allocation
of IPs for sending is rather
> On May 5, 2017, at 1:17 PM, John Levine wrote:
>
> In article <361703a8-dde8-8363-f4ca-ef5ab2754...@linuxmagic.com> you write:
>> On 17-05-05 09:40 AM, Joey Rutledge wrote:
>>> Hi fellow email geeks,
>>>
>>> MailChimp recently acquired a new IP range, 148.105.0.0/16 and have
In article <361703a8-dde8-8363-f4ca-ef5ab2754...@linuxmagic.com> you write:
>On 17-05-05 09:40 AM, Joey Rutledge wrote:
>> Hi fellow email geeks,
>>
>> MailChimp recently acquired a new IP range, 148.105.0.0/16 and have just
>> started sending from 148.105.8.0/21. ...
>Better first make sure
On 17-05-05 09:40 AM, Joey Rutledge wrote:
Hi fellow email geeks,
MailChimp recently acquired a new IP range, 148.105.0.0/16 and have just
started sending from 148.105.8.0/21. I’ve noticed a few issues with receivers
treating this range poorly, likely due to the previous owners of the range.
Hi fellow email geeks,
MailChimp recently acquired a new IP range, 148.105.0.0/16 and have just
started sending from 148.105.8.0/21. I’ve noticed a few issues with receivers
treating this range poorly, likely due to the previous owners of the range. If
you are a receiver and have the ability