Re: [anti-abuse-wg] Verification of abuse contact addresses ?
Fi Shing, I'm sure verifying the delivery of 70k e-mails (or however many is in the database) can be done in a few hours. But Marco's response mentions to *correcting* the contact addresses, not just verifying them. That involves working with human beings, so it makes sense that it will take a while. Cheers, -- Shane On 08/03/2019 11.07, Fi Shing wrote:
If it takes more than a week to verify your entire database, there is the first sign that something is wrong with your system.
-------- Original Message -------- Subject: Re: [anti-abuse-wg] Verification of abuse contact addresses ? From: Marco Schmidt <mschmidt@ripe.net <mailto:mschmidt@ripe.net>> Date: Thu, March 07, 2019 10:03 pm To: "Ronald F. Guilmette" <rfg@tristatelogic.com <mailto:rfg@tristatelogic.com>>, anti-abuse-wg@ripe.net <mailto:anti-abuse-wg@ripe.net>
Hello Ronald,
We are planning to publish an updated timeline soon.
Ultimately, our implementation will depend of the level of cooperation we get from LIRs and the nature of issues that need to be fixed before an abuse contact can be updated (for example, some organisations may need to reset their maintainer password).
Over the next few weeks we will be analysing our progress, to make a realistic estimation. From observations so far, we think we might be able to finish our initial validation of all abuse contacts within six months - but it is still too early to make any strong predictions.
Kind regards, Marco Schmidt RIPE NCC
On 05/03/2019 21:51, Ronald F. Guilmette wrote: > In message <9c95c110-d5a3-e94a-6b3c-b02030736e7c@ripe.net <mailto:9c95c110-d5a3-e94a-6b3c-b02030736e7c@ripe.net>>, > Marco Schmidt <mschmidt@ripe.net <mailto:mschmidt@ripe.net>> wrote: > >> It is correct that the implementation phase is still ongoing. Currently >> we are validating all the abuse contact information referenced in LIR >> organisation objects. Then we will proceed with the validation of abuse >> contacts referenced in LIR resource objects - the example that you >> mentioned belongs to this group. And finally all abuse contacts >> referenced in End User (sponsored) objects will be validated. > Thanks for the info Marco. > > I guess the only question I would ask is this: Is there a published > timeline for how this whole process is planned to play out, and for > when it is planned to be completed? > > > Regards, > rfg >
Hi I'm fairly new here. This is a formidable task, and not easily achieved. So kudos to RIPE for doing this. The abuse contacts already there helped me a lot. I don't appreciate people who can't even stand up with their real names, just pointing out that others are lame. We make this a better world by helping with advice that empowers, not with diminish comments. Cheers Serge On 08.03.19 11:40, Shane Kerr wrote:
Fi Shing,
I'm sure verifying the delivery of 70k e-mails (or however many is in the database) can be done in a few hours.
But Marco's response mentions to *correcting* the contact addresses, not just verifying them. That involves working with human beings, so it makes sense that it will take a while.
Cheers,
-- Shane
On 08/03/2019 11.07, Fi Shing wrote:
If it takes more than a week to verify your entire database, there is the first sign that something is wrong with your system.
-------- Original Message -------- Subject: Re: [anti-abuse-wg] Verification of abuse contact addresses ? From: Marco Schmidt <mschmidt@ripe.net <mailto:mschmidt@ripe.net>> Date: Thu, March 07, 2019 10:03 pm To: "Ronald F. Guilmette" <rfg@tristatelogic.com <mailto:rfg@tristatelogic.com>>, anti-abuse-wg@ripe.net <mailto:anti-abuse-wg@ripe.net>
Hello Ronald,
We are planning to publish an updated timeline soon.
Ultimately, our implementation will depend of the level of cooperation we get from LIRs and the nature of issues that need to be fixed before an abuse contact can be updated (for example, some organisations may need to reset their maintainer password).
Over the next few weeks we will be analysing our progress, to make a realistic estimation. From observations so far, we think we might be able to finish our initial validation of all abuse contacts within six months - but it is still too early to make any strong predictions.
Kind regards, Marco Schmidt RIPE NCC
On 05/03/2019 21:51, Ronald F. Guilmette wrote: > In message <9c95c110-d5a3-e94a-6b3c-b02030736e7c@ripe.net <mailto:9c95c110-d5a3-e94a-6b3c-b02030736e7c@ripe.net>>, > Marco Schmidt <mschmidt@ripe.net <mailto:mschmidt@ripe.net>> wrote: > >> It is correct that the implementation phase is still ongoing. Currently >> we are validating all the abuse contact information referenced in LIR >> organisation objects. Then we will proceed with the validation of abuse >> contacts referenced in LIR resource objects - the example that you >> mentioned belongs to this group. And finally all abuse contacts >> referenced in End User (sponsored) objects will be validated. > Thanks for the info Marco. > > I guess the only question I would ask is this: Is there a published > timeline for how this whole process is planned to play out, and for > when it is planned to be completed? > > > Regards, > rfg >
-- Dr. Serge Droz Member of the FIRST Board of Directors Senior Advisor ICT4Peace https://www.first.org https://www.ict4peace.org
In message <20190308030704.af7f9f79718891d8e76b551cf73e1563.3317785c9a.wbe@email19.godaddy.com>, "Fi Shing" <phishing@storey.xxx> wrote:
If it takes more than a week to verify your entire database, there is the first sign that something is wrong with your system.
For whatever little it is worth, I would just like to say that I am in general agreement with the proposition that it should be possible, in the very short run, to reliably determine which, among a set a email addresses, perhaps even numbering up to a million, are or are not producing undeliverable bounce responses. That having been said, I should also note that making this determination with high accuracy is not nearly as easy as some folks might imagine, due mostly to the utter lack of standards when it comes to the format of undeliverable bounce responses. And thus, some amount of manual "eyeballing" may be involved with any attempt to do this at scale. Regards, rfg
participants (4)
-
Fi Shing
-
Ronald F. Guilmette
-
Serge Droz
-
Shane Kerr