A group of which I am a member posted a message to say that messages sent by the Group were not being delivered.

Similar email delivery problems have manifested themselves on a group I Moderate, and examination of my own email delivery history shows my service provider bouncing emails from Groups.io because...

mx.lb.btinternet.com: 522 email sent from 66.175.222.12 found on industry IP blacklists (Spamhaus/Invaluement/ReturnPath) on 2020/10/25 15:20:41 GMT. To protect our customers, we use leading industry providers of blacklists to ensure only good senders can send email to us. If believe this is a mistake, please contact them directly as there is nothing our Postmaster will be able to do.

I don't know how many mail service proividers may have acted upon this erroneous blacklisting. FWIW this problem seems to have arisen recently, such as this morning UK time. Other than on the group I moderate my Groups.io activity is via the web UI so I have no means of knowing how widespread this problem might be.

Chris

Quite a few to me have bounced today as well, my mail goes via 1&1
Ionos:

mx00.1and1.co.uk: 554 kundenserver.de (mxeue010) Nemesis ESMTP Service
not available No SMTP service IP address is black listed. For
explanation visit
https://www.ionos.com/help/index.php?id=2425&;ip=66.175.222.12&c=bl

Dave

On 25 Oct 2020 at 8:34, Chris Jones via groups.io wrote:

A group of which I am a member posted a message to say that messages
sent by the Group were not being delivered.

Similar email delivery problems have manifested themselves on a group I
Moderate, and examination of my own email delivery history shows my
service provider bouncing emails from Groups.io because...

*mx.lb.btinternet.com: 522 email sent from 66.175.222.12 found on
industry IP blacklists (Spamhaus/Invaluement/ReturnPath) on 2020/10/25
15:20:41 GMT. To protect our customers, we use leading industry
providers of blacklists to ensure only good senders can send email to
us. If believe this is a mistake, please contact them directly as there
is nothing our Postmaster will be able to do.*

I don't know how many mail service proividers may have acted upon this
erroneous blacklisting. FWIW this problem seems to have arisen recently,
such as this morning UK time. Other than on the group I moderate my
Groups.io activity is via the web UI so I have no means of knowing how
widespread this problem might be.

http://davesergeant.com

Hmm, apparently soemthing is affot, I also got it from a seanet.com address:

spamtitan.isomedia.com: 554 5.7.1 Service unavailable; Client host [66.175.222.12] blocked using public.isobl.org; see http://antispam.isomedia.com/?ip=66.175.222.12 for more info and to be unbanned

Cheers,
Christos

On Sun, Oct 25, 2020 at 12:00 PM, Chris Jones wrote:

we use leading industry providers of blacklists to ensure only good senders can send email to us.

The "leading industry provider" seems to be Sorbs Spam. See https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a66.175.222.12&run=toolpage 

Regards,
Bruce

On Sun, Oct 25, 2020 at 05:24 PM, Mark Fletcher wrote:

I am investigating this and will report more later this afternoon.

Many thanks for your efforts on a Sunday!

Chris

As you should know by now, the list of 'bad' IP addresses is fetched by e-mail server admins from Spamhaus. The rate at which this is done (under a cron process) is, within reason, as often as they like. In practice the default is often every 24 hours. How long they live in the receiving e-mail server is also set at a decay pace by the admin., so if the timing is just 'right' and addresses are injected while Spamhaus has them 'up', it could take 1-2 days for a server to clear out definitions (often using a TTL algorithm). Unless, of course, an admin manually flushes the cache, although it's normally 'all or nothing' so they must remember to fetch manually from Spamhaus for fear of getting a bunch of real trash thru until the next fetch.

In practice, it'll last as long as it takes. The only thing you can ever do is inform Spamhaus that it's really not correct and make sure it at least cannot be included on the next fetch by any given e-mail server...... It certainly used to run by IP addr., so it's most annoying when used on sources that are using Shared servers or VPSes. That often blocks out many domains!

--
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 Sun, Oct 25, 2020 at 05:24 PM, Mark Fletcher wrote:

We are not currently blocked by them, but it appears that some places cache this.

Just to let you know that BT (a UK provider) now seems to have stopped bouncing Groups.io traffic.

Fingers crossed...

Chris

Trulyl no good deed goes unpunished.
Mark, thank you for your hard and unrelenting efforts.
You deserve far more praise than you receive.
--

Bob Bellizzi

On Sun, Oct 25, 2020 at 07:41 PM, J_Catlady wrote:

Are the group members showing up as bouncing, or is this invisible?

I can only readily use my own record as a detailed reference, and there were 3 recorded "bounces" this afternoon, but they didn't get me a blue flag. I can find no bounces recorded (for anyone) in my group's activity log for today either. The Owner's Manual does not explain the determination of bouncing status in any detail so looking for a clue there proved fruitless. It may be that as the error code was not the same as a "true bounce" that Groups.io interpreted the return differently.

It's all something of a Black Art... on the plus side my own service provider is passing mails through normally, at least for now.

Chris

On Sun, Oct 25, 2020 at 09:28 PM, I wrote:

on the plus side my own service provider is passing mails through normally, at least for now.

And they have stopped again. :( This was first drawn to my attention by a moderator on a different group who got the same error message as yesterday at 0843 UK time; I had a message for moderation through at 0900 but the post moderation release was bounced at 0949.

Grrr

Chris

During the last couple of days I have noticed that I quite a few messages are going into the Spam folder at gmail.  Messages from groups that never went into the spam folder before.

Barbara

Mark Fletcher wrote:

It appears most places are no longer blocking us because of this listing,
although an ISP in Italy is still blocking us.

I mentioned the problem long ago in GMF.
Italian ISP Telecom (which owns email providers alice.it, aliceposta.it, tin.it) has been rejecting Groups.io messages for months with the following error message:
"smtp.aliceposta.it: 550 mail not accepted from blacklisted IP address [66.175.222.12] "

Nearly all my members in hard bounce status have an account linked to Telecom.
I didn't find a way to contact Telecom about this and eventually I gave up trying.

Thank you for all your work, Mark.

Marina

Thank you Bob, yes, will do if it continues.  I just find it "strange" that this seems to happen while io groups is facing blacklisting in various places.  I usually only have real spam in the spam folder.
Barbara

On Mon, Oct 26, 2020 at 02:30 PM, Robert Oshel wrote:

You can set a filter in Gmail so it never sends messages from Groups.IO to spam.

I'm sorry but you are missing the point here. The problem is that Spamhaus has blacklisted Groups.io and service providers are reacting accordingly by bouncing Groups.io traffic in its entirety, not shunting it into individual's spam boxes.

At the moment it seems to be OK, but who knows what the next few hours will bring...

Chris

On Mon, Oct 26, 2020 at 02:26 PM, Mark Fletcher wrote:

We were blocked again by Spamhaus last night for a few hours.

BT have also restored normal service - for now anyway!

Mark; when Groups.io gets blacklisted do you receive any formal notification or are you reliant on one of us flagging the problem up here or via the support email address?

Chris