Matus UHLAR - fantomas wrote: > Bob Proulx wrote: > > Shouldn't that message trigger RCVD_IN_SORBS_DUL? > > trusted_networks 199.232.76.173 > only if 199.232.76.173 is in your internal_networks...
Hmm... I had never realized the difference between trusted_networks and internal_networks previously. I had always set the trusted_networks parameter and didn't even know about the internal_networks one. The TrustPath entry on the SA wiki doesn't even mention it. I just added a quick comment there. Your hint about internal_networks was definitely the problem. Because each is set from the other then as soon as either is set then it must always be set fully from then on out. A single IP entry was set in internal_networks and therefore the value of trusted_networks wasn't copied into it. That was the root cause of my problem. Once I removed the single lonely internal_networks setting then once again the entire trusted_networks value was copied into the internal_networks and everything started working again. A note to the developers... Is there really value in having both of these configurations? Now that I am aware of internal_networks I read through the documentation carefully several times and I couldn't imagine a configuration where splitting this was useful. If someone had an example of such to add to the documentation that would make the differentiation of these two more clear. Thanks! Bob
