Hi Denis,
> On 21 Mar 2024, at 04:03, denis walker via db-wg wrote:
>
> Hi Sander and others
>
> On Wed, 20 Mar 2024 at 23:06, Sander Steffann wrote:
>>
>> Hi Denis,
>>
>>> So we just stay where we are, yet again, with the NCC sending out tens
>>> of thousands of emails every day to some of
Denis,
On 21/03/2024 04.03, denis walker via db-wg wrote:
-we have no documented business requirements for either the RIPE
Database or a public registry
This is simply not true.
https://www.ripe.net/publications/docs/ripe-767/
All because you disagree with the published requirements does not
* Denis Walker wrote:
> [... it's old ...]
>
> Just a quick list from memory of some problems surrounding the
> database. 'Hear from users'...Whenever I bring up any issues like
> this, I either hit a total wall of silence or I am hit with familiar
> negativity. NO one ever talks about the future o
Hi Sander and others
On Wed, 20 Mar 2024 at 23:06, Sander Steffann wrote:
>
> Hi Denis,
>
> > So we just stay where we are, yet again, with the NCC sending out tens
> > of thousands of emails every day to some of the almost a million email
> > addresses in the database and you all continue to get
Hi Denis,
> So we just stay where we are, yet again, with the NCC sending out tens
> of thousands of emails every day to some of the almost a million email
> addresses in the database and you all continue to get spam sent to
> those harvested email addresses.
You seem to perceive a problem that n
On Wed, 20 Mar 2024 at 07:51, Lutz Donnerhacke via db-wg wrote:
>
> * Denis Walker wrote:
> > But looking through lots of email notifications about changes that you
> > already know about, because you did them, and maybe in the middle is a
> > notification of an attempted security breach that fail
Professionally speaking, I agree on both Lutz statements.
---
Thierry Le Bris
thierry.le-b...@ovhcloud.com
> Le 20 mars 2024 à 07:51, Lutz Donnerhacke via db-wg a écrit :
>
> * Denis Walker wrote:
>> But looking through lots of email notifications about changes that you
>> already know about
* Denis Walker wrote:
> But looking through lots of email notifications about changes that you
> already know about, because you did them, and maybe in the middle is a
> notification of an attempted security breach that failed on
> authentication (that you may miss), doesn't that also eat up brain
On Tue, 19 Mar 2024 at 17:03, denis walker via db-wg wrote:
> Hi Gert
>
> On Tue, 19 Mar 2024 at 16:05, Gert Doering wrote:
> >
> > Hi,
> >
> > On Tue, Mar 19, 2024 at 03:55:26PM +0100, denis walker via db-wg wrote:
> > > This new anti-spam measure is a convenient point to reflect on how one
> >
Hi Gert
On Tue, 19 Mar 2024 at 16:05, Gert Doering wrote:
>
> Hi,
>
> On Tue, Mar 19, 2024 at 03:55:26PM +0100, denis walker via db-wg wrote:
> > This new anti-spam measure is a convenient point to reflect on how one
> > part of the RIPE Database is used. Notifications are just one part of
> > an
Hi,
On Tue, Mar 19, 2024 at 03:55:26PM +0100, denis walker via db-wg wrote:
> This new anti-spam measure is a convenient point to reflect on how one
> part of the RIPE Database is used. Notifications are just one part of
> an audit system. Many other parts are missing. To be sending out 30k
> emai
Colleagues
I know none of you want to talk about any redevelopment of the RIPE
Database. Not even doing it bit by bit. I keep reminding you that it
is a 30 year old design and barely fit for purpose in the modern
world. But still you all want to keep this dinosaur even though it is
now on life sup
Hi Lutz,
> On 15 Mar 2024, at 08:57, Lutz Donnerhacke via db-wg wrote:
>
>> In this release, we will implement mail bounce detection (i.e. an outgoing
>> message has permanently failed delivery) and also unsubscription (i.e. one-
>> click unsubscribe from a mail client). Once an address is undel
> In this release, we will implement mail bounce detection (i.e. an outgoing
> message has permanently failed delivery) and also unsubscription (i.e. one-
> click unsubscribe from a mail client). Once an address is undeliverable or
> unsubscribed, we will not send further Whois update acknowledgeme
Dear colleagues,
As part of the Whois 1.111 release planned for 28th March, we will make changes
to comply with new requirements for bulk email senders from two of the large
email providers, namely Google [1][2] and Yahoo [3][4]. The RIPE NCC are
reviewing these requirements across all our serv
15 matches
Mail list logo
