On 9 Apr 2018, at 09:51, Dave <dave.beckett.uk@...> wrote:

i was told, that i am on the Alpha team.

the confusion, is with the 3 different mailing lists, as this one, use to be the beta list, and now i think it is the general list, but i am still trying to work it out, like many others.

-----Original Message----- From: Chuck Dean
Sent: Monday, April 09, 2018 9:12 AM
To: hello@flicktype.groups.io
Subject: Re: [flicktype] Test message to Flicktype subgroups and former group address

I suggest you go to your phone, and put your finger on your FlickType icon. If it says Fliktype beta, then you are a beta tester

Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.

Our 1972 Honda 600 Coupe

Our 1961 Vespa 400

On Apr 9, 2018, at 1:02 AM, Dave <dave.beckett.uk@...> wrote:

i have just woke up, and i am still a lot confused.

what list am i posting to? hmmmm. lol.

Dave.


-----Original Message----- From: Paula Page
Sent: Monday, April 09, 2018 7:33 AM
To: hello@flicktype.groups.io
Subject: Re: [flicktype] Test message to Flicktype subgroups and former group address

But which subgroup are we supposed to be joining? And if everyone is joining both, what is the point of the subgroups? Just asking, because I’m still a bit confused.

Paula

On 9 Apr 2018, at 05:29, Alan Lemly <walemly@...> wrote:

Chuck,



Thanks for explaining this. Yes, you're right that those wanting to post to the FlickType alpha and beta subgroups must subscribe to them. You can do so by sending a blank email to:



Alpha subgroup: alpha+subscribe@flicktype.groups.io

Beta subgroup: beta+subscribe@flicktype.groups.io



The links following subgroup and colon above are live and should generate a new email in your email client when executed. Simply send that message and you'll receive a confirmation message which you must reply to in order to confirm your subscription to the subgroup.



I think messages posted to flicktype@groups.io will show as being sent to hello@flicktype.groups.io but I'm not positive of this. When I tried posting to hello@flicktype.groups.io, I thought I got an error message.



I'm sure Kosta or Ashley will chime in with some more direction on how they want the list to proceed with posting to the subgroups.



Alan



-----Original Message-----
From: hello@flicktype.groups.io [mailto:hello@flicktype.groups.io] On Behalf Of Chuck Dean
Sent: Sunday, April 08, 2018 11:09 PM
To: hello@flicktype.groups.io
Subject: Re: [flicktype] Test message to Flicktype subgroups and former group address



Hello Alan,

When I send an email to the email address that begins with hello, it ends up coming back to hear.



When I send an email to the email address that begins with beta, it goes to the beta sub group, and is sent back to my email address.

I m not sure what this proves, but I think everybody who wants to be on the new beta list will have to subscribe at the website.



Chuck (mobile)

Pleez x cuze enny tie ping or spelin air ores.



Our 1972 Honda 600 Coupe



Our 1961 Vespa 400

On Apr 8, 2018, at 7:49 PM, Chuck Dean < <mailto:cadean329@...> cadean329@...> wrote:

Hi Alan,

I tried to email you on the other post that you just left, and it said that it was an invalid address. So I am trying you on this post.

This is where I went to find a sub groups:

<https://flicktype.groups.io/g/beta/messages> https://flicktype.groups.io/g/beta/messages

Chuck (mobile)

Pleez x cuze enny tie ping or spelin air ores.

Our 1972 Honda 600 Coupe

Our 1961 Vespa 400

On Apr 8, 2018, at 7:30 PM, Alan Lemly < <mailto:walemly@...> walemly@...> wrote:

Hi List,

Okay, I'm still scratching my head a bit. I posted the below message

as explained in order to test posting to the subgroups. I got back

three Delivery Status Notification Failure messages from the Mail

Delivery Subsystem for each message sent to alpha, beta, and hello

followed by @flicktype.groups.io. The failure message contained the following:

Message not delivered

Your message couldn't be delivered to <mailto:alpha@flicktype.groups.io> alpha@flicktype.groups.io

because the remote server is misconfigured. See technical details

below for more information.

The response from the remote server was:

510 5.1.1 Your email address, <mailto:walemly@...> walemly@..., is not subscribed to

that group.

However, the cc: sent to <mailto:flicktype@groups.io> flicktype@groups.io did come through as the

below message I believe to which I'm now replying. I'm confused because the To:

address in this message to which I replied is

<mailto:hello@flicktype.groups.io> hello@flicktype.groups.io which didn't seem to work when I typed it

in directly. I don't believe I made a typo but anything is possible.

Hopefully, Kosta or Ashley or someone with more experience with

subgroups in Groups.io can chime in with some guidance.

Alan Lemly

-----Original Message-----

From: <mailto:hello@flicktype.groups.io> hello@flicktype.groups.io <mailto:[mailto:hello@flicktype.groups.io]> [mailto:hello@flicktype.groups.io] On

Behalf Of Alan Lemly

Sent: Sunday, April 08, 2018 9:12 PM

To: <mailto:hello@flicktype.groups.io> hello@flicktype.groups.io

Cc: <mailto:flicktype@groups.io> flicktype@groups.io

Subject: [flicktype] Test message to Flicktype subgroups and former

group address

Hi List,

I'm still learning about subgroups on Groups.io but I'm testing

sending a message to the new alpha and beta subgroups Kosta wrote about earlier today.

I'm not sure if we have to join these subgroups or if everyone

already in the main FlickType group was automatically added. I also

am unclear why the former < <mailto:flicktype@groups.io> mailto:flicktype@groups.io>

<mailto:flicktype@groups.io> flicktype@groups.io address no longer works since it was the master

group but Kosta's message below seems to imply that general group

messages should go to < <mailto:hello@flicktype.groups.io> mailto:hello@flicktype.groups.io>

<mailto:hello@flicktype.groups.io> hello@flicktype.groups.io which sounds like another subgroup.

This test message was sent to the three subgroups of alpha, beta, and

hello in the To: field and to the original main group of flicktype in the CC:

field in order to see what happens.

Alan Lemly