I am behind Mike with this.
I approve of the concept that a member should NOT be dropped because of a spam claim.
Having membership Deleted for a spam claim is counter to the interests of Groups.io, to the
Group Owner and Member. And rising tension will not serve the Email Service Provider well,
ESP. lose-lose
If a FeedBackLoop, FBL message comes in could this be challenged and managed by
Groups.io at a higher level?
Challenged on the basis that a legitimate group member received a legitimate group mail then
the source of the FBL must actually be at fault.
To be managed by the ESP to the satisfaction of Groups.io, Group Owner and Group Member.?
The FBL is generated and sent by the member's? ESP. Email Service Provider, who must take
responsibility for their actions. Possibily by making provision for a White List.
Maybe Groups.io can broker a white list entry for each member.?
Maybe a contract between Groups.io and the ESP which shoves responsibility onto the FBL
generator and what they are going to do about it..
OK,
Tony??
On 3 Apr 2018 at 14:20, mike@... wrote about :
Subject : Re: [GMF] Automatic Deletion of Mem
I was just in a post a "new" item about the subject. Then saw this existing thread.
Compared to everyone else here, I would be near the bottom of the pole-technologically
speaking. Our group which is now has 10 or 15 members while we are in what I call "beta mode"
- is totally unsophisticated.
1. A member should NOT be dropped just because his server claimed an incoming message
was spam. It is hard enough getting them to go thru the sign up process the first time.
2. If possible, when an outgoing message is rejected by the member's email, send him a private
message, automatically, to explain to him what is going on. Maybe the message could be sent
under my, the moderators email so it goes thru.
In any case, the member should NOT be dropped.
??
