Skip to content

Update "02 Mismatch between company name and email address" snippet #294

@cappaxyz

Description

@cappaxyz

Moving to using issues in the AC report to track modifying the default snippets used in DeskPro. This is so historical records of where we were, and how we got to our new state existing beyond our tenure, email or slack archives.

Existing snippet is

Dear  (),

We use RDAP and Whois information from the RIR to authenticate 
requests. To allow for minimum authentication information from RIR, 
your email address must match. We detected a mismatch and, therefore, 
are not accepting your application. Please alter your data and reply 
to this ticket.

These are the email addresses we could fetch from the ASNs belonging 
to this organization:

Please send a confirmation email from one of the addresses listed 
above. Alternatively, those on CC, please register and claim your 
organisation at https://www.peeringdb.com. You may also add the/an 
authoritative email as secondary email to the requesting account:

Best regards,

I propose updating snippet to:

Dear (),

Thank you for submitting your affiliation request in PeeringDB.

PeeringDB uses RDAP data from the relevant RIR to help authenticate 
affiliation requests. At present, we cannot verify that the primary, 
verified email address on the PeeringDB user account that submitted 
this request matches an email address listed against an entity in the 
RDAP data for the ASN.

For that reason, we are not yet able to approve the affiliation 
request.

The email addresses we were able to fetch from the RDAP data for the 
ASN are:

[insert listed RDAP email addresses]

To proceed, please use one of the following options:

1. Update the RDAP data for the ASN so that it includes the primary, 
   verified email address used by the PeeringDB account that submitted 
   this request. Once this has been updated, please reply to this ticket 
   so we can review the request again.
2. Send a reply on this email chain to support@peeringdb.com from one 
   of the email addresses listed in the RDAP data above, confirming that 
   the affiliation request should be approved.
3. Create a new PeeringDB user account using one of the email 
   addresses listed in the RDAP data above, then submit a new affiliation 
   request from that account. That request should be approved 
   automatically. Once approved, you can use that account to approve the 
   existing affiliation request. You may then either keep the new account 
   as an additional administrative account or delete it if it is no 
   longer required.

Please reply to this ticket once you have completed one of the options 
above, or if you believe the RDAP information we have identified is 
incorrect.

Best regards,

2 yes votes (in addition to mine) should be sufficient; please give me a yes or submit your proposed variation.

Metadata

Metadata

Assignees

Labels

DeskPROSnippetsTo track snippet changes within DeskPro

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions