Date: Sun, 17 Apr 2016 18:03:41 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: Bill Account Confirmation - 0270505992 Message-ID: <5713C1ED.6090708@FreeBSD.org> In-Reply-To: <fb77dc89-ac90-d73c-a178-385622e4c03e@fechner.net> References: <E1arc1y-004JhX-2W@host-ns-3.basnet.by> <B5BD60FCE7BF4E3D83548E561C0330B2@Rivendell> <fb77dc89-ac90-d73c-a178-385622e4c03e@fechner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6sAInlLVwQbCic6PBo7BefviTIbJC2I3e Content-Type: multipart/mixed; boundary="GkVnDfKCeLX10AecGpE1SjI2aW5hoJbkv" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Message-ID: <5713C1ED.6090708@FreeBSD.org> Subject: Re: Bill Account Confirmation - 0270505992 References: <E1arc1y-004JhX-2W@host-ns-3.basnet.by> <B5BD60FCE7BF4E3D83548E561C0330B2@Rivendell> <fb77dc89-ac90-d73c-a178-385622e4c03e@fechner.net> In-Reply-To: <fb77dc89-ac90-d73c-a178-385622e4c03e@fechner.net> --GkVnDfKCeLX10AecGpE1SjI2aW5hoJbkv Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 17/04/2016 10:53, Matthias Fechner wrote: > Am 17.04.2016 um 11:30 schrieb Reko Turja: >> liukuma.net. IN SPF "v=3Dspf1 a mx -all" >> >> Just saying... >=20 > yes it seems that freebsd does not check the SPF record. > Just saw this morning a forged mail from my domain as well: > host -t SPF fechner.net > fechner.net has SPF record "v=3Dspf1 a mx a:anny.lostinspace.de -all" >=20 > Would be nice if the postmaster would add a SPF check. There used to be a very nice integrated SPF checking facility that was available as a set of patches to the FreeBSD postfix port (postfix being what the FreeBSD mail system runs on), but it wasn't compatible with the latest stable version of postfix and got dropped. Upstream would not accept the patches for reasons I don't entirely understand, although there would have been some extra work to do, given this seems to me to be a natural addition to postfix's new-ish postscreen process. Instead to get SPF checking nowadays you need to implement either milter-sid (which was intended primarily to support the now largely abandoned SPFv2 stuff that Microsoft tried to introduce) or else one of the postfix-policyd-spf implementations (you get to choose from either perl or python there.) Cheers, Matthew --GkVnDfKCeLX10AecGpE1SjI2aW5hoJbkv-- --6sAInlLVwQbCic6PBo7BefviTIbJC2I3e Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXE8HzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATq5wP/1XoLwjTwULMwk9gC20QSmbO 3bht2mP+Tg+mCs2MdXht0yiIR0PkkrEgw6axAO3+UUGeYvi6kmz4WtqDomjVviUV HzDRwryff0opsytXsu+zLK9+bmrHU81fwmP+3MDGqQyVlPvaooRAfbqPs70yP+Uz XUsc5NEhLy4kFOGjiIegNp94XjhZVq73+HnJ7dQY5m3w1UFcT5We1ukxatInACxO pPlRdCSH64qWp1nXIKQaKCobv3lN4YQoMMGHkEyEv5oPsQlJnCMFkeHhmcpAYGUU MXfqt9ItA1qTy9DCSofltn+ObamuUUnTlz8vl7rKvCNibH5FxsDGa2jfo3tMrHos R9pNPmWMf/vYeubHM05v0qlNXmmGwNFh61MIOlRbxTYc85mOTTrMbSmuVFySo4CB nFYFnDFq/kguCIDCll07ASoU3KpVtkglNKVUOu9/FUu7dRzdCzFKzbPnAFx/GI8u C2CLpBfkIH/tBSTyeSczxEZ5LdY1YCQzdE9BMudEX6vjrz3/MFBcJyIm46IwwOR+ zgHq9CzlZL2cG2j8VQGvXv37BCyZP8/0OIzYEAL+rcHIKVGPWkdNXnwTiN0Q6RaL eOWherpCoRgPUuXnOth25Wy6u5jBdmenZj6eZslcfTNSNVJfdXOec6x9Lg7lX3jU vWXKkRBNq292ZOmSQe1O =xxgN -----END PGP SIGNATURE----- --6sAInlLVwQbCic6PBo7BefviTIbJC2I3e--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5713C1ED.6090708>