This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] Complying with Mail Provider Requirements When Sending Mail from Whois
- Previous message (by thread): [db-wg] Complying with Mail Provider Requirements When Sending Mail from Whois
- Next message (by thread): [db-wg] Complying with Mail Provider Requirements When Sending Mail from Whois
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at gmail.com
Wed Mar 20 13:59:02 CET 2024
On Wed, 20 Mar 2024 at 07:51, Lutz Donnerhacke via db-wg <db-wg at ripe.net> 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 failed on > > authentication (that you may miss), doesn't that also eat up brain > > cycles? > > Please do not assume that LIR activities are single handed everywhere. > Several LIRs do have an automation (i.e. netbox) to update the RIPE DB. > Others might have multiple independent people working with RIPE on > their own behalf. So notifications, especially the notify: attribute > are currently in use. > > > So how about a compromise. A full audit trail of all details of all > > changes to all your data available by default to designated people > > through your portal account. Plus a daily email summarising all the > > changes also sent to people whose email addresses are set up in the > > portal account. So still no notif email addresses needed all across > > the database. This could even be done per maintainer. > > How about using the notify: attribute for notifications? 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. And you continue to get half an audit trail sent to your notify addresses. As the environment the database operates in continues to move forward, the database just limps on to the next problem and we hope we can patch it up again to keep it working. Even if that means a slightly further degraded system like blocking email addresses we have to do now. cheers denis co-chair DB-WG ======================================================== DISCLAIMER Everything I said above is my personal, professional opinion. It is what I believe to be honest and true to the best of my knowledge. No one in this industry pays me anything. I have nothing to gain or lose by any decision. I push for what I believe is for the good of the Internet, in some small way. Nothing I say is ever intended to be offensive or a personal attack. Even if I strongly disagree with you or question your motives. Politicians question each other's motives all the time. RIPE discussion is often as much about politics and self interest as it is technical. I have a style of writing that some may not be familiar with, others sometimes use it against me. I also have OCD. It makes me see the world slightly differently to others. It drives my mind's obsessive need for detail. I can not change the way I express my detailed opinions. People may choose how to interpret them. ======================================================== > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/
- Previous message (by thread): [db-wg] Complying with Mail Provider Requirements When Sending Mail from Whois
- Next message (by thread): [db-wg] Complying with Mail Provider Requirements When Sending Mail from Whois
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]