开云体育

Last week I seeded my new groups.io group by exporting the Y! group member list, converting it for Direct Add, and uploading the file.? I am seeing evidence that in some cases with multiple email addresses known to the Y! group, the email address that Y! gave me in the export was not the email address that the Y! group was set to deliver group messages to.?
Is this a known "feature" of the Y! group export function?
If so, is there any chance that the "Easy Group Transfer" function will be able to transfer the Y! group email addresses that were active delivery addresses in cases of multiple addresses known to the Y! group?

Also, FYI, yesterday a large number of @yahoo.com email addresses were listed in Activity as "bouncing", when quite a few messages had seemingly been delivered to them properly prior to that. I'm assuming this is further evidence of Y! mail issues.
John

John,

I am seeing evidence that in some cases with multiple email addresses
known to the Y! group, the email address that Y! gave me in the export
was not the email address that the Y! group was set to deliver group
messages to.

In the export provided in the Manage Members feature only the second column contains subscription addresses. The first column may contain email addresses, but those are the member's sign-in ID, which is not necessarily the same as their subscription email address. You should disregard any email addresses from the first column.

If so, is there any chance that the "Easy Group Transfer" function
will be able to transfer the Y! group email addresses that were active
delivery addresses in cases of multiple addresses known to the Y!
group?

The transfer agent will only use the proper subscription addresses. It will also skip any of those addresses which have "Bouncing" status.

To emulate that with an export you'd have to also export the Bouncing list, and remove from the complete list those email addresses that appear also in the Bouncing list. What I did in Excel was use a second sheet in the file to hold the Bouncing list, then put a Match() function in a spare column of the full list to identify which are also in the Bouncing list. Then filtering or sorting on that matching column separates out the non-bouncing addresses.

Or... Use the Chrome app to export your Y!Group's member's list. This produces more comprehensive information about each membership, and in particular includes a column that identifies whether the address is bouncing or not. The transfer agent uses access similar to the Chrome app.

Also, FYI, yesterday a large number of @yahoo.com email addresses were
listed in Activity as "bouncing", when quite a few messages had
seemingly been delivered to them properly prior to that. I'm assuming
this is further evidence of Y! mail issues.

I don't use Yahoo Mail (for aught but testing), but I've read others commenting about problems with their account, even sending direct from one Yahoo Mail address to another.

Shal


--
Help: /static/help
More Help: /g/GroupManagersForum/wiki
Even More Help: Search button at the top of Messages list

Thanks for the link to the Chrome app for downloading more data fields from Y! group membership.? I'm still curious why the "First Name" and "Last Name" fields shown in the Y! group list aren't included in either of the exports.?
I think I'll update the "Direct Add" wiki page I created to include the link to the chrome app.
I had never cleared "bouncing" members from the Y! group, so I did that prior to initiating the transfer, though I did take an export that included them.? If that will create any kind of an issue during the "easy transfer" of old Y! group content, I could temporarily "Direct Add" them here.
Also, Kudos for making server responses for email non-delivery available - it made my explanation to those affected more convincing.
John

John,

I'm still curious why the "First Name" and "Last Name" fields shown in
the Y! group list aren't included in either of the exports.

That's interesting. I don't know, maybe the UI is looking those up from some other table based on one of the fields that is there.

I had never cleared "bouncing" members from the Y! group, so I did
that prior to initiating the transfer, though I did take an export
that included them.

That was unnecessary work on your part. The transfer agent skips bouncers anyway.

If that will create any kind of an issue during the "easy transfer" of
old Y! group content, I could temporarily "Direct Add" them here.

The only issue I'm aware of is that any content "owned" by them (any subscription email address not in the Groups.io group at the time of the transfer, or copied in with it) will end up attributed to you, the logged in address that initiated the transfer.

Direct Adding them before the transfer would "fix" that, but it isn't clear to me that it would be worth the effort.

Also, Kudos for making server responses for email non-delivery
available - it made my explanation to those affected more convincing.

Kudos go to Groups.io, and specifically to Mark Fletcher. He doesn't read this group. If Groups.io had any other employees (which is bound to be true at some point) I don't know if any of them would read GMF. Probably not until there's someone dedicated to a support role.

Shal


--
Help: /static/help
More Help: /g/GroupManagersForum/wiki
Even More Help: Search button at the top of Messages list

To export mine (1,150 members) I just went to Management > Manage Members, scrolled down to the end, copied all of the data, pasted it into my text editor, copied that, and pasted it into Excel. There was some cleanup required but it worked well.

Btw, the Chrome app didn't work when I tried it.