开云体育

Thanks for the suggestion, I did post a suggestion to the beta list.

On further reflection however, I think it's problematic for a "not confirmed" subscriber to appear in the pending approval list in the first place.? I never saw this with Yahoo.? Granted, joining Groups.io and subscribing to a group are essentially separate processes.? Even so, there is clearly a design feature here that I don't yet understand.

I have observed that the system behaves differently depending on how a subscription request is submitted. The following is all assuming that the subscriber does not already have an established/confirmed Groups.io account, as is often the case.? Also note that my group requires moderator approval of new subscribers, and that the group makes use of the "pending subscription" notice feature (a big time saver).

Subscription via email: If a subscriber sends an email to [listname][email protected] they get a straightforward "reply to confirm" return message.? At this initial point the group owner is blissfully unawares.? Only after the subscriber replies (confirming their Groups.io account) is when the system 1) puts the subscriber on the group's pending approval list (with no "NC" tag, of course); 2) sends the "pending subscription" notice to the subscriber; and 3) sends the owner a notice that a new subscriber is awaiting their approval.? This is all logical and straightforward; no problems.

Subscription via web: The process is quite different when a subscriber selects the "apply for membership" button on the group's web page, then enters their email address when prompted.? It is at this initial point that the system 1) places the subscriber on the group's pending approval list (with the "NC" tag); 2) sends both the "pending subscription" notice and the "request for confirmation" messages to the subscriber; and 3) sends the owner a notice that a new subscriber is awaiting their approval.? Again, this all happens before the subscriber confirms their Groups.io account.? It's a situation with great potential for confusion for both subscriber and owner.

As a further complication, the content of the "request for confirmation" message is also different from the first case.? I found it to be repetitive and confusing, especially coming on the heels of the "pending subscription" notice.? This is perhaps a separate issue that can be set aside for the moment.

Bottom line: It seems to me that the subscription process should work the same regardless of how the request was initiated, and that an unconfirmed subscriber should never be placed on the pending approval list.? That would obviate the need for the "NC" tag.

Can anyone explain why the "subscription via web" and the "subscription via email" processes are so different?? What am I missing??

Thanks.

?????????????? -- Charlie