On Sun, 2021-12-19 at 21:13 -0500, John Levine via mailop wrote:
> tektonic.net
you'd do them a favor if you alerted them that their website is so 2012. Not
just the design: expired certificate and still using an outdated TLS version.
I trust your judgment that they are good at screening
It appears that Daniele Nicolodi via mailop said:
>I already asked on this list, and I'll ask again: what is a reputable
>hot where to park a server these days?
I've been happy with tektonic.net who have the usual range of linux,
BSD, and Windows VPS. Their prices and tech support are pretty
On 19/12/2021 21:05, John Levine via mailop wrote:
It appears that Jay Hennigan via mailop said:
Our investigation has determined that the above IP(s) do not qualify for
mitigation.
Which roughly translates to "we don't care about receiving email from
independent senders".
You misspelled
It appears that Jay Hennigan via mailop said:
>> Our investigation has determined that the above IP(s) do not qualify for
>> mitigation.
>>
>> Which roughly translates to "we don't care about receiving email from
>> independent senders".
>
>You misspelled "We deliberately decided not to
On 12/19/21 06:23, Daniele Nicolodi via mailop wrote:
Not qualified for mitigation
109.74.203.128
Our investigation has determined that the above IP(s) do not qualify for
mitigation.
Which roughly translates to "we don't care about receiving email from
independent senders".
You misspelled
On Sun, Dec 19, 2021 at 03:23:03PM +0100, Daniele Nicolodi via mailop wrote:
> The Linode support team contacted the Microsoft but their intervention did
> not have any effect. I contacted them myself through
>
>
On 06/12/2021 22:13, Daniele Nicolodi via mailop wrote:
On 06/12/2021 21:09, Mary via mailop wrote:
I had the same experience with outlook.com and servers hosted by
many cloud providers, including Linode.
The solution with Linode is very simple, just open a ticket and
they'll get in touch
Am 06.12.2021 um 22:03 schrieb Jarland Donnell via mailop:
A worthwhile note is that, at least in my experience, the messaging
there can be a bit misleading. I've removed my old blog where I proved
it with logs, but what it basically amounted to was this: I have many
times received that exact
On 12/6/21 1:02 PM, Michael Peddemors via mailop wrote:
In general, Linode is not a bad place.. However, you should ask them to
provide you 'rwhois' for your IP Address.
Linode didn't offer rwhois nor SWIP when I asked them about it O(18)
months ago. I'd love to learn if that has changed.
On 06/12/2021 21:02, Michael Peddemors via mailop wrote:
In general, Linode is not a bad place.. However, you should ask them to
provide you 'rwhois' for your IP Address.
What do you mean with "rwhois"?
Most of the bad IP(s) are compromised servers, you might have just got
the bad luck of
On 06/12/2021 21:09, Mary via mailop wrote:
I had the same experience with outlook.com and servers hosted by
many cloud providers, including Linode.
The solution with Linode is very simple, just open a ticket and
they'll get in touch with M$ and you'll be added into their
whitelist. It
A worthwhile note is that, at least in my experience, the messaging
there can be a bit misleading. I've removed my old blog where I proved
it with logs, but what it basically amounted to was this: I have many
times received that exact error, and had the next email accepted by
their systems
I had the same experience with outlook.com and servers hosted by many cloud
providers, including Linode.
The solution with Linode is very simple, just open a ticket and they'll get in
touch with M$ and you'll be added into their whitelist. It usually takes 2
business days.
Just make sure to
Hello,
is outlook.com blocking all Linode IPv4 space or am I just unlucky?
eur.olc.protection.outlook.com[104.47.18.225] said: 550 5.7.1
Unfortunately, messages from [109.74.203.128] weren't sent. Please contact
your Internet service provider since part of their network is on our
14 matches
Mail list logo
