On 1/25/24 01:12, Marco Moock via mailop wrote:
Both don't pass here, so fix SPF and try again.
I would hope that redacted.example.net and 192.0.2.1 fail.
redacted.example.net is part of one of the (few) names reserved for
documentation; specifically example.net. Likewise 192.0.2.1 is part o
Dnia 24.01.2024 o godz. 21:48:39 Grant Taylor via mailop pisze:
>
> Am I missing something obvious or has Google started implementing
> this new requirement ahead of their published schedule?
>
> The only surprise to me is that this happened ~8 days before the
> published February 1st date.
Appa
> On 25 Jan 2024, at 07:57, Thomas Walter via mailop wrote:
>
> Moin,
>
> On 25.01.24 04:48, Grant Taylor via mailop wrote:
>> I knew that Google was going to start requiring SPF or DKIM (in addition to
>> other sender guidelines [1]. But I thought they were starting February 1st,
>> per th
Moin,
On 25.01.24 04:48, Grant Taylor via mailop wrote:
I knew that Google was going to start requiring SPF or DKIM (in addition
to other sender guidelines [1]. But I thought they were starting
February 1st, per their own sender guidelines.
Just to clarify, because some of our customers were
Am 24.01.2024 um 21:48:39 Uhr schrieb Grant Taylor via mailop:
> I knew that Google was going to start requiring SPF or DKIM (in
> addition to other sender guidelines [1]. But I thought they were
> starting February 1st, per their own sender guidelines.
IIRC Google starts to require DKIM for bul
On 1/24/24 22:12, Alexander Neilson via mailop wrote:
Was this over v6?
Nope. Hence the Test-Net-1 IPv4 address.
This was on a friends system and said friend is an IPv4 stalwart in that
he sees no benefit for the additional time and overhead for IPv6 for his
small business that has sufficie
On 1/24/24 22:09, Russell Clemings via mailop wrote:
I saw it a couple of weeks ago.
I wonder if what they meant by February 1st is that's when they would
hit the 100% requirement and they are doing the 1% / 5% / 10% / 50% /
80% / 100% ramp up now.
Similar, a server reporting in via cron.
Regards
Alexander
Alexander Neilson
Neilson Productions Limited
021 329 681
alexan...@neilson.net.nz
> On 25/01/2024, at 16:56, Grant Taylor via mailop wrote:
>
> Hi,
>
> I knew that Google was going to start requiring SPF or DKIM (in addition to
> other sender guidelines [1]. But I thoug
In past mailop posts, Brandon Long from Google has posted about that. For
example, on September 12th, 2023:
"And yes, we are continuing to ramp no auth, no entry."
There was also a more recent post on the list with additional details about
their Feb. 1st changes.
Hope this helps,
-Jeffrey
On We
I saw it a couple of weeks ago. Similar, a server reporting in via cron. It
was pretty easy to fix once I realized that I needed a separate SPF for
each subdomain. I had thought the record for the parent domain would cover
it, but I guess I was the only person who thought that.
On Wed, Jan 24, 202
Hi,
I knew that Google was going to start requiring SPF or DKIM (in addition
to other sender guidelines [1]. But I thought they were starting
February 1st, per their own sender guidelines.
I saw a bounce from a system (cron job output) trying to send directly
to gmail.com, no forwarding inv
11 matches
Mail list logo
