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/[email protected]/
how to proceed with changed:
- Previous message (by thread): how to proceed with changed:
- Next message (by thread): how to proceed with changed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
kissg at sztaki.hu
kissg at sztaki.hu
Tue Jun 9 16:09:22 CEST 1998
James Adridge wrote: > If people change jobs then it should be possible to perform an inverse query > on the changed field in the same way as the admin-c, tech-c, etc. to permit > updating of all affected records. I think active ripe-ops are also unhappy if spammed newbies send them tons of complaining mails. Remember this philosophy: | For legal reasons, anyone and everyone that is related to an IP Address | or related higher domains or IP routes are included in the anti-spam | message, that way noone can say later, they didn't know or weren't | notified about the law. These peoples doesn't know and doesn't want to know what is the difference between changed and admin-c fields. They just see Yet Another E-mail Address To Born. Which of you wants to be "anyone and everyone"? I definitely not. A new idea: Every "changed" field should contain <president at whitehouse.gov>. So the Secret Service or the FBI will explain politely all of these newbies, that Lenin was right when he said: "To learn, to learn, to learn" (before writing) :-) Regards Gabor
- Previous message (by thread): how to proceed with changed:
- Next message (by thread): how to proceed with changed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]