Dobes,
Sounds like a good strategy. You should be aware of the verifiedEmail
field in the auth_info API response. This field isn't always present,
but if it is there, you can trust that the email address provided in
that field has been verified to belong to the user who is signing in.
Google, Yahoo both provide verified email addresses. Other providers
let the user send whatever email they want without actually confirming
it, acting mainly as a form-filler. Unverified emails are available
from many providers and are placed in the "email" field of the
auth_info response.
So, for both sign-in and register, let them authenticate using RPX and
then if a verifiedEmail address is found you can use that without
sending them the confirmation email. If a non verified email is
found, take care to send them a confirmation email to verify that they
do indeed own that address.
Cheers,
Brian Ellin