From owner-freebsd-questions@freebsd.org Sat Apr 20 04:11:32 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B428315826F4 for ; Sat, 20 Apr 2019 04:11:32 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from vps349.pairvps.com (vps349.pairvps.com [216.92.231.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C5057817C8 for ; Sat, 20 Apr 2019 04:11:31 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from [192.168.0.100] (unknown [104.220.39.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps349.pairvps.com (Postfix) with ESMTPSA id C6EF1A5376; Sat, 20 Apr 2019 00:11:23 -0400 (EDT) Subject: how to filter advertisers from joining the list Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Frank Fenderbender In-Reply-To: Date: Fri, 19 Apr 2019 21:11:22 -0700 Reply-To: Frank Fenderbender Content-Transfer-Encoding: quoted-printable Message-Id: References: To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1085) X-Rspamd-Queue-Id: C5057817C8 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of frankfenderbender@council124.org designates 216.92.231.69 as permitted sender) smtp.mailfrom=frankfenderbender@council124.org X-Spamd-Result: default: False [0.12 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_SPAM_SHORT(0.05)[0.046,0]; HAS_REPLYTO(0.00)[frankfenderbender@council124.org]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a:cegray.mail.pairserver.com]; HEADER_FORGED_MDN(2.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.993,0]; RCPT_COUNT_ONE(0.00)[1]; REPLYTO_EQ_FROM(0.00)[]; DMARC_NA(0.00)[council124.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MX_GOOD(-0.01)[mailwash31.pair.com]; NEURAL_HAM_MEDIUM(-0.99)[-0.990,0]; IP_SCORE(-0.13)[asn: 7859(-0.58), country: US(-0.06)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7859, ipnet:216.92.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Apr 2019 04:11:32 -0000 Sorry that I posted under another current questioner's subject-line. I clicked the reply so I didn't have to type anything else in to get the = To:
filled in, and then forgot to change the question to my = own, before asking my own inside the question. email's body. I should've slowed down after having to delete 3 of my 10 = incoming list emails as overt spam. Since BSD is based in security and a history of being older than most = all surviving OSs, I My question is whether we can imagine reducing overt email from the list = that send "questions" about dating, or about buying a service/product... = as a captive audience. It seems ironic that a list membership about a secure OS exhibits = insecurity in who can access our mailboxes and detour our = attention-spans with misrepresentation of purpose. So, I thought that others so-captured might want to seek some proactive = revenge if we can decipher the problem, the tasks, and access. If it's an "open" list then it's up to use to fend off invaders, right? = It's not in anyone's "job description" unless it's in all of our = membership implications? If we don't do it, who will. eh? We do lots of this stuff by ourselves = all the time, so a list mechanism may just need some known detail = brought up so that volunteers will be able to research, prototype with a = test-list, validate, and suggest workarounds or fixes.=20 Examples of everyday improvements we all have made, or could make: Problem: In this day-and-age, 80% of all US phone calls = are robocalls, esp. between 7-9am and 6-8pm.. Workaround: we've used the wildcard features of CPR CallBlocker = and Ooma to pre-delete junk calls and callers. Problem: We send about 30% of what Amazon sells back as = misrepresented, faulty, or incorrect. Workaround: we avoid Jeff Bezos whenever possible. Problem: We screened fake-people from a Yahoo Group = mail-list I used to have; it was tough, because you had to screen for = real people. Workaround: We did not admit to membership anyone who did not = issue a self-statement , semi-divulging that they were not going to lob = ads at us. Problem: quantities of fake-people assault forums. Workaround: on our SMF forum, we use email verification, BOT = lists, and essentially block all eAddresses with alphanumeric = name-fields since that indicates a spammer more often than a lazy = person. =09 Problem: Sado-parasites, thieves, and psycho-terrorists = assault WAN-connected systems on auto-pilot so they can destroy = somewhere else concurrently. Workaround: We added TXT/SPF files to reduce having our spoofed = email addresses get us blocked from relaying mail-servers. We added anti-malware programs to reduce = battles with viruses, spyware, etc. Problem: Approx. 20% of all our USPS-handled packages are = delayed, damaged, or lost. Workaround: We use non-USPS deliverers whenever it's an option, = as a workaround to them ever improving anything but 'images' of quality. So, rather than "getting used to" or tolerating the intolerable creep of = 'quantity over quality', small efforts can often reap great rewards. I enjoy, and thus, prefer reading real questions and answers because a = topic relates to me or just because it sounds interesting. There's so much interesting use and knowledge in listees' worlds that I = resent being demographically-manipulated, like having to answer spam = calls to find out I'm colluding in wasting my time by NOT proactively = blocking them. So, maybe we can get some info about the system running the list so we = can try to make some improvements in proactively blocking spammers at = the membership level? If it is near-"impossible" then we find out from one or more answers why = that is, and, if it is not impossible, then we find out what it may take = and approach it like any other software project that "raising the bar" = for higher quality implies? here's to saving the Delete-button finger for more interesting pursuits, frank=