I am so sorry, I made a stupid assumption. by simply stating "not really" I assumed that people would understand that this means that technically

...

This seems to describe a problem where the recipient's mail service subscribes to a spam blocklist that is incorrectly blocking GTALUG.

this is NOT the case... It is not GTALUG that is blocked... GTALUG is completely clean and in a clean IP range. mailman includes the relay IP number, in the headers, so the incoming email server checks all "Received: from " against whatever RBL dnsbl, etc. So, if the person/ip/sender, that 'sent' to the GTALUG mailing list, ip no is listed, THEN there are issues in receiving email...(by whatever recipient email server) so, sorry about that :( for the rest, I guess I could also elaborate a lot more if anyone is interested? On Fri, 27 Jul 2018 07:45:26 +0200 ac via talk <talk@gtalug.org> wrote:

not really.

the polar other side of your opinion is my opinion :)

people supporting and paying money to resource whores who also are non responsive to abuse complaints and whom also may host criminals and other scumbags deserve to have their email refused :)

the days of 'bullet proof' hosting are nearing the end as many mail server admins are simply tired of constantly trying to do battle with snowshoe and other rubbish.

of course, again, best practise is not to 'drop' but to score email incoming from abusive hosts and IP numbers as well as bad places on the net, and at first mark them as spam, report that spam and then, eventually, these resources will also end up in a permanent drop dnsbl :)

and;

...

--Bob, who is experiencing such problems with the lists he manages.

does your list require people to opt in? or are people simply added and then expected to unsubscribe?

see, sometimes 'people' are not real people, they could be data in stolen databases, they could be submitted by devious 3rd parties to cause your list harm, there could be so many issues...

If you are just adding email addresses to your list :) - then you will find yourself experiencing issues if something goes wrong and you are reported somewhere...

On Fri, 27 Jul 2018 00:23:50 -0400 Bob Jonkman via talk <talk@gtalug.org> wrote:

...

This seems to describe a problem where the recipient's mail service subscribes to a spam blocklist that is incorrectly blocking GTALUG.

This is not GTALUG's problem; the recipients not receiving mail should complain to their mail provider to use a better blocklist. Or perhaps those recipients should switch to a different mail provider that doesn't use that blocklist. Selfhosting springs to mind...

Alex shouldn't have to contact every poorly configured blocklist when recipient mail providers choose to use those poorly configured blocklists. Of course, when the recipients' mail provider doesn't give any indication to the recipient that their mail is being blocked, it's difficult for the recipient to know they're missing mail. And if mail from talk-owner@gtalug.org is also blocked, then it's impossible for the list owner to let the recipient know their mail is bouncing.

--Bob, who is experiencing such problems with the lists he manages.

On 2018-07-26 02:23 PM, Alex Volkov via talk wrote:

...

Oh, it's not the messages that list receives that get filtered out, it's when mailman sends out list to the recipients, some who have spamhaus and running on an IPv6 port get mailing list messages filtered.

We could disable IPv6 on our end, but it just feels wrong to me.

Here's the error message I'm getting on my personal email server

<subscriptions@flamy.ca>: host mail.flamy.ca[2600:3c03:e000:173::1] said: 554     5.7.1 Service unavailable; Client host [2600:3c03::f03c:91ff:fe50:ea0a] blocked using sbl.spamhaus.org;https://www.spamhaus.org/sbl/query/SBLCSS     (in reply to RCPT TO command)

I believe the following hosts have similar settings to mine --

csclub.uwaterloo.ca vex.net

I believe there are 7 people including myself, that get routinely affected by the issue.

On 2018-07-26 03:06 AM, ac via talk wrote:

...

Hi,

There seems to be many people using non blocking RBL for DROP?

Alex, Instead of using that specific spamhaus DNSBL for DROP you should rather use it for scoring?

An example of a DROP RBL is chronic webiron.com and dnsbl.ascams.com these you can use for DROP?

Will it not be better to add scoring to sa and then to add numeric values?

hth

Andre

On Wed, 25 Jul 2018 12:06:23 -0400 Alex Volkov via talk <talk@gtalug.org> wrote:

...

We also have a web interface for mailman, so you can check if you're messages are showing up there, since the default mailing list settings is not to receive your own emails.

https://gtalug.org/pipermail/talk/

On 2018-07-25 11:53 AM, James Knott via talk wrote:

...

Let me know if you don't receive this message.  ;-)

I sent it to both the list and you directly, so you can see if it got through the list.

On 07/25/2018 11:49 AM, Lennart Sorensen via talk wrote: > I don't think I have received any messages from the list in > about 2 weeks. The only thing I have gotten is a message > saying I have been removed due to bounces (strangely that one > didn't bounce). No idea why that would happen since other > things work fine, including lkml which is notorious for > hating bouncing emails. > > Anyone have any idea what could be going on? >   --- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk

--- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk

---

Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk

--- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk

--- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk