On 2021-06-23 10:48, Franco wrote:
On 22.06.21 08:58, Jeroen Massar wrote:
I suggest using a mailhost that has proper spam filtering, considering it is
trivial to identify
that the sending host is not properly configured, why bother accepting mail
from it?
That's not enough. In first place, the SWINOG contributors should be protected
from being crawled.
-> SWINOG homework
Won't fix a thing. Also as a public list, it is public.
As noted anybody can subscribe or archive the list.
As an example:
https://www.mail-archive.com/[email protected]/msg07408.html
Apparently 3 years old:
https://swinog.swinog.narkive.com
etc etc etc..
And a spammer can just simply also subscribe, next to the avenue of a
hacked computer of one of the members who does not clean out their mailbox.
Greets,
Jeroen
PS: I simply use my mail address everywhere publicly, as spam will come
anyway from whatever source when the address is public somewhere, one
just need to filter and classify properly: good old Spamassassin with a
few RBLs, bit of mimedefang and you are pretty good already (5 per day
in my case), any other (mostly paid) resources will bring spam amount
close to 0 while being able to actually use your mail address.
Spam is the way of live and unfortunately there is always going to be
some source where it will be coming from, as long as the spammers gain
something from their spams... (that something I am still wondering
about, but clearly they must gain something even if the procentiles are
super low).
Oh, and yes, to avoid From: spamming, do have proper DKIM/SPF/DMARC
checks, they 'solve' the spamming issue quite a bit, with only few
mailinglists being problematic while forwarding.
_______________________________________________
swinog mailing list
[email protected]
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
