This is correct — Code4Lib's free Google Workspace for the group was
disabled by Google, and the Journal's email address is one of the ones
caught up in that. The "[log in to unmask]" is the best way to reach us
now...I'll update the Journal's editorial board page.


Peter

On Sat, Jun 8, 2024 at 1:35 AM Cary Gordon <[log in to unmask]> wrote:

> I’ll take a wild guess, and say that we probably had one of the free
> community Google Apps accounts that they did away with a few years ago.
>
> The solution is to find some other source to host our email. Oregon State
> manages the domain, with DNS hosted on Cloudflare, so someone there (Ryan
> Wick?) could switch the MX records.
>
> Cary Gordon
> The Cherry Hill Company
> http://chillco.com
>
>
> On Fri, Jun 7, 2024 at 9:02 AM Jon Fackrell <[log in to unmask]>
> wrote:
>
> >  Hi Carolyn,
> >
> > I think the editorial board is still working on regaining access to
> > [log in to unmask] and are using [log in to unmask] in the meantime.
> >
> > Jon Fackrell
> >
> >
> > On Jun 7, 2024 at 9:44:34 AM, "Carolyn Pecoskie, Ms." <
> > [log in to unmask]> wrote:
> >
> > > Hi code4lib,
> > >
> > > I am trying to get in touch with the editorial board of the code4lib
> > > Journal, but I am finding that the journal email ([log in to unmask]
> > > <mailto:[log in to unmask]>) is giving me a bounce-back message in
> > > Outlook. Is anyone aware of any issues with this email address? Or is
> > there
> > > an alternative way to get in touch?
> > >
> > > Thanks, and happy Friday!
> > > Carolyn
> > >
> > > Carolyn Pecoskie (she/her/hers/elle)
> > > Metadata & Electronic Resources Librarian / Bibliothécaire, métadonnées
> > et
> > > ressources électroniques
> > > McGill University / Université McGill
> > > t. 1 (514) 398-1713 | [log in to unmask]<mailto:
> > > [log in to unmask]>
> > >
> >
>