Summary: are IP's in noDelay checked against just the IP that's connecting
to ASSP or does it search all of the received headers?
I've got all of Office365's IPS addresses (which I extract from their SPF)
set in NoDelay so that mail sent from Office365 is never delayed. That
seems to work fine.
One of our vendors uses Office365 but they then have all outbound mail go
through their internal SMTP server and then out to the destination SMTP
server.
As I'd expect, this shows as a couple received lines in the email, from top
to bottom:
Received from their-outgoing *A.B.C.D* by my ASSP
Received from their-proxy *a.b.c.F* by their-outgoing
Received: from nam02-bl2-obe.outbound.protection.outlook.com (
mail-bl2nam02lp0086.outbound.protection.outlook.com [*207.46.163.86*])
<-- real line
Received: from BLUPR17CA0052.namprd17.prod.outlook.com (10.162.85.148) by
BN6PR17MB1380.namprd17.prod.outlook.com (10.173.165.9)
The Office365 IP of 207.46.163.86 IS in my noDelay file, I wouldn't expect
that to trigger noDelay since it's A.B.C.D that's connecting to us (which
is not in NoDelay). However, the log shows not delayed because of a
207.46.163.86 match in noDelay. *Does this no delay check look at the
entire header vs just the IP that it actually connecting to ASSP? *
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
