Dear all, There have been concerns lately about e-mail addresses in the "changed" fields being used to send unsolicited e-mail messages. Please review this discussions in the mailing archives. Archives for the RIPE mailing lists are available at http://www/info/maillists.html After deliberations in the db-wg mailing list, the RIPE NCC suggests the implementation of the following changes: - By default changed fields won't be shown in queries. - These fields can be retrieved using a query option (whois -c). - These fields will not be compared against incoming data when deleting the object. The RIPE NCC would appreciate comments on the mentioned changes before implementation begins. The comment period will be a week since the posting of this message. Please direct your comments directly to the RIPE NCC using the ripe-dbm@ripe.net mailbox. The changes will be implemented in the next release of the RIPE DB code, due July 15th, 1998. Best regards, Joao Damas RIPE DB group RIPE NCC
Dear all,
Hi,
- By default changed fields won't be shown in queries. - These fields can be retrieved using a query option (whois -c).
do we need someone who stops the time when the first anti-spam tool has deciphered the new option ? can we start a discussion to hide the notify: fields as well ? Here this address gets an order of magnitude more anti-spam mail than any entry found in a changed: line. Sorry, if this sounds sarcastic. I'm just trying to prevent people from wasting time that could be better spent in the forthcoming reimplementation of the database. Greetings, -- i.A. Michael van Elst / phone: +49 721 6635 330 Xlink - Network Information Centre \/ fax: +49 721 6635 349 Vincenz-Priessnitz-Str. 3 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster@xlink.net [ Xlink Internet Consulting GmbH, Sitz Koeln ] [ Amtsgericht Koeln HRB 3526, Geschaeftsfuehrer: Michael Rotert ]
Michael van Elst <mlelstv@xlink.net> writes:
do we need someone who stops the time when the first anti-spam tool has deciphered the new option ?
The difference is that then it is deliberate and not accidental. What we wnat to do is prevent accidental and unwanted use of e-mail addresses which are very often not connected to the database object anyways. I get dozens of e-mails a day because I used to change database objects more than 7 years ago.
can we start a discussion to hide the notify: fields as well ? Here this address gets an order of magnitude more anti-spam mail than any entry found in a changed: line.
I consider this well-directed e-mail as the notify attribute, as the mnt-notify, should be maintained current and point to a mailbox maintaining the database object and the resource associated with it. It is then a matter of local policy whether you answer this kind of mail or you do not.
Sorry, if this sounds sarcastic. I'm just trying to prevent people from wasting time that could be better spent in the forthcoming reimplementation of the database.
We looked at this and it is not a big deal to implement. Daniel
Joao, At 10:59 am +0200 25/6/98, Joao Luis Silva Damas wrote:
After deliberations in the db-wg mailing list, the RIPE NCC suggests the implementation of the following changes:
I think the changes sound fine but I have been using a widely-used USENET convention for making my email address easily readable by a human but not so easy for a machine (since most machine-processing of bulk lists of email addresses is, I understand, case-insensitive). E.g.
Update OK: [person] JM1-RIPE (John Martin)
person: John Martin address: TERENA Secretariat address: Singel 468 address: NL-1017 AW Amsterdam address: The Netherlands phone: +31 20 530 4488 fax-no: +31 20 530 4499 e-mail: martin@NOSPAMterena.nl nic-hdl: JM1-RIPE remarks: This object is no longer maintained by hostmaster@cwi.nl remarks: Remove the "NOSPAM" from the email addresses to contact owner changed: hostmaster@cwi.nl 940816 changed: ripe-dbm@ripe.net 950809 changed: martin@NOSPAMterena.nl 980624 source: RIPE
...which I admit, is not perfect, but perhaps better than nothing - right? (And it works quite well for my USENET postings... so far). I dont always use "NOSPAM" but I try to make it obvious. And in the case of the "changed:" fields, the people who _should_ be interested _should_ know what to do ;-> Rgds, John John Martin TERENA, Singel 466-468, NL - 1017 AW Amsterdam phone: +31 20 530 4488 ** fax: +31 20 530 4499 ** http://www.terena.nl/ ** Please note new telephone and fax numbers
hello, world\n John Martin wrote: # Joao, # # At 10:59 am +0200 25/6/98, Joao Luis Silva Damas wrote: # >After deliberations in the db-wg mailing list, the RIPE NCC suggests the # >implementation of the following changes: # # I think the changes sound fine but I have been using a widely-used USENET # convention for making my email address easily readable by a human but not # so easy for a machine (since most machine-processing of bulk lists of email # addresses is, I understand, case-insensitive). E.g. # # >Update OK: [person] JM1-RIPE (John Martin) # > # >person: John Martin # >address: TERENA Secretariat # >address: Singel 468 # >address: NL-1017 AW Amsterdam # >address: The Netherlands # >phone: +31 20 530 4488 # >fax-no: +31 20 530 4499 # >e-mail: martin@NOSPAMterena.nl # >nic-hdl: JM1-RIPE # >remarks: This object is no longer maintained by hostmaster@cwi.nl # >remarks: Remove the "NOSPAM" from the email addresses to contact owner # >changed: hostmaster@cwi.nl 940816 # >changed: ripe-dbm@ripe.net 950809 # >changed: martin@NOSPAMterena.nl 980624 # >source: RIPE # # ...which I admit, is not perfect, but perhaps better than nothing - right? # (And it works quite well for my USENET postings... so far). I dont always # use "NOSPAM" but I try to make it obvious. # # And in the case of the "changed:" fields, the people who _should_ be # interested _should_ know what to do ;-> John, you also have NOSPAM in your e-mail: field. If I'd see this in one of DFNs customer's person objects, I'd really get angry. I'm trying to contact our >1000 admin-cs and tech-cs on a regular basis, to see whether they're still alive and kicking. This happens automatically by a script. Now if I'd see martin@NOSPAMterena.nl in there -- I'd dump you right away. Sorry, but I don't regard anti spam measurements as a justification for littering the RIPE DB (which *already* has a lot of bogus information) with dead email addresses. I *do* want to automate as much as I can. Having to manually frob email addresses is absolutely not acceptable. Just to put the spam discussion on the right track (IMHO :-), yes I do get 1 to 5 spams per day, what the heck, I could not care less -- I have a delete button. Let the flame fest begin. Regards, Jens Schweikhardt -- ## Network Operation Center, DFN-Verein Geschdftsstelle Stuttgart ## ## http://www.noc.dfn.de/ finger trouble@noc.dfn.de wartung@noc.dfn.de ## ## >>>>>> mailto: noc@noc.dfn.de <<<<<< ## ## Phone: 0711-63314-112, FAX 0711-63314-133 (business hours) ##
On Thu, Jun 25, 1998 at 11:44:12AM +0200, Jens Schweikhardt wrote:
Just to put the spam discussion on the right track (IMHO :-), yes I do get 1 to 5 spams per day, what the heck, I could not care less -- I have a delete button.
You seem to be very patient- I get >7000 emails/month and my `d' button has the use that a spacebar should. -- Yiorgos Adamopoulos -- #include <std/disclaimer.h> mailto: Y.Adamopoulos@noc.ntua.gr -- Network Operations Center, NTUA, GREECE
participants (6)
-
Daniel Karrenberg -
Jens Schweikhardt -
Joao Luis Silva Damas -
John Martin -
Michael van Elst -
Yiorgos Adamopoulos