| |
YT7MPB > LINUX 21.02.24 22:43l 77 Lines 2588 Bytes #999 (0) @ WW
BID : 7773_YT7MPB
Read: GUEST
Subj: Re: SpamAssasin make ham bulls spam!
Path: IZ3LSV<IR0AAB<I0OJJ<N6RME<YT7MPB
Sent: 240220/1614Z 7773@YT7MPB.#NSD.SRB.EU LinBPQ6.0.24
>From yt7mpb%yt7mpb.#nsd.srb.eu@i0ojj.ampr.org Tue Feb 20 17:15:15 2024
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0o.9dev) with SMTP
id AA16989702 ; Tue, 20 Feb 2024 17:15:15 +0100
Message-Id: <7773_YT7MPB@i0ojj.bbs>
>From: yt7mpb@yt7mpb.#nsd.srb.eu
X-JNOS-User-Port: Telnet (i0ojj @ 44.134.32.240) -> Sending message
On Mon, 19 Feb 24 16:34:00 Z
WG3K wrote:
> R:240219/1644Z @:VE2JOS.#MTL.QC.CAN.NOAM #:62515 [Beauharnois]
> $:1119_WG3K R:240219/1643Z 3929@VE3CGR.#SCON.ON.CAN.NOAM LinBPQ6.0.24
> R:240219/1643Z 32550@KA1VSC.#CCT.CT.USA.NOAM LinBPQ6.0.24
> R:240219/1634Z 1119@WG3K.#SMD.MD.USA.NOAM LinBPQ6.0.24
>
> -----Original Message-----
> From: YT7MPB
> To: LINUX@WW
> Sent: 2/19/2024 10:49
> Subject: Re: SpamAssasin make ham bulls spam!
>
> > On Fri, 16 Feb 24 20:06:00 Z
> > WG3K wrote:
>
> >> I think SpamAssassin adds information to the header that tells why
> >> the message was determined to be "ham" or "spam". Can you provide
> >> that information?
> >>
> >> 73,
> >> Eric WG3K
>
> > I do not see any such information within the header of messages that
> > SpamAssassin sent to spam folder. Where exactly shall be that info?
> > Tnx.
>
> You should be able to look at the header of the message in your mail
> program. It should look something like this:
>
> rewrite_header Subject *****SPAM*****
>
> header FROM_HAS_MIXED_NUMS From =~ /\d+[a-z]+\d+\S*@/i
> describe FROM_HAS_MIXED_NUMS From: contains numbers mixed in
> with letters
>
> score A_HREF_TO_REMOVE 2.0
>
>
> You should be able to configure Spamassassin to ignore messages
> coming from the packet network, too.
>
> https://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Conf.html
>
> 73,
> Eric WG3K
>
>
I see ... but SpamAssassin does not change the header at all here. (By
means to make them look *****SPAM***** or like.) All the headers remain
the same as in original messages, but the messages end up in a separate
SpamAssassin folder. (A separate folder was suggested by the spam
plugin manual.) Seems that the spam plugin integration is bad. I do not
know whether it is a software bug or poor configuration.
I also visited the link you gave above but yet unsure whether
SpamAssassin needs some additional configuration in Linux. (I installed
it from the official repository, and cannot recall if it asked me for
creating & modifying any configuration file. So I supposed it worked in
some default behavior, subject to further 'learning' what is spam and
what is ham.)
--
73 de Misko YT7MPB@YU7BPQ.#NSD.SRB.EU
Read previous mail | Read next mail
| |
