spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jdow <j...@earthlink.net>
Subject Um, T'Bird and Spamassassin are not seeing eye to eye lately
Date Wed, 19 Jun 2019 08:00:43 GMT
FORGED_MUA_MOZILLA is misfiring on my emails. You should be able to see that in 
an SA run against this email since it seems to trigger on all my emails. I am 
filtering with 3.004000 on a Scientific Linux 7.x system. I noticed this, 
finally, today when an email to a mailing list came back and triggered the 
forged rule. This may be specific to relays through groups.io. Here is a sample 
header and first part of a message:

===8<---
 From - Tue Jun 18 20:06:37 2019
X-Account-Key: account2
X-UIDL: 002ebd304714358b
X-Mozilla-Status: 0010
X-Mozilla-Status2: 00000000
X-Mozilla-Keys: 

Return-Path: <bounce+7651+31137+391786+766443@groups.io>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	thursday.wizardess.wiz
X-Spam-Level: **
X-Spam-Status: No, score=2.7 required=5.0 tests=BAYES_00=-1.9,
	DATE_IN_PAST_06_12=1.543,DKIMWL_WL_HIGH=-0.001,DKIM_SIGNED=0.1,
	DKIM_VALID=-0.1,FORGED_MUA_MOZILLA=2.309,HEADER_FROM_DIFFERENT_DOMAINS=0.249,
	JD_LO_BAYES=0.001,JD_VLO_BAYES=0.001,MAILING_LIST_MULTI=-1,RDNS_NONE=0.793,
	SPF_HELO_NONE=0.001,SPF_SOFTFAIL=0.665 autolearn=no autolearn_force=no
	version=3.4.0
X-Original-To: jdow@thursday.wizardess.wiz
Delivered-To: jdow@thursday.wizardess.wiz
Received: from thursday.wizardess.wiz (localhost [IPv6:::1])
	by thursday.wizardess.wiz (Postfix) with ESMTP id 86B68419923C
	for <jdow@thursday.wizardess.wiz>; Tue, 18 Jun 2019 20:06:33 -0700 (PDT)
Received: from pop.earthlink.net [209.86.93.202]
	by thursday.wizardess.wiz with POP3 (fetchmail-6.3.24)
	for <jdow@thursday.wizardess.wiz> (single-drop); Tue, 18 Jun 2019 20:06:33 
-0700 (PDT)
Received: from noehlo.host ([209.86.89.133])
	by mdl-gnash.atl.sa.earthlink.net (EarthLink SMTP Server) with SMTP id 
1HDqV36lX3Nl3710; Tue, 18 Jun 2019 23:05:53 -0400 (EDT)
Received: from web01.groups.io ([66.175.222.12])
	by ibscan-saipan.atl.sa.earthlink.net (EarthLink SMTP Server) with ESMTP id 
1HDqV21gX3PGoUl1
	for <jdow@earthlink.net>; Tue, 18 Jun 2019 23:05:52 -0400 (EDT)
X-Received: from elasmtp-galgo.atl.sa.earthlink.net 
(elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61])
  by groups.io with SMTP; Tue, 18 Jun 2019 18:49:42 -0700
X-Received: from [47.140.131.91] (helo=[192.168.37.230])
	by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4)
	(envelope-from <jdow@earthlink.net>)
	id 1hdLDY-0003Ou-5Z
	for main@airspy.groups.io; Tue, 18 Jun 2019 17:00:36 -0400
Subject: Re: [airspy] Help with AirSpy
To: main@airspy.groups.io
References: <5D07EC0C.70803@yahoo.com> <29260.1560872734203103331@groups.io>
  <5D090E48.3060007@yahoo.com>
  <CAGtQ24NAtZRxqZFqG3mmZdjxNBiwyewpb=E1Sx4+4-D9J83wvQ@mail.gmail.com>
  <8076DC12-BEBF-4E0F-ADCF-D484F63EE915@blackcatsystems.com>
From: "jdow" <jdow@earthlink.net>
Message-Id: <15A97A99FCCB8DB4.7301@groups.io>
Date: Tue, 18 Jun 2019 14:00:35 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
  Thunderbird/60.7.1
MIME-Version: 1.0
In-Reply-To: <8076DC12-BEBF-4E0F-ADCF-D484F63EE915@blackcatsystems.com>
X-ELNK-Trace: 
bb89ecdb26a8f9f24d2b10475b5711209bcb8c5973b81554483f969212e6ff18f03e6360f34aaf19350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 47.140.131.91
Precedence: Bulk
List-Unsubscribe: <https://airspy.groups.io/g/main/unsub>
Sender: main@airspy.groups.io
List-Id: <main.airspy.groups.io>
Mailing-List: list main@airspy.groups.io; contact main+owner@airspy.groups.io
Delivered-To: mailing list main@airspy.groups.io
Reply-To: main@airspy.groups.io
X-Orig-Message-Id: <1baf2ebe-0e60-a082-6119-c55ed310b5ae@earthlink.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=groups.io;
  q=dns/txt; s=20140610; t=1560913552;
  bh=TGutsx+DixyfPAnGgIW26vjB/U1mlUo7XjSQaqdeGa0=;
  h=Content-Type:Date:From:Reply-To:Subject:To;
  b=DGf+MNkwV4AQPpL7u/eHFnDlwhu+LUzPYD6uuorHQ2GwLxoZE9xObieCj6WzPu+rbMb
  Uo2QdUSS+eTztQXMt/YWIlyRAqQLe/Ki0AdvXaFwU82uwi0nXRfnAv1JNaMDD8PVvDRZB
  m/b+Gm7A5Deso+G9Afl1ir5If5s/gLU2fdo=
X-ELNK-TLSInbound:: 1
X-Authentication-Results: dkim="pass"; (0:DKIM_STAT_OK: function completed 
successfully); dmarc="none"; (1); dwl="miss"; den="not exempt"
X-ELNK-SMM: ---+10-10-52-70dkdd10
X-ELNK-AV: 0
X-ELNK-Info: sbv=0; sbrc=.0; sbf=00; sbw=000;
X-Jdow: user jdow

You might benefit from a modest gain preamplifier up at the antenna. If you have
5 dB of cable loss a 7 to 10 dB gain preamp would do wonders without overly
compromising your dynamic range.

Cable loss increases your noise figure dB for dB. So the long feed line you have
may be reducing your sensitivity considerably.

{^_^}===8<---

{^_^}   Joanne

Mime
View raw message