hey peter,
like your pf book very much helped me a lot to grasp some stuff :)
fot the host solution I already did this but skiped the part with
following the includes.
MS is providing a list of there possible ip ranges here
https://technet.microsoft.com/en-us/library/dn163583(v=exchg.150).aspx
and thats just scary ...
Am 21.04.2017 um 11:59 schrieb Peter N. M. Hansteen:
On Fri, Apr 21, 2017 at 11:25:14AM +0200, Markus Rosjat wrote:
so if you have spamd in place in greylisting mode and you have customers
that work with people who use Office365 as a service you will get calls that
emails are delayed for a freaking long time and if you check the ip range
that outlook.com could send from you get scared.
start with
$ host -ttxt outlook.com
and follow the includes to the very end. Then weep.
TL;DR: last time I looked that expanded to eighty-some *networks* of varying
sizes.
https://github.com/akpoff/spf_fetch fed the relevant domains is one solution,
and in addition you will find my collection of manually maintained SPF
sedimentation
is available at https://home.nuug.no/~peter/nospamd
The problem is that the 'architects' behind outlook.com and their ilk are really
not on board with the idea that having some tiny bit of control over where your
mail
comes from is a good idea, but they were made to comply with the SPF/DKIM/DMARC
scheme
(straight out of the Rube Goldberg school of engineering), which is one of
those endless
and endlessly tiresome artifacts of the "something has to be done", "this is
something"
'system architect' responses.
--
Markus Rosjat fon: +49 351 8107223 mail: [email protected]
G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden
http://www.ghweb.de
fon: +49 351 8107220 fax: +49 351 8107227
Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before
you print it, think about your responsibility and commitment to the
ENVIRONMENT
