Oh no Mark, y'all stay well out there.

--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu

Our block group is organizing for the pandemic and trying to get the whole block involved. To that end, we are re-inviting many people who did not act on invites a long time ago. To to this, we are using "send again" from the Sent Invite page, but are discovering to our chagrin that the original (and now completely obsolete) custom messages sent to them years ago are going out to these people again. Hopefully I'm missing something, but I can't find a way to change it. I think the custom message should be editable when re-sending an invite.
--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu

On Mon, Mar 16, 2020 at 12:38 PM, Jim Avera wrote:

But ANY message from any user gets posted.

Another but, only if they have the specific email address assigned to the integration.  Highly unlikely that someone would accidentally create that address.  And you could also set the #email hashtag that will be assigned to them as moderated for a backup plan.

Duane

Ah,perfect!  (the From: and ReplyTo: headers point back to the originating sender).

Not so perfect after all!   This is an announce-only group, so only messages sent by moderators should get posted.  But ANY message from any user gets posted.

So the "email integration" thing is not usable except for completely-open groups.

On Mon, Mar 16, 2020 at 07:15 AM, Bruce Bowman wrote:

Jim -- Consider setting up an email integration for your group and have the forwarder send it's messages to that. 

Ah,perfect!  (the From: and ReplyTo: headers point back to the originating sender).  Thanks for the tip.

P.S. Is there a convention for marking a topic (like this one) "closed" or "solved"?

Hmm, there a BUG/REGRESSION may have crept in to the Direct-Add Notification stuff:

The help text says (I see now) that D-A Notifs are auto-sent if "active". But that is not the case, i.e. a D-A Notif. is not used automatically; and there is no checkbox to make a D-A Notification "active" (like there is for Welcome and Guidelines).

Here is the current help text for the D-A Notification:

When clicking on a map pin, the list of entries automatically scrolls below the map with the selected row being highlighted by a blue bar on the left side. However, if the pin relates to the last entry on the list, scrolling is not quite to the bottom of the page meaning an extra user action is required to show the selected row.

Andy

On Sun, Mar 15, 2020 at 11:27 PM, Jim Avera wrote:

If an email account is set up to auto-forward to a GIO group, then the resulting messages appear to be from the forwarding email mbox, not the original sender.   Consequently, a "reply" to the post goes to the forwarding mbox and just loops back to the group (and I suspect that GIO is checking subscriber privs based on the forwarding mbox instead of the original source mbox). 

Jim -- Consider setting up an email integration for your group and have the forwarder send it's messages to that. 

Regards,
Bruce

On Mon, Mar 16, 2020 at 03:28 AM, Jim Avera wrote:

You have been added by <owner name> to the <group name> group at Groups.io.

In cases where there are multiple owners and/or Mods with the relevant permissions, for clarity, <owner name> should really be <owner/mod doing the DA>.

Andy

When a subscriber is Direct Added, the first email they get is a canned message which the owner can not control except to insert text in the middle.  Some portions of that canned text can be inappropriate or confusing for reasons described in this GMF post: https://groups.io/g/GroupManagersForum/message/30412

I'd like to suggest either:

* Give owners complete control of that initial communication, OR

* Let owners control the initial part, and possibly also the final part, of that first email, and put the canned bits in the middle.

If you do need to force certain text to be included, force only what is strictly necessary and eliminate possibly-wrong/confusing bits (see referenced GMF post for specifics).


Possible implementations:

(1) Eliminate that initial email altogether (or provide an option to not send it), and make the "Direct Add" Notification work like the Welcome Notification, i.e. send it automatically to newly-DA'd subscribers, before the Welcome message (or possibly make it an alternative Welcome sent only to Directly-added subscribers).

The owner could then change the DA Notification as desired to introduce subscribers to the system.

A *default* D-A Notification would contain the canned text, to preserve today's behavior  by default (assumes DA Notif is made to work like Welcome).

--or--

(2) Like (1) above but require that the DA Notification include certain text, perhaps by requiring a "[Required Text]" token somewhere which gets substituted; or else always *append* the required text to the owner's D-A Notification (ideally displaying the added text in the Notification editor so the owner can see what the combined message will look like).  But allow the owner to control the first part of the message, and any group-specific information.

Thanks for considering this suggestion!



P.S. Here is a possible *default* D-A Notification with the forced bits in the middle:

Hello [Name],

You have been added by <owner name> to the <group name> group at Groups.io.

You can visit your group, start reading messages and adjust options here: https://groups.io/g/<group>.

<<BEGIN REQUIRED TEXT>>
The email for this group is: <group>@groups.io.

Most importantly, please add this email address to your safe sender list in your email client’s contacts. If you find emails from this group landing in spam, promo, or social folders, please move those emails to your primary inbox so that you can train your email client to put them directly in your inbox.

If this was a mistake, please click on the following link and you will be immediately removed:

<Unsubscribe link>

<<END REQUIRED TEXT>>

The Groups.io Team

The confirmation page for unfollowing a topic asks "unfollow this thread?" but should be "topic"
--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu

Changing a role from Moderator to Member is logged as "changed moderator permissions" but should be "changed role."
--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu

On Tue, Dec 18, 2018 at 05:34 PM, Shal Farley wrote:

If you think it will cause trouble in your groups don't enable it (allow members to edit without re-send), or enable it and require such edits be moderated, or don't allow members to edit at all.

I don't see a setting for requiring edited messages to be moderated. I would prefer that, at minimum, moderators should receive a notice of the edit, regardless of their settings. I don't really "need" to moderate but it seems prudent to at least be aware.

Bill

Not certain this is a bug rather than an unavoidable limitation.  My expectations might be unrealistic :-)

If an email account is set up to auto-forward to a GIO group, then the resulting messages appear to be from the forwarding email mbox, not the original sender.   Consequently, a "reply" to the post goes to the forwarding mbox and just loops back to the group (and I suspect that GIO is checking subscriber privs based on the forwarding mbox instead of the original source mbox).  In the web interface, I see a From: header referring to the forwarding mbox,  and the only reference to the actual originator is in a Return-Path: header.

This is different than when forwarding to an ordinary email address (at least a gmail address); then the From: header still refers to the original sender and a "reply" does the right thing.  When the forwarding mbox is at yahoo, an additional X-Yahoo-Forwarded: From (forwarding mbox) To (final recipient) header is included (I don't know how forwarded-from-gmail messages look).

GIO's SMTP server or something must be re-writing headers in a way which defeats forwarding like this.

WHY DO I WANT THIS, you might ask?  We formerly used an ordinary email mailbox for group messages; a "moderator" simply read the messages at that email account and forwarded them to the "subscribers".    Now we are switching to GIO, and I want to make the old "posting email address" auto-forward to the group, so users will not have to learn a new posting address, and so existing user instructions will still be correct enough to be usable.

(Thanks for all the great work!)

On Sun, Mar 15, 2020 at 10:17 PM, Michael Pavan wrote:

To clarify:

Simple switch(es) to turn off imposed (so called 'System') Hashtags.

Quite; I eventually worked out that those were the real subject of both this and the corresponding GMF thread; it is far from clear there as well.

Chris