[clamav-users] clamav list spf problem

[Gene Heskett]

On Thursday 21 June 2018 09:33:31 Reindl Harald wrote:

> Am 21.06.2018 um 15:29 schrieb Gene Heskett:
> > On Thursday 21 June 2018 06:54:43 Andrew McGlashan wrote:
> >> On 21/06/18 17:54, Tilman Schmidt wrote:
> >>> Am 20.06.2018 um 19:14 schrieb Andrew McGlashan:
> >>>> This is an opportunity to fix things, such an opportunity should
> >>>> not lost, especially if it helps more people to understand the
> >>>> problems with having too liberal SPF rules (defeating the purpose
> >>>> of SPF).
> >>>
> >>> I disagree. The purpose of clamav-users is to discuss ClamAV
> >>> issues, not to educate people on SPF, so the primary objective of
> >>> fixing the SPF record should be reliable delivery, not educational
> >>> value.
> >>
> >> Normally, I would agree with you, but unfortunately, SPF has been a
> >> thing for far too long to have so many still outstanding issues;
> >> which can only mean that those whom need to know are not looking in
> >> the usual places, or they are just plain ignorant.  Or perhaps they
> >> aren't looking anyware useful and can't see any need to do so....
> >> so, the community (including this one) has a role to help improve
> >> awareness of these problems for the good of the entire community
> >> and to lessen ongoing SPF abuses.
> >
> > What I'd like to see is a good description of SPF.  All these
> > acronyms get thrown around, usually with no references as to why its
> > even needed or how to implement it. Does it help control the
> > neighborhood feral cat problem or what?
>
> what more than https://en.wikipedia.org/wiki/Sender_Policy_Framework
> do you need?

That about covers it, and seems to indicate that there are some scoring 
rules in Spamassassin as I use it on all incoming mail from shentels 
pop3 port that could be turned up, way up. Fetchmail to procmail and 
procmail does ALL that checking.

But what about what I send?  Other than my password to access shentels 
mail server, I don't think they retain anything else so they could even 
properly set that stuff up, and my local domain is not known beyound my 
dd-wrt reflashed router. And from the wording of the rfc's, I doubt if I 
should try to set kmail 1.9.10 up to do it. I use TDE, r14.0.4 here. You 
could look at the headers of this message to see if its proper.

> it helps you to score messages or even whitelist them without
> whitelist a forged sender (SpamAssassin: whitelist_auth)

Thanks.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>