Bugzilla

(In reply to DevTeam from comment #191)
> One outgoing SMTP service, say 'john' at 'service1' defined by the hostname.
> Two incoming IMAP services say 'john' at service1 and 'sales' at service1, but both accounts are setup to use the same outgoing service, where while most people think of this as a 'single service'.. there is no real way to 'link' them up together.. 
> 
> Remember, the idea is to make this simple for the average user, and simple for them to say, 'Yeah, I approve that device' like they can do with most other services.

It must not be made too "simple" at the expense of privacy. Also, the SMTP service can even be at server2 (service2) unrelated to service1.

Also remember the different servers may need different clientID contents (the spec mentions MAC address, licence number, anything) so there is absolutely no general expectation that any common clientID has to be used for different servers, not even for the incoming and outgoing part of what you call 'service' (one username). Those can be 2 separate servers with different clientID requirement even with same provider.

(In reply to DevTeam from comment #191)
> One outgoing SMTP service, say 'john' at 'service1' defined by the hostname.
> Two incoming IMAP services say 'john' at service1 and 'sales' at service1, but both accounts are setup to use the same outgoing service, where while most people think of this as a 'single service'.. there is no real way to 'link' them up together.. 
> 
> Remember, the idea is to make this simple for the average user, and simple for them to say, 'Yeah, I approve that device' like they can do with most other services.

It must not be made too "simple" at the expense of privacy. Also, the SMTP service can even be at server2 (service2) unrelated to service1.

Also remember the different servers may need different clientID contents (the spec mentions MAC address, licence number, anything) so there is absolutely no general expectation that any common clientID has to be used for different servers, not even for the incoming and outgoing part of what you call 'service' (one username). Those can be 2 separate servers with different clientID requirement even with same provider.
This means, it is not as simple for the user as "I approve that device". You never explained how the user seeing some random string in the server UI can decide that "yes, this is my device" when he never saw that string. It is you trying to hide this clientID from the user making him unaware of it.