If the abuse contact (ab...@ovh.net) is not responding to e-mails report the
lack of response to RIPE NCC, the RIR that delegated the resources to them. I
know that if members under APNIC fail to maintain an abuse and IRT contact
their account is suspended until it is validated.
I already
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
Tonight we received a huge wave of extortion spams from OVH hosted domains trying to get bitcoin payments. The senders
claim that recipients watched child porn.
This is the final straw for me to add a rule to reject all mail traffic from OVH until the sender is whitelisted. OVH is
completely
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
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
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
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,
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
On 2024-01-15 at 16:03 -0800, Randolf Richardson, Postmaster wrote:
> > I have seen my share of MUAs that behave in weird ways when
> > encountering things larger than it can handle, so you have
> > to always cope for them in the mail server. Implementing different
> > types of restrictions, and
Dnia 24.01.2024 o godz. 11:57:13 Randolf Richardson, Postmaster via mailop
pisze:
> > But, in reality not really worth the trouble.. domains are easy to
> > forge, and innocent companies maybe trying to verify the address,
> > because a bad guy used it in a contact form..
>
> Not when
> On 2024-01-23 12:35, Randolf Richardson, Postmaster via mailop wrote:
> >>> Hi folks,
> >>>
> >>> I suspect this exists, but can't come up with the right search.
> >>>
> >>> I have domains that should never receive mail. I'd like a milter that
> >>> looks for mail to those domains and feeds the
This thread had me think for long enought that I thought it might be useful to
do a short (for me at least) writeup -
A Simpler Life: Trapping Spambots Based on Target Domain Only
https://nxdomain.no/~peter/domain-only-trapping.html
(or tracked
On 1/23/24 1:40 PM, Michael W. Lucas via mailop wrote:
Hi folks,
Hi,
I have domains that should never receive mail. I'd like a milter that
looks for mail to those domains and feeds the IP of the sender to an
outside program.
I'm interpreting your statement to mean that you are talking
14 matches
Mail list logo
