What happens to emails when someone a year from now sends an email to
dspace-t...@lists.sourceforge.net, since a decade of random documentation
suggests so, they've historically been subscribed, and used to just work?
I'm guessing they'll get a bounce, can there be a message in the bounce?
This
Hi Peter,
Yes, once we've migrated, we'll bounce back any emails to old SF lists.
We can customize the bounce message to tell them that the list has
migrated, etc. We'll also hide all old SF lists (making them not
visible to public by default), unsubscribe everyone and turn off any new
Hi Developers / Committers,
As of yet, I've heard little feedback on the proposed mailing list
migration. So, I'm assuming no one else has major objections to any of
these options.
Currently, I'm leaning towards just migrating all mailing lists +
archives into Google Groups, even though the
How are you planning to do the migration, as the Groups Migration API
documentation suggests that it does take notice of the Date: field in the
(RFC 822 formatted) messages?
G
On 3 August 2015 at 15:40, Tim Donohue tdono...@duraspace.org wrote:
Hi Developers / Committers,
As of yet, I've
Hi Graham,
The Groups Migration API unfortunately only works for Google Apps
Groups. It won't work for normal googlegroups.com Groups (annoying, I
agree). See it's prerequisites:
https://developers.google.com/admin-sdk/groups-migration/v1/guides/prerequisites
(There's also no way to migrate a
Hi Developers,
In case you haven't seen recent Developer Meeting notes, I wanted to
update everyone here on recent working investing the migration of our
DSpace mailing lists off of SourceForge (lists.sourceforge.net). As you
may have heard, SourceForge had some major stability issues recently
