Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: whitelist issues with sprintpcs.com
To: users@spamassassin.apache.org
References: <CAB1R3sj5uKqtr94Tj8up=Kko23UTcYATzP_CpEDuTBtvWfQs5w@mail.gmail.com>
 <36cceebf-b0b8-3b6d-213b-c53ef57a1efa@thelounge.net>
 <10c32b240d6c88d1153b2720c8a8d3b6@junc.eu>
 <ff422541-423a-c8f2-353c-ca2a39601a10@thelounge.net>
 <f2bc271cd6c07da31be36a9082771a6c@junc.eu>
 <6fef7254-f35d-f411-f22c-998a7cc55663@thelounge.net>
 <5e66eaa56c63f43b17c5f4f5323b83ba@junc.eu>
From: Reindl Harald <h.reindl@thelounge.net>
Openpgp: id=13540402D67A7F71C6E974EA866063CF7F780279;
 url=https://arrakis.thelounge.net/gpg/h.reindl_thelounge.net.pub.txt
Organization: the lounge interactive design
Message-ID: <cdd88914-a16a-6746-31e9-39b3a8923abd@thelounge.net>
Date: Sun, 3 Jul 2016 20:55:49 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <5e66eaa56c63f43b17c5f4f5323b83ba@junc.eu>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="oFGSN0FpKRLFTdODUwSpFWaOtCF0F4iKn"
archived-at: Sun, 03 Jul 2016 18:55:57 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--oFGSN0FpKRLFTdODUwSpFWaOtCF0F4iKn
Content-Type: multipart/mixed; boundary="pffseu5AppXTMML5bp21ElWvNrbqITJus"
From: Reindl Harald <h.reindl@thelounge.net>
To: users@spamassassin.apache.org
Message-ID: <cdd88914-a16a-6746-31e9-39b3a8923abd@thelounge.net>
Subject: Re: whitelist issues with sprintpcs.com
References: <CAB1R3sj5uKqtr94Tj8up=Kko23UTcYATzP_CpEDuTBtvWfQs5w@mail.gmail.com>
 <36cceebf-b0b8-3b6d-213b-c53ef57a1efa@thelounge.net>
 <10c32b240d6c88d1153b2720c8a8d3b6@junc.eu>
 <ff422541-423a-c8f2-353c-ca2a39601a10@thelounge.net>
 <f2bc271cd6c07da31be36a9082771a6c@junc.eu>
 <6fef7254-f35d-f411-f22c-998a7cc55663@thelounge.net>
 <5e66eaa56c63f43b17c5f4f5323b83ba@junc.eu>
In-Reply-To: <5e66eaa56c63f43b17c5f4f5323b83ba@junc.eu>

--pffseu5AppXTMML5bp21ElWvNrbqITJus
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable


Am 03.07.2016 um 20:36 schrieb Benny Pedersen:
> On 2016-07-03 20:26, Reindl Harald wrote:
>
>>         Envelope-Sender
>>         Resent-Sender
>>         X-Envelope-From
>>         From
>
> please tell me what mta add this headers as envelope_sender header ?

obviously enough otherwise it would no exist

> maybe you after that could tell who is idiot ?

well, i can explain that in a better way

EVERY header in doubt is forged, starting with From at the begin and=20
hence for x-headers SpamAssasin relys on internal_networks and/or=20
trusted_networks to know *which* headers are on your own side and which=20
are from untrsued networks

hence all your first 3 or 4 replies are bullshit by definition

nobody asked for unforgeable whitelisting since it#s not posible in the=20
case of the OP

the following rule is the way to go
whitelist_from_rcvd *@pm.sprint.com sprintpcs.com

and *yes i know* that the PTR can be forged, since i control the=20
PTR-zones of our interfaces it would take 10 seconds to get a=20
something.sprintpcs.com

the real problem of the OP is moste likely "(amavisd-new, port 10024)"=20
and so the SA-list is the wrong place for "why is whitelist_from_rcvd=20
from not working properly"


--pffseu5AppXTMML5bp21ElWvNrbqITJus--

--oFGSN0FpKRLFTdODUwSpFWaOtCF0F4iKn
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAld5X7UACgkQhmBjz394AnlMzACdHXQXyG5t3GbAy/8AZ5xOB7g1
HScAnA/lMC59HLkhyRFBrAXxurWCa9ns
=RjQZ
-----END PGP SIGNATURE-----

--oFGSN0FpKRLFTdODUwSpFWaOtCF0F4iKn--