[db-wg] Complying with Mail Provider Requirements When Sending Mail from Whois

Professionally speaking, I agree on both Lutz statements.

---
Thierry Le Bris
thierry.le-bris at ovhcloud.com




> Le 20 mars 2024 à 07:51, Lutz Donnerhacke via db-wg <db-wg at ripe.net> a écrit :
> 
> * 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?
> 
> 
> -- 
> 
> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20240320/f59450b2/attachment.html>