On Wed, 8 Jun 2016, jimimaseye wrote:
On 08/06/2016 16:05, Matus UHLAR - fantomas [via SpamAssassin] wrote:
note that if a server acts as your MX, it should be listed in
internal_networks, no matter if other company manages it.
That applies for backup MX servers for your domain, or, even primary MX if
you fetch mail from it e.g. via pop3.
Mathaus, as this thread has shown, can you explain why adding this range as an
internal network hasnt made a difference (and it is still
being checked)?
This sounds like a config file confusion issue. IE the SA that you are running is looking at different config files than the ones that you are editing
or some config file that is being read -after- your expected config files is over-riding your internal_networks settings. Try running SA with the '--debug' option to see the explicit list of config files that it is reading. Make sure that it's reading yours and look at the ones that come after yours to make sure that none of them have a "clear_internal_networks" directive. Be sure the user/environment that you test in is the same that is used during the processing of messages.Silly question, is some meta-framework involved in your system (EG amavis, etc..)
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
smime.p7s
Description: S/MIME Cryptographic Signature
