Jo Rhett wrote: > Daryl, this part of the conversation is academic at best. Amavisd > milter has been patched and is providing the proper received headers, > and network autodetection is still broken. Really, that seems quite odd. I myself have never had it fail for that case before when all the IPs are public ones unless SA couldn't make sense of a Received: header.
Any chance UNPARSABLE_RELAY is firing off? Can you extract a message with that header in it and feed it to SA with debugging on and see if the Received: parser is getting confused? (This could at least tell us a bit about why SA is misunderstanding things.) > > I was trying to build a test case for documenting the flaws, and after > reviewing the code realized that it would take less effort to rewrite > the entire autodetection bit than to explain to Matt Kettler and > others why they need to fix it. Wait, why do I need to fix it? I can't.. I'm a device-driver writer by trade, I don't know jack-squat about writing perl code, so actually working on the SA code itself is out of my area. My involvement in SA is writing rules and trying to help people out. I'm not one of the developers. That said, if the Received: headers are in fact there, and the auto-detect is screwing up, just add a trusted_networks statement to your config. Don't go to all the work of rewriting it.
