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
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
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 sho
mailmain includes the receiving IP number, irrespective of whether it
is ipv6 or ipv4, it is not an ipv6 or ipv54 issue :)
it is because 2600:3c03:e000:173::1 is in an abuse range. (probably
because of the snowshoe from linode)
if mail.flamy.ca was an ipv4 that was also abusive or non responsiv
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 messa
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
